Re: F19: journald stops logging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2013-08-03 at 10:39 +0100, Pedro Francisco wrote:
> Journald stops logging. I had enabled lots of iwl3945 debugging
> 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?

I'd guess it got tripped up by the huge amount of stuff you're writing
to it, if 'allowing system journal files to grow to 1.4G' is any
indication. I'd file a bug against systemd with the details from this
post and probably a bit more (what debugging did you enable exactly,
just how much stuff does it write to the logs...).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux