Hey ! I'm experiencing some problem trying to use the monitor server. I've zope 2.7.6 running, with an emergency user defined in the instance's access file, with password stored as clear text. When I try to run the monitor_client.py script, I type my password and everything I get (except a warning for using regsub instead of re) is : warning: unhandled connect event and the script ends. Does anyone managed to access the monitor server with zope 2.7.6 ? Non related question : is there some documentation about Zope's icp capabilities ? TIA -- Sylvain Thénault LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org
Sylvain Thénault wrote at 2005-5-11 18:03 +0200:
... warning: unhandled connect event
This is a medusa/asyncore message indicating a bug: no application specific "connect" method was defined for the asynchronous connect event. -- Dieter
On Thursday 12 May à 20:43, Dieter Maurer wrote:
Sylvain Thénault wrote at 2005-5-11 18:03 +0200:
... warning: unhandled connect event
This is a medusa/asyncore message indicating a bug: no application specific "connect" method was defined for the asynchronous connect event.
so do we agree this is a Zope 2.7.6 bug ? Should I fill an entry to the collector ? BTW, Andreas seems to have had the same problem as reported in a comments of http://www.zope.org/Collectors/Zope/1565, and nothing more has happened, so I doubt about my correct usage of this feature, even if I can't think about what I made wrong (I've zope running on localhost and an access file with clear text password...). -- Sylvain Thénault LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org
Sylvain Thénault wrote at 2005-5-13 16:43 +0200:
...
Sylvain Thénault wrote at 2005-5-11 18:03 +0200:
... warning: unhandled connect event
This is a medusa/asyncore message indicating a bug: no application specific "connect" method was defined for the asynchronous connect event.
so do we agree this is a Zope 2.7.6 bug ? Should I fill an entry to the collector ?
Cannot hurt (but I doubt it will help).
... even if I can't think about what I made wrong (I've zope running on localhost and an access file with clear text password...).
I assume this feature is only very rarely used nowadays (although there are still a few use cases). Since ages, I am using "zopectl debug" to analyse Zope problems; and some IDEs (e.g. the commercial WingIDE) allow to debug a life Zope instance (which uses techniques similar to the monitor but is *much* more comfortable). -- Dieter
participants (2)
-
Dieter Maurer -
Sylvain Thénault