[ZODB-Dev] Re: [ZODB-Dev] ZEO starting/using problem

Tino Wildenhain tino@wildenhain.de
Mon, 09 Dec 2002 17:49:56 +0100


Hi,

--On Montag, 9. Dezember 2002 11:20 -0500 Jeremy Hylton <jeremy@zope.com> 
wrote:

>>>>>> "EB" == Eric Brun <Eric.Brun@univ-savoie.fr> writes:
>
>   EB> I try ZEO ZODB3.1 branch and the same thing happens : the client
>   EB> Zoe in a hang when I start it has 'zope' user.  When I start has
>   EB> root, no hang
>
>   EB> What is the solution ?
>
> Is there any more information in the debug log for either the client
> or the server?  For example, do you see a "new connection" log message
> on the server?  Are there any tracebacks in the log?

Start of ZEO:

------
2002-12-09T17:37:47 INFO(0) ZEO/start.py Changed directory to 
/usr/devel/storage/var
------
2002-12-09T17:37:48 INFO(0) ZEO/start.py Serving zopeimages: 
<ZODB.FileStorage.FileStorage instance at 0x821ebdc>
------
2002-12-09T17:37:48 INFO(0) ZEO/start.py Serving zoperoot: 
<ZODB.FileStorage.FileStorage instance at 0x81ca24c>
------
2002-12-09T17:37:48 INFO(0) ZSS:2095 StorageServer created RW with 
storages: zopeimages:RW, zoperoot:RW

Then Start of Zope, which yells out:

------
2002-12-09T17:39:21 INFO(0) ZCS:2113 ClientStorage (pid=2113) created 
RW/normal for storage: 'zoperoot'
------
2002-12-09T17:39:21 INFO(0) ZEC:zoperoot ClientCache: storage='zoperoot', 
size=20971520; file[0]=None
------
2002-12-09T17:39:21 INFO(0) ZCS:2113 Testing connection <ManagedConnection 
('127.0.0.1', 16001)>
------
2002-12-09T17:39:21 INFO(0) ZCS:2113 Connected to storage
------
2002-12-09T17:39:21 INFO(0) ZODB Opening database for mounting: 
'143937112_1039339259.101064'
------
2002-12-09T17:39:21 INFO(0) ZODB Mounted database 
'143937112_1039339259.101064' at /temp_folder
------
2002-12-09T17:39:22 INFO(0) ZServer HTTP server started at Mon Dec  9 
17:39:22 2002
...

While ZEO log adds this line:

2002-12-09T17:39:21 INFO(0) ZSS:2095 new connection ('127.0.0.1', 45876): 
<ManagedServerConnection ('127.0.0.1', 45876)

An HTTP-connection to zope is neither shown in Z2.log nor leaves any
trace in the ZEO_EVENT.log

Zope running with the Data.fs without ZEO works fine.

Regards
Tino