Hi all, 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.... Thanks, -S
Excerpts from Scott Owen's message of 2018-06-21 09:16:56 -0400:
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
I was able to solve this problem by disabling anacron, as described here: https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html
Thanks Mark, But...unfortunately....look like the issues is still happening...even with the anacron line rem'd out... -S On Thu, Jun 21, 2018 at 3:43 PM, Mark Alexander <marka@pobox.com> wrote:
Excerpts from Scott Owen's message of 2018-06-21 09:16:56 -0400:
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
I was able to solve this problem by disabling anacron, as described here:
https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Try this: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19610 El mar., 26 jun. 2018 a las 10:13, Scott Owen (<sowen@edzone.net>) escribió:
Thanks Mark,
But...unfortunately....look like the issues is still happening...even with the anacron line rem'd out...
-S
On Thu, Jun 21, 2018 at 3:43 PM, Mark Alexander <marka@pobox.com> wrote:
Excerpts from Scott Owen's message of 2018-06-21 09:16:56 -0400:
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
I was able to solve this problem by disabling anacron, as described here:
https://lists.katipo.co.nz/pipermail/koha/2016-September/046167.html _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Scott-- I don't know if it is related, but I just upgraded from 17.05 --> 17.11 and immediately started having issues with logrotate and Zebra not starting when koha-common started/restarted or after logrotation. This is a multi-tenant, package install running on Ubuntu 16.04. Things worked fine for the first instance on the machine, but Zebra and logrotate failed for the remaining installations. Additionally, I received an error report that logrotate was failing at the postrotate script. I have had issues with the new koha-zebra commands in the past when on 17.05, so that was a likely place to start. In the end, I went into /etc/logrotate.d/koha-common and /etc/init.d/koha-common and replaced all instances of koha-zebra command with the deprecated versions (i.e. koha-start-zebra, koha-restart-zebra, koha-stop-zebra) and all has been well since... gcb ~~~~~~~~~~~~~~~ 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....
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)
Thanks Paul, Is there any drawback to this ?? (other than the small slice of time where the logs may not be written to ) ?? -S 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
On Tue, Jun 26, 2018 at 09:14:43AM -0400, Scott Owen wrote:
Is there any drawback to this ?? (other than the small slice of time where the logs may not be written to ) ??
No, not in my opinion -- just do it in the wee hours of the morning to avoid a loss of log entries. 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)
Very good then, I'll try that on one of my instances for a few days and see what happens.... Thanks again ! On Tue, Jun 26, 2018 at 9:41 AM, Paul Hoffman <paul@flo.org> wrote:
On Tue, Jun 26, 2018 at 09:14:43AM -0400, Scott Owen wrote:
Is there any drawback to this ?? (other than the small slice of time where the logs may not be written to ) ??
No, not in my opinion -- just do it in the wee hours of the morning to avoid a loss of log entries.
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
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
participants (5)
-
Bortel, Gary -
Mark Alexander -
Paul Hoffman -
Scott Owen -
Tomas Cohen Arazi