We are seeing spontaneous restarts of Zope with no indication in any of
the standard Zope logs. Looking at the ZEO log indicates that the
restarts of Zope are due to a lost connection between Zope & ZEO but
with no other information. The logging level is set at the distribution
The restarts are a huge problem because session variables are not
persistent and so all of the user state they contain is lost on restart.
In our statful implementation, this is a major problem. I want to adjust
the configuration so that the Zope/ZEO connection is stable.
In our configuration, Zope and ZEO are linked via localhost on a
I've Googled about looking for some infomation about tuning the ZEO/Zope
interface, but have found little real information. Some additional log
detail would be helpful.
We are running a fairly vanilla setup, excerpted below:
# ZEO client storage:
# ZODB cache, in number of objects
# ZEO client cache, in bytes
# Uncomment to have a persistent disk cache
# monitor-address PORT
# transaction-timeout SECONDS
exit-codes 0, 2
# user zope
# 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.
It's not clear what changes will lead to a more stable connection because
it is not clear what's triggering the problem. Any advice would be
Presumably the shotgun approach would work -- increase the cache sizes,
lengthen the invalidation-queue-size, and increase the backoff-limit but
it would be nice to have some guidance.
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -