NULL result without error in PyObject_Call

[Michele M. <mic...@ma...>]

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!