Marcel de Rooy
af47f00636
Somehow, it may happen that Zebra keeps writing to the old rotated logfile
with extension .log.1. I must add that although I saw that happen (a new
log was created and was empty, while Zebra kept writing to log.1 for weeks),
I cannot reproduce it every time.
By stopping the zebra server in prerotate and starting it again in
postrotate, this should not happen at all. In practice, this implies that
your Zebra server is restarted once a week.
Note: The existing sharedscripts directive makes sure that these actions
are not executed for all individual logfiles but once for all matching
logfiles (even when running multiple instances).
Test plan:
[1] Apply the change in koha-common.logrotate to the file
/etc/logrotate.d/koha-common.
[2] Run logrotate -f /etc/logrotate.conf (forcing a logrotate).
[3] Check in zebra-error.log that your zebra server was stopped
('killed by signal 15').
[4] Verify that your Zebra server runs (read: has been restarted).
(Do a search..)
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Marc Véron <veron@veron.ch>
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Signed-off-by: Brendan Gallagher brendan@bywatersolutions.com
18 lines
415 B
Text
18 lines
415 B
Text
# Rotate log files for all Koha instances.
|
|
|
|
/var/log/koha/*/*.log {
|
|
rotate 5
|
|
weekly
|
|
missingok
|
|
compress
|
|
delaycompress
|
|
notifempty
|
|
sharedscripts
|
|
prerotate
|
|
/usr/sbin/koha-stop-zebra $(koha-list --enabled) > /dev/null
|
|
endscript
|
|
postrotate
|
|
/etc/init.d/apache2 reload > /dev/null
|
|
/usr/sbin/koha-start-zebra $(koha-list --enabled) > /dev/null
|
|
endscript
|
|
}
|