journal corrupted or uncleanly shut down, renaming and replacing

[JoshuaA]

I see this at every boot on my laptop:

"systemd-journald[199]: File /var/log/journal/f0ef3fc3e4fc49499dde3f432cce4c77/user-1000.journal corrupted or uncleanly shut down, renaming and replacing"

-- systemd-204-9.fc19.x86_64

I shut down from KDE shutdown widget and it seems normal but there seems to be a random element when the system boots; sometimes synaptic touch pad is detected other times not -- also system freezes occasionally, almost always when firefox is running.

[Gareth Jones]

I don’t know much about the Systemd journal, other than it’s Systemd’s native equivalent to /var/log/*. I’d start by seeing if there were any problems with the disk or file-system though, unless anyone has any better ideas.

Are there any suspicious messages in /var/log/boot.log or /var/log/messages after a shut-down/boot cycle? Check the SMART data for your disk (e.g. “smartctl -x /dev/sda” or whatever disk tool KDE provides). Also try forcing a file-system check (e.g. “su -c "touch /forcefsck” and reboot).

[JoshuaA]

I know nothing about systemd journal or why it has over 600 MB of data in /var/log/journal. I think I may have to figure out how to turn it off.

SMART says the disk is OK

It seems like journald just doesn't know when it's time to shut down and it keeps way too much data --logs going back to April 3.

I don't know why I need systemd-journal or how to control it but something is not right with it.

[Gareth Jones]

I missed that you’re using F19. Is /var/log/messages huge too? Is it possibly related to this thread: http://forums.fedoraforum.org/showthread.php?t=291813?

That bug should be fixed, but I’m not sure what happens if there are left over logs from when it was active.

[JoshuaA]

Thanks, I'm going to nuke the journal files and see if it can cope. There is also a messages file dated 16th June 594MB so I am most likely caught in the after effects of the rsyslog bug.