[ZODB-Dev] Disconected Error

[Alastair Burt]

"Jeremy Hylton" <jeremy@zope.com> (2003-02-28):

>> I keep getting Disconnected Errors with my ZEO. They always arise when I
>> use the undo tab in the ZMI. I see from searching the mailing lists that I
>> am not the only one to experience these errors arising from undo
>> behaviour. But, as far as I can see, there is no indication in the list
>> archives of the root cause of this problem and how to get around
>> it. When I
>> mount the Data.fs directly, without using the ZEO, there is no
>> problem. Can
>> anyone tell me what is going wrong?
>
> I expect the ZEO server is failing in some unexpected way.  Can you get
> debug log output from the server?  Normally, an uncaught traceback on the
> server is propagated back to the client.  I don't know what that isn't
> happening here.

In my stupid log file, I get the following:

  2003-02-28T15:12:43 INFO(0) ZCS:3416 Connected to storage: ('127.0.0.1', 19010)
  ------
  2003-02-28T15:18:14 PROBLEM(100) ZCS:3416 Disconnected from storage: "('localhost', 19010)"
  ------
  2003-02-28T15:18:14 INFO(0) ZCS:3416 Testing connection <ManagedConnection ('127.0.0.1', 19010)>
  ------
  2003-02-28T15:18:15 INFO(0) ZEC:1 read_index: cache file 0 has 3035 records and 5091873 bytes
  ------
  2003-02-28T15:18:17 INFO(0) ZCS:3416 Connected to storage: ('127.0.0.1', 19010)

I guess all of this is on the client side. I do not know how get the server
to log more information. I got zctl.py to call ZEO.start.py with -d, but
that did not seem to help any.

--- Alastair