Jens Vagelpohl wrote: > > On 30 Jun 2006, at 13:40, Julien Anguenot wrote: >>> Yesterday night, we were having a long nightly running process (several >>> hours) on one of the ZEO node. (Around 500 Mo logs on this one). The >>> reopen occurred while the Zope server was still working. The reopen went >>> ok but it restarted the Zope server at the same time which of course >>> stopped the actual running operation of ours. >>> >>> Did someone experienced this ? >>> >>> Any feedbacks appreciated. > > For maximum reliability I tend to forego the built-in log reopening in > favor of using the logrotate utility in "copytruncate" mode. This will > not require any log file reopening, logrotate will simply make a copy of > the existing log and then truncate the logfile that continues to be in > use to zero length. Zope or the ZEO server won't have to know or care at > all at that point.
Thank you Jens for the quick reply. I think I'm going to send these instructions, to be on the safe side, to the administrators taking care of the cluster. Do you have any idea about the "zopectl logreopen" misbehavior as someone who's avoiding using it explicitly ;) ? Cheers, J. -- Julien Anguenot | Nuxeo R&D (Paris, France) Open Source ECM - www.nuxeo.com CPS Platform - http://www.cps-project.org Mobile: +33 (0) 6 72 57 57 66
Description: OpenPGP digital signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )