[MXS-2445] Logrotate config missing from RHEL RPM package Created: 2019-04-22 Updated: 2019-06-19 Resolved: 2019-06-10 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Packaging |
| Affects Version/s: | 2.2.20 |
| Fix Version/s: | 2.3.8 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Assen Totin (Inactive) | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| 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 } |
| Comments |
| Comment by markus makela [ 2019-04-29 ] |
|
SIGHUP previously reloaded the configuration but was removed along with the configuration reloading. The signal is unused and could be re-mapped to log rotation again. |