#journalctl corrupt file

46 messages · Page 1 of 1 (latest)

grand kernel
#

I used systemd-analyze blame to try figure out why it was taking so long to boot. I ran sudo journalctl --verify to try find the cause. Could this be an issue to why it is taking longer to boot and is it crucial that this is fixed?

PASS: /run/log/journal/(shortened)/system.journal
PASS: /var/log/journal/(shortened).journal
d65fc0: Invalid entry item (0/23) offset: 000000
d65fc0: Invalid object contents: Bad message
File corruption detected at /var/log/journal/(shortened) (of 16777216 bytes, 83%).
FAIL: /var/log/journal/(shortened)~ (Bad message)
PASS: /var/log/journal/(shortened)~
PASS: /var/log/journal/(shortened)/system.journal

Prior to this error, I am not aware if this was happening. I changed the maximum file sizes to 50M but later returned it to its default after no difference in boot time.

cold osprey
#

you either have file corruption which is a early sign of a disk failure or

#

i would think you have a systemd unit that is hanging while you are booting up which can also be a file system check due to failing drive

#

more than likely it will be a systemd unit just taking a long time to acquire it's target such as

#

a network unit trying to get an ip address and your dhcp server is being slow to give an ip

#

your systemctl status might say something like this

#

if you run systemctl you will be shown which units are failing by the red dot next to them

grand kernel
#

@cold osprey
Actually it looks completely fine. I ran systemctl status and it is not degraded and systemctl does not return any failing services.

Apologies but I also forgot to mention, the main culprit of the long boot time is systemd-journald.service

#

And after deleting the file after making changes to the journald configuration, journalctl —verify now returns no errors.

cold osprey
#

Good

grand kernel
cold osprey
#

i would first turn off the journal service and see if the problem is fixed temporally

#

i would then turn it back on and look for the issue with the journal service and see which external input is slowing journalctrl down

grand kernel
grand kernel
cold osprey
#

journalctl

#

on the left of each line there is a time stamp

grand kernel
deep fiberBOT
#

xaix1999 received a thank you cookie!

grand kernel
#

looks like it's my wireless mouse...

cold osprey
#

Maybe try a wired mouse

grand kernel
#

any way to fix this?

cold osprey
#

did you disable the wireless adapter?

grand kernel
cold osprey
#

did you reboot the system with the wired mouse plugged in and the wireless adapter removed?

grand kernel
cold osprey
#

is this a different device each time or the same device?

grand kernel
#

i have 2 different mouses, 1 wired and 1 wireless

cold osprey
#

is the wireless unplugged?

grand kernel
#

i only plugged in one at a time to test

#

wireless and wired make it longer even if only one of them are plugged in

cold osprey
#

unplug both and then boot

grand kernel
#

let me see if it does the same with my wifi adapter one sec ill plug it in

#

nope he wifi adapter is fine

grand kernel
#

and

#

it doesn't take 10 seconds to boot up systemd-journald.service anymore

#

when no mouse is plugged in

#

same with wired headphones too, takes 10 seconds

cold osprey
#

sounds like your usb controller

#

probably the front or the back will work better, if you have a desktop pc.

grand kernel