Séra Balázs to [email protected] • 4 months agoRemember to not to forget clearing your journallemmy.worldmessage-square61fedilinkarrow-up1668
arrow-up1668imageRemember to not to forget clearing your journallemmy.worldSéra Balázs to [email protected] • 4 months agomessage-square61fedilink
minus-squareMorethanevillinkfedilink151•4 months agoCleanup Check current disk usage: sudo journalctl --disk-usage Use rotate function: sudo journalctl --rotate Or Remove all logs and keep the last 2 days: sudo journalctl --vacuum-time=2days Or Remove all logs and only keep the last 100MB: sudo journalctl --vacuum-size=100M How to read logs: Follow specific log for a service: sudo journalctl -fu SERVICE Show extended log info and print the last lines of a service: sudo journalctl -xeu SERVICE
minus-squaremacniellinkfedilink37•4 months agoI mean yeah -fu stands for “follow unit” but its also a nice coincidence when it comes to debugging that particular service.
minus-square@[email protected]linkfedilink24•4 months ago --vacuum-time=2days this implies i keep an operating system installed for that long
minus-squareslazer2aulinkfedilinkEnglish19•4 months ago sudo journalctl --disk-usage panda@Panda:~$ sudo journalctl --disk-usage No journal files were found. Archived and active journals take up 0B in the file system. hmmmmmm…
minus-square@[email protected]linkfedilink12•edit-24 months agouser@u9310x-Slack:~$ sudo journalctl --disk-usage Password: sudo: journalctl: command not found
minus-square@[email protected]linkfedilink5•4 months agoI don’t have any feelings towards particular init systems.
minus-square@[email protected]linkfedilink4•4 months agoJust curious, what distro do you use that systemd is not the default? (I at least you didn’t change it after the fact if you don’t have any feelings (towards unit systems ;) ) )
minus-square@[email protected]linkfedilink8•4 months agoThank you for this, wise sage. Your wisdom will be passed down the family line for generations about managing machine logs.
minus-squareMorethanevillinkfedilink5•4 months agoGlad to help your family, share this wisdom with friends too ☝🏻😃
minus-square@[email protected]linkfedilink2•4 months agoYeah, if I had dependents they’d gather round the campfire chanting these mystical runes in the husk of our fallen society
minus-square@[email protected]linkfedilink2•4 months ago@[email protected] is the remindme bot offline?
minus-squareAtegonlinkfedilink3•edit-24 months agoIts semi broken currently and also functions on a whitelist with this community not being on the whitelist
minus-square@[email protected]linkfedilink3•4 months agoIf you use OpenRC you can just delete a couple files
minus-square@[email protected]linkfedilink3•4 months agoActually something I never dug into. But does logrotate no longer work? I have a bunch of disk space these days so I would not notice large log files
minus-squareMorethanevillinkfedilink2•edit-24 months agoIf logrotate doesn’t work, than use this as a cronjob via sudo crontab -e Put this line at the end of the file: 0 0 * * * journalctl --vacuum-size=1G >/dev/null 2>&1 Everyday the logs will be trimmed to 1GB. Usually the logs are trimmed automatically at 4GB, but sometimes this does not work
minus-square@[email protected]linkfedilink5•4 months agoIf we’re using systemd already, why not a timer?
minus-squareMorethanevillinkfedilink3•4 months agoCron is better known than a systemd timer, but you can provide an example for the timer 😃
minus-square@[email protected]linkfedilink5•edit-24 months agoReally, the correct way would be to set the limit you want for journald. Put this into /etc/systemd/journald.conf.d/00-journal-size.conf: [Journal] SystemMaxUse=50M Or something like this using a timer: systemd-run --timer-property=OnCalender=daily $COMMAND
minus-square@[email protected]linkfedilink2•4 months agoWhy isn’t it configured like that by default?
minus-square@[email protected]linkfedilink5•4 months agoIt is. The defaults are a little bit more lenient, but it shouldn’t gobble up 80 GB of storage.
Cleanup
Check current disk usage:
sudo journalctl --disk-usageUse rotate function:
sudo journalctl --rotateOr
Remove all logs and keep the last 2 days:
sudo journalctl --vacuum-time=2daysOr
Remove all logs and only keep the last 100MB:
sudo journalctl --vacuum-size=100MHow to read logs:
Follow specific log for a service:
sudo journalctl -fu SERVICEShow extended log info and print the last lines of a service:
sudo journalctl -xeu SERVICEI mean yeah -fu stands for “follow unit” but its also a nice coincidence when it comes to debugging that particular service.
😂😂
this implies i keep an operating system installed for that long
something something nix?
panda@Panda:~$ sudo journalctl --disk-usage No journal files were found. Archived and active journals take up 0B in the file system.hmmmmmm…
seems like someone doesn’t like systemd :)
I don’t have any feelings towards particular init systems.
Just curious, what distro do you use that systemd is not the default? (I at least you didn’t change it after the fact if you don’t have any feelings (towards unit systems ;) ) )
Slackware
Badass! Thanks!
Thank you for this, wise sage.
Your wisdom will be passed down the family line for generations about managing machine logs.
Glad to help your family, share this wisdom with friends too ☝🏻😃
Yeah, if I had dependents they’d gather round the campfire chanting these mystical runes in the husk of our fallen society
@[email protected] 6 months
@[email protected] is the remindme bot offline?
Its semi broken currently and also functions on a whitelist with this community not being on the whitelist
Ok, thanks!
If you use OpenRC you can just delete a couple files
Actually something I never dug into. But does logrotate no longer work? I have a bunch of disk space these days so I would not notice large log files
If logrotate doesn’t work, than use this as a cronjob via
sudo crontab -ePut this line at the end of the file:0 0 * * * journalctl --vacuum-size=1G >/dev/null 2>&1Everyday the logs will be trimmed to 1GB. Usually the logs are trimmed automatically at 4GB, but sometimes this does not work
If we’re using systemd already, why not a timer?
Cron is better known than a systemd timer, but you can provide an example for the timer 😃
Really, the correct way would be to set the limit you want for journald. Put this into
/etc/systemd/journald.conf.d/00-journal-size.conf:Or something like this using a timer:
systemd-run --timer-property=OnCalender=daily $COMMANDThanks for this addition ☺️
Why isn’t it configured like that by default?
It is. The defaults are a little bit more lenient, but it shouldn’t gobble up 80 GB of storage.
Good question, it may depend on the distro afaik