This seems to have done the trick. Haven't had to start zebra in two days now ... me= happy ! Thanks to everyone for the assistance with this. On Fri, Jun 22, 2018 at 11:56 AM Paul Hoffman <paul@flo.org> wrote:
On Thu, Jun 21, 2018 at 09:16:56AM -0400, Scott Owen wrote:
I still seem to be having some issues with logrotate and the zebra service starting up....
I have tried both of the options discussed in bug # https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885
Has there been a good / reliable fix to this issue ? I was hoping that an upgrade to 17.11 might be the solution...but sadly, I still seem to have this issue on 2 of my 3 Kha installs....
Another possible solution, which avoids shutting down Koha altogether, is to tweak the logrotate config to use the "copytruncate" setting. So instead of all the prerotate/postrotate stuff, just do this:
/var/log/koha/*/*.log { rotate 5 weekly missingok compress delaycompress notifempty copytruncate }
Here's what the logrotate man page says about copytruncate:
copytruncate Truncate the original log file in place after creating a copy, instead of moving the old log file and optionally creating a new one. It can be used when some program cannot be told to close its logfile and thus might continue writing (appending) to the previous log file forever. Note that there is a very small time slice between copying the file and truncating it, so some log- ging data might be lost. When this option is used, the create option will have no effect, as the old log file stays in place.
Paul.
-- Paul Hoffman <paul@flo.org> Systems Librarian Fenway Libraries Online c/o Wentworth Institute of Technology 550 Huntington Ave. Boston, MA 02115 (617) 442-2384 (FLO main number) _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha