Hash: SHA1

Julien Anguenot wrote:
> 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 ;) ?

I think the shift to the oh-so-much-better Python logging module is not
complete.  See this bit in ZEO/runzeo.py:

    def handle_sigusr2(self):
        # TODO: this used to reinitialize zLOG. How do I achieve
        # the same effect with Python's logging package?
        # Should we restart as with SIGHUP?
        log("received SIGUSR2, but it was not handled!", \

svn blames Tim for the comment, and Gintautas for the actual logging
call change.

- --
Tres Seaver          +1 202-558-7113          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to