Closed christoph-zededa closed 2 months ago
I see lots of:
2024-06-06T22:17:50.7496145Z "severity": "err",
2024-06-06T22:17:50.7497162Z "source": "dhcpcd",
2024-06-06T22:17:50.7497417Z "iid": "2843",
2024-06-06T22:17:50.7497767Z "content": "control_free: No such file or directory",
2024-06-06T22:17:50.7498128Z "msgid": "1686",
2024-06-06T22:17:50.7498485Z "timestamp": "2024-06-06T22:05:30.808785330Z"
2024-06-06T22:17:50.7498783Z },
and
2024-06-06T22:17:50.7845035Z {
2024-06-06T22:17:50.7845144Z "severity": "err",
2024-06-06T22:17:50.7845264Z "source": "dhcpcd",
2024-06-06T22:17:50.7845482Z "iid": "2841",
2024-06-06T22:17:50.7845632Z "content": "no such user dhcpcd",
2024-06-06T22:17:50.7845739Z "msgid": "1626",
2024-06-06T22:17:50.7845949Z "timestamp": "2024-06-06T22:05:30.673920100Z"
2024-06-06T22:17:50.7846117Z },
@christoph-zededa You can ignore those dhcpcd errors. We always had those. I would like to get rid of them, but probably the only option is to filter them out inside the newlog service.
refs #977