From 11c860b10a82850f1ce01ea910293a7c7ad61ff7 Mon Sep 17 00:00:00 2001 From: Marcel de Rooy Date: Mon, 1 Feb 2016 13:48:06 +0100 Subject: [PATCH] Bug 15713: Restart zebra when rotating logfiles Content-Type: text/plain; charset=utf-8 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 --- debian/koha-common.logrotate | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/debian/koha-common.logrotate b/debian/koha-common.logrotate index 37024d3..0299b62 100644 --- a/debian/koha-common.logrotate +++ b/debian/koha-common.logrotate @@ -8,7 +8,11 @@ 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 } -- 1.7.10.4