0

I was perplexed to find that, when running for instance journalctl -f showed my logs to stop on Apr 20th, 8 months ago. I piped to less, journalctl | less and pressed G to go to the end, same thing.

Then I did journalctl | less and went down 'slowly' (ctrl+d), this way I was able to go way further than Apr 20th...

Theres a LOT in the logs! I think it is because there's a limit on what is being loaded. However, shouldn't the logs get rotated? Or somehow pruned without user intervention?

In my journald.conf SystemMaxFileSize/SystemMaxUse isn't set (a solution I found here). I could try the above, but I kinda want to get to the bottom of it.

I'm on Manjaro 5.8.18-1.

Any help or insights are greatly appreciated. Thanks!

1

The bottom of it is that SystemMaxUse is not defined by default, so journald log can grow infinitely large.

Journald logs are not rotated because it stores data in a way which makes rotating logs near impossible.

To reduce the size of your logs, run sudo journalctl --vacuum-size=100M

To avoid the issue, please define SystemMaxUse - I personally have:

cat /etc/systemd/journald.conf.d/systemMaxUse.conf
[Journal]
SystemMaxUse=64M

More than enough for a home PC.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.