> I have used Zeo with Zope 2.7.6 for some time now. I currenty run Plone
> 2.05 on Zope 2.7.6 with zeo in production. Zope and Zeo runs on the same
> machine running Debian Linux 3.0 (i386). I started using zeo to make
> debugging of a simple skin product easier.
> Now I am moving to a fresh server w Debian Linux 3.1 where I am trying
> the same setup with Zope 2.8.1.
> Zope 2.8.1 with Zeo 3.4.1 fails utterly.
> I can some times get instances running but eventually get transactions
> failures, lost connections, and poskeyerrors.
> It seems like smooth sailing when I run Zope 2.8.1 standalone.
I expect you'd get better advice on a Zope list, like
If it's an identifiable problem with ZODB/ZEO 3.4.1, then this (zodb-dev) is
a good place to discuss it, but since there are no other reports of this I
have to suspect it's due to a problem(s) in your specific Zope and/or Plone
configuration. For example,
> Another fishy thing is that zeo fails to start when you uncomment the
> #user zope
> in zeo.conf
suggests OS-level permission problems (do you get log messages? exceptions?
the process hangs? ... "fails to start" could mean a lot of things).
> Are there any additional test suites that I can run to nail down my
> problem? I did run the standard make tests in Zope 2.8.1 with no
You could try running test.py with the "--all" switch, and that will run
more ZEO connection tests. Those are ZEO unit tests, though. AFAIK, there
is nothing in the test suite that specifically tries to run Zope with ZEO.
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org