You are not logged in.
When my machine boots I get lots of Failed to start Journal Service errors on the screen. And I mean A LOT:
$ journalctl -b|grep "Failed to start Journal Service"|wc -l
2340After a few seconds boot process continues just fine, and everything works:
... snipped another few hundred of the same error ...
Dec 12 09:50:09 Motoko systemd[1]: Starting Journal Service...
Dec 12 09:50:09 Motoko systemd[1]: systemd-journald.service start request repeated too quickly, refusing to start.
Dec 12 09:50:09 Motoko systemd[1]: Failed to start Journal Service.
Dec 12 09:50:09 Motoko systemd[1]: Starting Journal Service...
Dec 12 09:50:09 Motoko systemd[1]: Started Journal Service.
Dec 12 09:50:09 Motoko systemd-journal[417]: Journal startedSince not BBS is not full of this (in fact google turned up nothing) I guess this is specific to my machine, but I have no idea where to look or where to fix this.
I only reboot around kernel updates, so I have no idea after which update is this behavior started. Sometimes during the last three weeks.
Last edited by ijanos (2012-12-21 17:33:21)
Offline
So have you fully migrated to systemd? You might want to step through this once again.
Offline
Yep, I did the full systemd switch more than 2 month ago and everything works fine since then.
And yes, I already check all those config files. The funny thing is that everything works fine. Just for some reason journald refuses to start for a few second and then comes to its sense.
Offline
Well, it's not doing it anymore... marking as solved.
Offline