Séra Balázs@lemmy.world to linuxmemes@lemmy.world · 2 个月前Remember to not to forget clearing your journallemmy.worldimagemessage-square54fedilinkarrow-up1669arrow-down110
arrow-up1659arrow-down1imageRemember to not to forget clearing your journallemmy.worldSéra Balázs@lemmy.world to linuxmemes@lemmy.world · 2 个月前message-square54fedilink
minus-squareMorethanevil@lemmy.fedifriends.sociallinkfedilinkarrow-up151·2 个月前Cleanup 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-squaremacniel@feddit.orglinkfedilinkarrow-up38·2 个月前I mean yeah -fu stands for “follow unit” but its also a nice coincidence when it comes to debugging that particular service.
minus-squarelseif@sopuli.xyzlinkfedilinkarrow-up23·2 个月前 --vacuum-time=2days this implies i keep an operating system installed for that long
minus-squareslazer2au@lemmy.worldlinkfedilinkEnglisharrow-up19·2 个月前 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-squaresuperkret@feddit.orglinkfedilinkarrow-up12·edit-22 个月前user@u9310x-Slack:~$ sudo journalctl --disk-usage Password: sudo: journalctl: command not found
minus-squaremacniel@feddit.orglinkfedilinkarrow-up20·edit-22 个月前seems like someone doesn’t like systemd :)
minus-squaresuperkret@feddit.orglinkfedilinkarrow-up5·2 个月前I don’t have any feelings towards particular init systems.
minus-squareScipitie@lemmy.dbzer0.comlinkfedilinkarrow-up4·2 个月前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 ;) ) )
minus-squareTekkip20@lemmy.worldlinkfedilinkarrow-up8·2 个月前Thank you for this, wise sage. Your wisdom will be passed down the family line for generations about managing machine logs.
minus-squareMorethanevil@lemmy.fedifriends.sociallinkfedilinkarrow-up5·2 个月前Glad to help your family, share this wisdom with friends too ☝🏻😃
minus-squareVirtualOdour@sh.itjust.workslinkfedilinkarrow-up2·2 个月前Yeah, if I had dependents they’d gather round the campfire chanting these mystical runes in the husk of our fallen society
minus-squareelxeno@lemm.eelinkfedilinkarrow-up2·2 个月前@ategon@programming.dev is the remindme bot offline?
minus-squareAtegon@programming.devlinkfedilinkarrow-up3·edit-22 个月前Its semi broken currently and also functions on a whitelist with this community not being on the whitelist
minus-squarePacmanlives@lemmy.worldlinkfedilinkarrow-up3·2 个月前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
minus-squareMorethanevil@lemmy.fedifriends.sociallinkfedilinkarrow-up2·edit-22 个月前If 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-squarefallingcats@discuss.tchncs.delinkfedilinkarrow-up5·2 个月前If we’re using systemd already, why not a timer?
minus-squareMorethanevil@lemmy.fedifriends.sociallinkfedilinkarrow-up3·2 个月前Cron is better known than a systemd timer, but you can provide an example for the timer 😃
minus-squarefallingcats@discuss.tchncs.delinkfedilinkarrow-up5·edit-22 个月前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: [Journal] SystemMaxUse=50M Or something like this using a timer: systemd-run --timer-property=OnCalender=daily $COMMAND
minus-squareMorethanevil@lemmy.fedifriends.sociallinkfedilinkarrow-up3·2 个月前Thanks for this addition ☺️
minus-squareMonkderVierte@lemmy.mllinkfedilinkarrow-up2·2 个月前Why isn’t it configured like that by default?
minus-squarefaerbit@sh.itjust.workslinkfedilinkarrow-up5·2 个月前It is. The defaults are a little bit more lenient, but it shouldn’t gobble up 80 GB of storage.
minus-squareMorethanevil@lemmy.fedifriends.sociallinkfedilinkarrow-up2·2 个月前Good question, it may depend on the distro afaik
minus-squarerambling_lunatic@sh.itjust.workslinkfedilinkarrow-up2·2 个月前If you use OpenRC you can just delete a couple files
Cleanup
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
I 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
@RemindMe@programming.dev 6 months
@ategon@programming.dev 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!
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 -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
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 $COMMAND
Thanks 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
If you use OpenRC you can just delete a couple files