Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.2.20
-
Fix Version/s: 2.3.8
-
Component/s: Packaging
-
Labels:None
-
Sprint:MXS-SPRINT-83, MXS-SPRINT-84
Description
MariaDB-provided RPM package lack a logrotate configuration. MaxScale comes with logginig to /var/log/maxscale/maxscale.log enabled hence he file grows indefinitely.
It is a common and good practice for RPM packages to provide a logrotate config for each log file, written by the package.
Sample logrotate file (not necessarily best one - I spotted that SIGUSR1 whould cause MAxScale to reopen logs, but have not tested this; the more usual kill -HUP <pid_file> seems not to do this):
/var/log/maxscale/maxscale.log
{ daily rotate 30 missingok notifempty compress sharedscripts postrotate systemctl restart maxscale endscript }