You are not logged in.
Pages: 1
Started getting an error during boot saying I have a audit socket error.
Looked at systemctl status on journald and it shows this:
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Sat 2023-08-05 07:37:02 BST; 1min 50s ago
TriggeredBy: ● systemd-journald.socket
○ systemd-journald-audit.socket
● systemd-journald-dev-log.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 314 (systemd-journal)
Status: "Processing requests..."
Tasks: 1 (limit: 38333)
FD Store: 16 (limit: 4224)
Memory: 7.8M
CPU: 76ms
CGroup: /system.slice/systemd-journald.service
└─314 /usr/lib/systemd/systemd-journald
Aug 05 07:37:02 arch systemd-journald[314]: Collecting audit messages is disabled.
Aug 05 07:37:02 arch systemd-journald[314]: Journal started
Aug 05 07:37:02 arch systemd-journald[314]: Runtime Journal (/run/log/journal/3042f6e3e8d04104b528c0b3bef87255) is 8.0M, max 639.2M, 631.2M free.
Aug 05 07:37:02 arch systemd[1]: systemd-journald.service: Deactivated successfully.
Aug 05 07:37:03 arch systemd-journald[314]: Time spent on flushing to /var/log/journal/3042f6e3e8d04104b528c0b3bef87255 is 38.995ms for 1118 entries.
Aug 05 07:37:03 arch systemd-journald[314]: System Journal (/var/log/journal/3042f6e3e8d04104b528c0b3bef87255) is 49.2M, max 50.0M, 768.0K free.
Aug 05 07:37:03 arch systemd-journald[314]: Received client request to flush runtime journal.
Aug 05 07:37:03 arch systemd-journald[314]: /var/log/journal/3042f6e3e8d04104b528c0b3bef87255/system.journal: Boot ID changed since last record, rotating.
Aug 05 07:37:03 arch systemd-journald[314]: Rotating system journal.
Aug 05 07:37:13 arch systemd-journald[314]: /var/log/journal/3042f6e3e8d04104b528c0b3bef87255/user-1000.journal: Boot ID changed since last record, rotating.
Guessing I just need to enable audit service?
Last edited by Mr Green (2023-08-05 15:06:33)
Mr Green I like Landuke!
Offline
around april 16 2023 systemd-journal started giving messages about monotonic clock, see https://bbs.archlinux.org/viewtopic.php?id=286918
Since systemd 254-1 'monotic clock' does no longer appear, now the message you posted does appear.
I have audit=0 as kernel parameter since a long time and never saw these messages until april.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Added audit=0 to kernel line and indeed error message is gone.
Did find this:
https://superuser.com/questions/1247161 … -transport
Thank you for pointing me in the right direction...will mark thread as solved
Mr Green I like Landuke!
Offline
Pages: 1