[systemd-devel] Journald stops logging when lots of output

[Zbigniew Jędrzejewski-Szmek]

On Sat, Aug 03, 2013 at 11:14:28PM +0100, Pedro Francisco wrote:
> (question migrated from test at lists.fedoraproject.org )
> 
> On Fedora 19, journald ( systemd-204-9.fc19.i686 ) stops logging. I
> had enabled lots of iwl3945 debugging ( various messages for each
> iwl3945 interaction -- modprobe iwl3945 debug=0x47ffffff ) throughout
> the night and the last thing `journalctl -b` has is:
> 
> Ago 03 02:25:45 s2 systemd-journal[29414]: Allowing system journal
> files to grow to 1.4G.
> Ago 03 02:25:45 s2 systemd-journal[29414]: Journal started
> Ago 03 02:25:45 s2 systemd[1]: systemd-journald.service: main process
> exited, code=exited, status=1/FAILURE
> Ago 03 02:25:45 s2 systemd[1]: Started Trigger Flushing of Journal to
> Persistent Storage.
Some similar bugs appeared with jorunald apparently dying when
the kernel logs a lot. [1] is recent, but I think I saw some other
instances. journald should throttle kernel messages, and could
ligitimately loose some when the kernel is really verbose, but
of course it shouldn't exit. I would start by investigating
why journald exited.

Zbyszek

[1] https://bugzilla.redhat.com/show_bug.cgi?id=990323


> Ago 03 02:25:45 s2 systemd[1]: systemd-journald.service: main process
> exited, code=killed, status=10/USR1
> Ago 03 02:25:45 s2 systemd[1]: Started Trigger Flushing of Journal to
> Persistent Storage.
> Ago 03 02:25:45 s2 systemd[1]: systemd-journald.service: main process
> exited, code=killed, status=10/USR1
> Ago 03 02:25:45 s2 systemd[1]: Started Trigger Flushing of Journal to
> Persistent Storage.
> Ago 03 02:25:45 s2 systemd-journal[29419]: Allowing system journal
> files to grow to 1.4G.
> Ago 03 02:25:45 s2 systemd-journal[29419]: Journal started
> Ago 03 02:25:45 s2 systemd[1]: systemd-journald.service: main process
> exited, code=exited, status=1/FAILURE
> Ago 03 02:25:45 s2 systemd[1]: Started Trigger Flushing of Journal to
> Persistent Storage.
> Ago 03 02:25:45 s2 systemd-journal[29423]: Allowing system journal
> files to grow to 1.4G.
> Ago 03 02:25:45 s2 systemd-journal[29423]: Journal started
> Ago 03 02:25:45 s2 systemd[1]: systemd-journald.service: main process
> exited, code=exited, status=1/FAILURE
> Ago 03 02:25:45 s2 systemd[1]: Started Trigger Flushing of Journal to
> Persistent Storage.
> 
> It is now 10:35 and while dmesg has (lots) of new info, journalctl -f does not.
> 
> Any tips on what may be wrong?
> 
> -- 
> Pedro
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>