You are not logged in.

#1 2018-03-26 19:57:00

MountainX
Member
Registered: 2016-02-08
Posts: 371

systemd journal corruption

I am frequently seeing corrupted files when I run:

journalctl --verify

There's an old thread on the topic here: https://bbs.archlinux.org/viewtopic.php?id=156139

However, I have not found any solution to the issue. I have seen it on every Arch Linux system I have administered, including recently on an Arch VPS I set up. It seems journal file corruption is the norm, not the exception.

There is a five year old discussion on it here: systemd - journalctl --verify reports corruption - Unix & Linux Stack Exchange https://unix.stackexchange.com/question … corruption
But there is no solution presented.

Here is an example of corruption from a system I checked today:

000000: Invalid tail monotonic timestamp                                                                                                                                                                                                                            
File corruption detected at /var/log/journal/7db5321aaf884af786868ec2f2e9c7b0/user-1000@b70c1fae8f70465f9865941b34b16590-0000000000053a8a-000564202e09ce9f.journal:270f070 (of 41943040 bytes, 97%). 

6251f8: Data object references invalid entry at f5d068                                                                                                                                                                                                              
File corruption detected at /var/log/journal/7db5321aaf884af786868ec2f2e9c7b0/system@000567d61afcdce5-4b89cce0de846a95.journal~:f574d8 (of 16777216 bytes, 95%).   

63ec9a8: Invalid data object at hash entry 0 of 233016                                                                                                                                                                                                              
File corruption detected at /var/log/journal/7db5321aaf884af786868ec2f2e9c7b0/system@0005683cfe1d1205-a424f58116dd7fda.journal~:3ee2b10 (of 109051904 bytes, 60%). 

Offline

#2 2018-03-30 05:23:06

MountainX
Member
Registered: 2016-02-08
Posts: 371

Re: systemd journal corruption

Is anybody else seeing corrupted journal files?

Offline

#3 2018-03-30 13:25:01

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,302

Re: systemd journal corruption

I don't see corruptions of the systemd journal.

The .journal~ suffix can appear when the journal is not cleanly closed.

But if you only have 3 errors, it's not very serious.

Offline

#4 2018-03-30 13:49:28

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: systemd journal corruption

You could try putting journal in ram and letting syslog-ng write everything to disk, see https://wiki.archlinux.org/index.php/Sy … md_journal


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB