[ZODB-Dev] Yet more ZEo weird error messagism :-S

[Chris Withers]

Jeremy Hylton wrote:
> 
> The serendipity of detecting bugs continues to amuze and delight me.
> Jens Vagelpohl reported a very similar problem yesterday.  Is there
> any chance you have a MemoryError traceback in the logs for your ZEO
> server?

I think this is the relevent chunk from the log:

------
2001-09-26T02:44:17 ERROR(200) ZEO uncaptured python exception, closing channel
<ZEOConnection con\
nected 127.0.0.1:40191 at 16776b08> (socket.error:(104, 'Connection reset by
peer') [/usr/local/li\
b/python2.1/asyncore.py|poll|107]
[/usr/local/lib/python2.1/asyncore.py|handle_write_event|390] [/\
usr/local/zope/2.4.0_base/lib/python/ZEO/smac.py|handle_write|188]
[/usr/local/lib/python2.1/async\
ore.py|send|330])
------
2001-09-26T02:44:34 INFO(0) ZEO Server Close 376924936
------
2001-09-26T04:11:11 ERROR(200) ZEO Server Pack failed for 1
Traceback (innermost last):
  File /usr/local/zope/2.4.0_base/lib/python/ZEO/StorageServer.py, line 391, in
_pack
    (Object: dispatcher)
  File /usr/local/zope/2.4.0_base/lib/python/ZODB/FileStorage.py, line 1436, in
pack
    (Object: /var/local/zope/storage/var/Data.fs)
MemoryError


> If you do have a MemoryError on the other end, you should grab the
> latest source for the zeo-1_0-branch of the CVS repository. 

Hurm, does this mean there will be a 1.0b5?

> I fixed
> it last night to avoid consuming excessive amounts of memory when it
> logs information. 

Can you explain this a little more? There shouldn't be a lot of logging going on
with this storage server...

That said, there seems to be a lot of this stuff:
2001-09-25T18:52:44 INFO(0) ZEO Server Close 365405544
------
2001-09-25T18:53:28 INFO(0) ZEO Server Connect 290458800 ('127.0.0.1', 34089)
------
2001-09-25T18:53:36 INFO(0) ZEO Server Close 290458800
------
2001-09-25T18:56:33 INFO(0) ZEO Server Connect 380649648 ('127.0.0.1', 35106)
------
2001-09-25T18:56:38 INFO(0) ZEO Server Close 380649648

What does this mean?

cheers,

Chris