You are not logged in.
Pages: 1
I tried to launch commands to analyze the size of actual logs and to rotate them, nothing works
Since 6 months my logs are not rotated
Offline
https://bbs.archlinux.org/viewtopic.php?id=57855
http://www.catb.org/~esr/faqs/smart-questions.html
Which logs are you talking about? Which log rotation utility are you using and why...(something else rather than just the journal?), what are the outputs of these commands.
Offline
I'm talking about the logs `journalctl` pointing to
I'm using the Arch default one (considering that it used to rotate before march and that I never installed anything about that)
Because Arch does it by default and that if there isn't any logs becomes unbearable
The output of `journalctl` is tons of logs
Output of `logrotate -f /etc/logrotate.d/rsyslog` is `no such file of directory`
Offline
You can limit "amount" of logs by space, as described here:
https://wiki.archlinux.org/index.php/Sy … size_limit
You can also limit log storage by time limits, read about and pay attention to default values:
man journald.conf | less -p 'MaxFileSec|MaxRetentionSec'
Last edited by Fixxer (2020-09-13 11:38:47)
Offline
My problem is not about space and storage but about logs managment, my logs does not rotate so the system does not work anymore
For example if the politic was "200MB per log file, compress all old logs, delete the 7th log file" my logs were nicely managed
But now the system does nothing and it's like "Main log at 8GB, old logs at 200MB, no rotation, no deletion" and it can't continues like that
And my problem is not about configuring, because it used to work but not now, it's about finding why the politic does not apply anymore and relaunch that politic
For example `# Entries in this file show the compile time defaults.` in `journald.conf`, and those default configuration already manage rotation, but I don't have any rotation, so the problem is not about configuring
Last edited by vf (2020-09-13 12:01:04)
Offline
the politic was "200MB per log file, compress all old logs, delete the 7th log file"
Where have you configured this? Please share your /etc/systemd/journald.conf.
But now the system does nothing and it's like "Main log at 8GB, old logs at 200MB, no rotation, no deletion" and it can't continues like that
Why not? You've already said this is not about space, and you've already been directed to the man page which explains how to limit by size and age. If you aren't reaching these thresholds, then what is the problem?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Look at these parameters (SystemMaxFiles defaults to 100):
man journald.conf | less -p 'SystemMaxFileSize|SystemMaxFiles'
Which way will you choose - it's your decision.
For diagnosis:
df -BM /
journalctl --disk-usage
Last edited by Fixxer (2020-09-13 12:15:55)
Offline
I said "For example if"
It can't continues like that because "logs becomes unbearable"
The problem is not "about space and storage but about logs managment", because "my logs does not rotate so the system does not work anymore", and it's not "about configuring, because it used to work but not now", The problem is about "finding why the politic does not apply anymore and relaunch that politic"
Don't reply hedge please...
Offline
It can't continues like that because "logs becomes unbearable"
Please elaborate on this. In what way do they become "unbearable"?
The problem is about "finding why the politic does not apply anymore and relaunch that politic"
Then please post your journald.conf as requested.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1