Menu
▾
▴
|
From: Michele M. <mic...@ma...> - 2005-10-12 16:18:50
|
Hello, I have a problem with the LDAPUserFolder and the developer suggested me to post the problem here: System: Red Hat Enterprise Linux AS release 4 (Nahant Update 2) gcc version 3.4.3 Python 2.3.5 Zope 2.7.7 LDAPUserFolder 2.2 and >=2.5 OpenLDAP 2.2.13 python-ldap 2.0.10 Description: With the 2.2 Version of LDAPUserFolder I haven't any problem but with the others mentioned I get after a while (could be 5 minutes or 1 hour) the following error messages: (4) May 24 21:50:13: getUserByAttr: "uid=mmarcio" not found (4) May 24 21:50:13: _lookupuserbyattr: No user "uid=mmarcio" (NULL result without error in PyObject_Call) (9) May 24 21:50:13: _lookupuserbyattr: Using filter "(&(uid=mmarcio)(objectClass=top)(objectClass=person))" (9) May 24 21:50:13: _lookupuserbyattr: Binding as "cn=nethz_proxy,ou=admins,ou=id,ou=auth,o=ethz,c=ch" (3) May 24 21:49:39: LDAPUserFolder reinitialized by __setstate__ (4) May 24 17:29:05: getUserByAttr: "uid=admin" not found (4) May 24 17:29:05: _lookupuserbyattr: Binding as "cn=admin,ou=users,ou=nethz,ou=id,ou=auth,o=ethz,c=ch" fails (9) May 24 17:29:05: _lookupuserbyattr: Using filter "(&(uid=admin)(objectClass=top)(objectClass=person))" (9) May 24 17:29:05: _lookupuserbyattr: Binding as "cn=nethz_proxy,ou=admins,ou=id,ou=auth,o=ethz,c=ch" I can "solve" the problem only if I restart my Zope Instance. The developer replied to me: >>> From: Jens Vagelpohl >>> This error message originates in the python-ldap extensions >>> themselves. There is no C code in the LDAPUserFolder product. If you >>> made any changes to python-ldap when you upgraded the LDAPUserFolder >>> package I suggest trying different versions of python-ldap. I'm >>> afraid there isn't much I can do to help. >> >> From: Michele Marcionelli >> But what I didn't understand is, that I use 2 different LDAP User >> Folders (2.2 and 2.5) with the same Python/Zope, i.e. with the same >> python-ldap. >> >> How can I give you more information? Debug? Etc.? > > From: Jens Vagelpohl > I'm still not sure if I will be able to help you because that's in > the C layer which I never looked at. It would be helpful, even if > it's done just for the purpose of tossing this onto the python-ldap > list, for you to find out the specific query and invocation that > causes this. Can someone help me? Cheers, Michele -- mic...@ma... / phone: +41 44 632 6193 eth zentrum / hg g 14 / raemistrasse 101 - ch-8092 zurich !DSPAM:434d375a115958476112754! |
|
From: Jens V. <je...@da...> - 2005-10-12 16:24:46
|
On 12 Oct 2005, at 17:18, Michele Marcionelli wrote: >> From: Jens Vagelpohl >> I'm still not sure if I will be able to help you because that's in >> the C layer which I never looked at. It would be helpful, even if >> it's done just for the purpose of tossing this onto the python-ldap >> list, for you to find out the specific query and invocation that >> causes this. >> > > Can someone help me? Not without doing what I asked you to do: Find out what invocation and query caused the problem. Reduce it to a simple test case that provokes the problem. jens |
|
From: Michele M. <mic...@ma...> - 2005-10-12 16:42:50
|
Hi Jens, On 12.10.2005, at 18:24, Jens Vagelpohl wrote: > On 12 Oct 2005, at 17:18, Michele Marcionelli wrote: >>> From: Jens Vagelpohl >>> I'm still not sure if I will be able to help you because that's in >>> the C layer which I never looked at. It would be helpful, even if >>> it's done just for the purpose of tossing this onto the python-ldap >>> list, for you to find out the specific query and invocation that >>> causes this. >> >> Can someone help me? > > Not without doing what I asked you to do: Find out what invocation and > query caused the problem. Reduce it to a simple test case that > provokes the problem. I don't know if there is a specific query that causes the problem. - I start zope: everything work fine - Nobody access the Server - Wait... let say... one hour - and I can't login as ldap-user anymore... - in the logfile appears the "NULL result without error in PyObject_Call" message Is that maybe a timeout/connection problem? You improved something like that in the 2.3 or 2.4 Version of LDAPUserFolder. HTH, Michele -- mic...@ma... / phone: +41 44 632 6193 eth zentrum / hg g 14 / raemistrasse 101 - ch-8092 zurich !DSPAM:434d3cfe211325585820369! |
|
From: Jens V. <je...@da...> - 2005-10-12 16:46:48
|
On 12 Oct 2005, at 17:42, Michele Marcionelli wrote: >>> Can someone help me? >>> >> >> Not without doing what I asked you to do: Find out what invocation >> and query caused the problem. Reduce it to a simple test case that >> provokes the problem. >> > > I don't know if there is a specific query that causes the problem. > > - I start zope: everything work fine > - Nobody access the Server > - Wait... let say... one hour > - and I can't login as ldap-user anymore... > - in the logfile appears the "NULL result without error in > PyObject_Call" message > > Is that maybe a timeout/connection problem? You improved something > like that in the 2.3 or 2.4 Version of LDAPUserFolder. No, this is not a timeout problem. If it was, then the exception returned by the server would tell you so. Instrument the code in the LDAPUserFolder so it writes out queries to a file, for example. You just want to find out what the last queries are before things go wrong. The goal is to take the LDAPUserFolder out of the equation and provoke this behavior with just python-ldap. jens |
|
From: Michele M. <mic...@ma...> - 2005-10-12 16:54:18
|
> Instrument the code in the LDAPUserFolder so it writes out queries to > a file, for example. You just want to find out what the last queries > are before things go wrong. The goal is to take the LDAPUserFolder out > of the equation and provoke this behavior with just python-ldap. Ok... hemm... What sould I do exactly? ;-)) I'm sorry but I've no Idea... I'm just a python beginner. Thanks, Michele -- mic...@ma... / phone: +41 44 632 6193 eth zentrum / hg g 14 / raemistrasse 101 - ch-8092 zurich !DSPAM:434d3fb2246012105311696! |
