- Server operating system version
- Ubuntu 24.04.3 LTS
- Plesk version and microupdate number
- Plesk Obsidian 18.0.74 Update 2
Scenario:
I use Warden and like to fine-tune the Amavis log files to further improve my filters.
Unfortunately, I only have access to the last four to five days. After doing some research, I made changes that affect journal log retention.
But after a week of the changes being in effect (service restart, server restart), there is no change to be seen. Only 4-5 days remain.
Where is the error? Have I overlooked something, or is there another setting that needs to be adjusted?
Grateful for any advice.
I use Warden and like to fine-tune the Amavis log files to further improve my filters.
Unfortunately, I only have access to the last four to five days. After doing some research, I made changes that affect journal log retention.
Code:
cat /etc/systemd/journald.conf
[Journal]
Storage=persistent
#Compress=yes
#Seal=yes
SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
SystemMaxUse=2G
#SystemKeepFree=25%
#SystemMaxFileSize=100M
#SystemMaxFiles=100
#RuntimeMaxUse=10%
#RuntimeKeepFree=
#RuntimeMaxFileSize=
RuntimeMaxFiles=100
MaxRetentionSec=6month
MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes
#AutoFlush=yes
But after a week of the changes being in effect (service restart, server restart), there is no change to be seen. Only 4-5 days remain.
Code:
journalctl --disk-usage
Archived and active journals take up 798.0M in the file system.
Where is the error? Have I overlooked something, or is there another setting that needs to be adjusted?
Grateful for any advice.