On Thu, Sep 26, 2013 at 2:46 PM, Olav Vitters wrote:
> On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
>> (Of course, journald should not exit under any such circumstances, but
>> to find that we first need to track down why it does that currently).
>
> Though it might hide pro
On Wed, Sep 11, 2013 at 6:33 PM, Lennart Poettering
wrote:
> On Mon, 12.08.13 14:58, Pedro Francisco (pedrogfranci...@gmail.com) wrote:
>
>> Hi,
>> Systemd complains frequently about corrupted journal. Do note: I don't
>> have the default mount options.
Hi,
Systemd complains frequently about corrupted journal. Do note: I don't
have the default mount options.
$ dmesg |grep corrupte
[ 51.766346] systemd-journald[181]: File
/var/log/journal/06fde5edd4974fa9a343215f093f5aae/user-42.journal
corrupted or uncleanly shut down, renaming and replacing.
How should I see journald status/log?
sudo systemctl status systemd-journald.service ?
P.S.: /var/lib/systemd/coredump is empty.
On Sun, Aug 4, 2013 at 5:15 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sat, Aug 03, 2013 at 11:14:28PM +0100, Pedro Francisco wrote:
>> (question migrat
(question migrated from t...@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=0x47ff ) throughout
the night and the last thing `journalct
e% Mounted on
rootfs 15G 11G 4,1G 72% /
System: up-to-date Fedora 17, x86
$ sudo rpm -qa systemd*
systemd-sysv-44-21.fc17.i686
systemd-44-21.fc17.i686
systemd-analyze-44-21.fc17.i686
What else can I do to debug what is going on next time it happens?
Thanks in Advance
