[ZODB-Dev] more lockup information / zope2.9.6+zodb 3.6.2
Alan Runyan
runyaga at gmail.com
Mon Apr 9 16:50:47 EDT 2007
Hi Jim, yes, still having lockups. We have a list of deadlockdebugger
info associated with each lockup.
The client configuration as at the beginning of this thread. The zeo
server configuration is as follows:
# ZEO configuration file
%define INSTANCE /usr/local/zeo-ah
<zeo>
address 8100
read-only false
invalidation-queue-size 100
# pid-filename $INSTANCE/var/ZEO.pid
# monitor-address PORT
# transaction-timeout SECONDS
</zeo>
<filestorage 1>
path $INSTANCE/var/Data.fs
</filestorage>
<filestorage 2>
path $INSTANCE/var/Catalog.fs
</filestorage>
<eventlog>
level info
<logfile>
path $INSTANCE/log/zeo.log
</logfile>
</eventlog>
<runner>
program $INSTANCE/bin/runzeo
socket-name $INSTANCE/etc/zeo.zdsock
daemon true
forever false
backoff-limit 10
exit-codes 0, 2
directory $INSTANCE
default-to-interactive true
# user zope
python /usr/local/python/bin/python
zdrun /usr/local/zope-2.9.6/lib/python/zdaemon/zdrun.py
# This logfile should match the one in the zeo.conf file.
# It is used by zdctl's logtail command, zdrun/zdctl doesn't write it.
logfile $INSTANCE/log/zeo.log
</runner>
any insight would be appreciated.
cheers
alan
More information about the ZODB-Dev
mailing list