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

[Zbigniew Jędrzejewski-Szmek]

On Sun, Aug 04, 2013 at 01:22:21PM +0200, Kay Sievers wrote:
> On Sun, Aug 4, 2013 at 12:14 AM, Pedro Francisco
> <pedrogfrancisco at gmail.com> 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.
> > 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?
> 
> Probably fixed by:
>   http://cgit.freedesktop.org/systemd/systemd/commit/?id=8b18fdc19531ba56d0bdfe34c62870997a9bcc96

Kay, are you saying that this commit could influence the
starting and stopping of journald, not just lost messages?

Zbyszek