Menu
▾
▴
python-ldap-dev
|
From: Ron T. <Ro...@US...> - 2008-04-26 03:39:29
|
Hi Michael,
I know you mentioned that I should send you more info if I get an exception.
I got a SERVER_DOWN and then retried the call manually and blew up python2.4
This is CentOS 5, python2.4.4, python-ldap 2.3.4
File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 507, in
search_s
return
self.search_ext_s(base,scope,filterstr,attrlist,attrsonly,None,None,timeout=
self.timeout)
File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 501, in
search_ext_s
return self.result(msgid,all=1,timeout=timeout)[1]
File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 427, in
result
res_type,res_data,res_msgid = self.result2(msgid,all,timeout)
File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 431, in
result2
res_type, res_data, res_msgid, srv_ctrls =
self.result3(msgid,all,timeout)
File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 437, in
result3
ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout)
File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 96, in
_ldap_call
result = func(*args,**kwargs)
ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
>>> ico.getNewUsersThatWereInvited()
python2.4: io.c:234: ber_flush2: Assertion `( (sb)->sb_opts.lbo_valid == 0x3
)' failed.
Aborted
I thought I'd send it to you incase it gives you any clues about SERVER_DOWN
which has been a royal pain!
I actually was able to reproduce this error twice. 3rd time worked.
Thanks again for all your help!
Ron
|
|
From: Michael S. <mi...@st...> - 2008-04-26 09:13:53
|
Ron Teitelbaum wrote:
>
> I know you mentioned that I should send you more info if I get an exception.
>
> I got a SERVER_DOWN and then retried the call manually and blew up python2.4
>
> This is CentOS 5, python2.4.4, python-ldap 2.3.4
> [..]
> python2.4: io.c:234: ber_flush2: Assertion `( (sb)->sb_opts.lbo_valid == 0x3
> )' failed.
> Aborted
Hmm, this is a debug message of OpenLDAP's libldap. Never saw this.
Which version of OpenLDAP is installed there? CentOS is based on Fedora?
Red Hat / Fedora is far behind with its OpenLDAP version. Any chance for
a library mix with another libldap? Could you please check which libldap
is dynamically linked? Use ldd for that.
On my system where OpenLDAP is separately compiled and installed to
prefix /opt/openldap-2.3:
# ldd /usr/lib/python/site-packages/_ldap.so
linux-gate.so.1 => (0xffffe000)
libldap_r-2.3.so.0 => /opt/openldap-2.3/lib/libldap_r-2.3.so.0
(0xb7ecf000)
liblber-2.3.so.0 => /opt/openldap-2.3/lib/liblber-2.3.so.0
(0xb7ec1000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xb7e92000)
libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb7e4f000)
libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7d08000)
libpython2.5.so.1.0 => /usr/lib/libpython2.5.so.1.0 (0xb7be7000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7bd0000)
libc.so.6 => /lib/libc.so.6 (0xb7a9d000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb7a8a000)
libdl.so.2 => /lib/libdl.so.2 (0xb7a86000)
libz.so.1 => /lib/libz.so.1 (0xb7a72000)
libutil.so.1 => /lib/libutil.so.1 (0xb7a6e000)
libm.so.6 => /lib/libm.so.6 (0xb7a49000)
/lib/ld-linux.so.2 (0x80000000)
> I thought I'd send it to you incase it gives you any clues about SERVER_DOWN
> which has been a royal pain!
It shouldn't be a problem. It works for me very often. I believe it's an
issue with your local installation.
> I actually was able to reproduce this error twice. 3rd time worked.
Strange.
Ciao, Michael.
|
|
From: Ron T. <Ro...@US...> - 2008-04-28 16:41:24
|
Hi Michael,
Yes CentOS 5 is the free version of Fedora 5,
Here is the output:
ldd libldap.so
linux-gate.so.1 => (0x002d7000)
liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00176000)
libresolv.so.2 => /lib/libresolv.so.2 (0x002f7000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0089a000)
libssl.so.6 => /lib/libssl.so.6 (0x00652000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x00416000)
libc.so.6 => /lib/libc.so.6 (0x00c0c000)
libdl.so.2 => /lib/libdl.so.2 (0x00d4e000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x0399c000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0058d000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x005bd000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00411000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0054b000)
libz.so.1 => /usr/lib/libz.so.1 (0x00101000)
/lib/ld-linux.so.2 (0x00bea000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00578000)
libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00573000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00dde000)
libsepol.so.1 => /lib/libsepol.so.1 (0x00d96000)
It looks quite different from your version.
Thanks,
Ron
> -----Original Message-----
> From: Michael Ströder
>
> Ron Teitelbaum wrote:
> >
> > I know you mentioned that I should send you more info if I get an
> exception.
> >
> > I got a SERVER_DOWN and then retried the call manually and blew up
> python2.4
> >
> > This is CentOS 5, python2.4.4, python-ldap 2.3.4
> > [..]
> > python2.4: io.c:234: ber_flush2: Assertion `( (sb)->sb_opts.lbo_valid ==
> 0x3
> > )' failed.
> > Aborted
>
> Hmm, this is a debug message of OpenLDAP's libldap. Never saw this.
> Which version of OpenLDAP is installed there? CentOS is based on Fedora?
> Red Hat / Fedora is far behind with its OpenLDAP version. Any chance for
> a library mix with another libldap? Could you please check which libldap
> is dynamically linked? Use ldd for that.
>
> On my system where OpenLDAP is separately compiled and installed to
> prefix /opt/openldap-2.3:
>
> # ldd /usr/lib/python/site-packages/_ldap.so
> linux-gate.so.1 => (0xffffe000)
> libldap_r-2.3.so.0 => /opt/openldap-2.3/lib/libldap_r-2.3.so.0
> (0xb7ecf000)
> liblber-2.3.so.0 => /opt/openldap-2.3/lib/liblber-2.3.so.0
> (0xb7ec1000)
> libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xb7e92000)
> libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb7e4f000)
> libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7d08000)
> libpython2.5.so.1.0 => /usr/lib/libpython2.5.so.1.0 (0xb7be7000)
> libpthread.so.0 => /lib/libpthread.so.0 (0xb7bd0000)
> libc.so.6 => /lib/libc.so.6 (0xb7a9d000)
> libresolv.so.2 => /lib/libresolv.so.2 (0xb7a8a000)
> libdl.so.2 => /lib/libdl.so.2 (0xb7a86000)
> libz.so.1 => /lib/libz.so.1 (0xb7a72000)
> libutil.so.1 => /lib/libutil.so.1 (0xb7a6e000)
> libm.so.6 => /lib/libm.so.6 (0xb7a49000)
> /lib/ld-linux.so.2 (0x80000000)
>
> > I thought I'd send it to you incase it gives you any clues about
> SERVER_DOWN
> > which has been a royal pain!
>
> It shouldn't be a problem. It works for me very often. I believe it's an
> issue with your local installation.
>
> > I actually was able to reproduce this error twice. 3rd time worked.
>
> Strange.
>
> Ciao, Michael.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/jav
> aone
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
|
|
From: Michael S. <mi...@st...> - 2008-04-28 15:45:04
|
Ron Teitelbaum wrote: > ldd libldap.so > linux-gate.so.1 => (0x002d7000) > liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00176000) > libresolv.so.2 => /lib/libresolv.so.2 (0x002f7000) > libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0089a000) > libssl.so.6 => /lib/libssl.so.6 (0x00652000) > libcrypto.so.6 => /lib/libcrypto.so.6 (0x00416000) > libc.so.6 => /lib/libc.so.6 (0x00c0c000) > libdl.so.2 => /lib/libdl.so.2 (0x00d4e000) > libcrypt.so.1 => /lib/libcrypt.so.1 (0x0399c000) > libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0058d000) > libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x005bd000) > libcom_err.so.2 => /lib/libcom_err.so.2 (0x00411000) > libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0054b000) > libz.so.1 => /usr/lib/libz.so.1 (0x00101000) > /lib/ld-linux.so.2 (0x00bea000) > libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00578000) > libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00573000) > libselinux.so.1 => /lib/libselinux.so.1 (0x00dde000) > libsepol.so.1 => /lib/libsepol.so.1 (0x00d96000) > > It looks quite different from your version. Well, it likely looks differently because install paths might be different. Is that listing complete? libldap(_r) seems to be missing. You should check with e.g. rpm -qf /usr/lib/liblber-2.3.so.0 if these files are part of a RPM package and of which version your OpenLDAP installation is. Hmm, another point popping up from your lib listing above: Any SE Linux policy prohibiting execution/linking of shared libs? Ciao, Michael. |
|
From: Ron T. <Ro...@US...> - 2008-04-28 16:36:00
|
Hi Michael,
Here are the results:
$ rpm -qf /usr/lib/liblber-2.3.so.0
openldap-2.3.27-8.el5_1.3
$ rpm -qf /lib/libresolv.so.2
glibc-2.5-18.el5_1.1
$ rpm -qf /usr/lib/libsasl2.so.2
cyrus-sasl-lib-2.1.22-4
$ rpm -qf /lib/libssl.so.6
openssl-0.9.8b-8.3.el5_0.2
$ rpm -qf /lib/libcrypt.so.1
glibc-2.5-18.el5_1.1
$ rpm -qf /usr/lib/libgssapi_krb5.so.2
krb5-libs-1.6.1-17.el5_1.1
$ rpm -qf /usr/lib/libkrb5.so.3
krb5-libs-1.6.1-17.el5_1.1
There is no limit on linking that I know of.
Here is a proper listing using _ldap.so. Sorry about that I did libldap.so
ldd /usr/lib/python2.4/site-packages/_ldap.so
linux-gate.so.1 => (0x00774000)
libldap_r-2.3.so.0 => /usr/lib/libldap_r-2.3.so.0 (0x002dd000)
liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x0040c000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00582000)
libssl.so.6 => /lib/libssl.so.6 (0x00b5a000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x00110000)
libpthread.so.0 => /lib/libpthread.so.0 (0x0053e000)
libc.so.6 => /lib/libc.so.6 (0x00d83000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00708000)
libdl.so.2 => /lib/libdl.so.2 (0x00243000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00247000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00275000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00322000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00832000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00f1f000)
libz.so.1 => /usr/lib/libz.so.1 (0x00a05000)
/lib/ld-linux.so.2 (0x00bea000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x002a3000)
libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x002ac000)
libselinux.so.1 => /lib/libselinux.so.1 (0x002af000)
libsepol.so.1 => /lib/libsepol.so.1 (0x004c1000)
Thanks,
Ron
> -----Original Message-----
> From: Michael Ströder [mailto:mi...@st...]
>
> Ron Teitelbaum wrote:
> > ldd libldap.so
> > linux-gate.so.1 => (0x002d7000)
> > liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00176000)
> > libresolv.so.2 => /lib/libresolv.so.2 (0x002f7000)
> > libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0089a000)
> > libssl.so.6 => /lib/libssl.so.6 (0x00652000)
> > libcrypto.so.6 => /lib/libcrypto.so.6 (0x00416000)
> > libc.so.6 => /lib/libc.so.6 (0x00c0c000)
> > libdl.so.2 => /lib/libdl.so.2 (0x00d4e000)
> > libcrypt.so.1 => /lib/libcrypt.so.1 (0x0399c000)
> > libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0058d000)
> > libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x005bd000)
> > libcom_err.so.2 => /lib/libcom_err.so.2 (0x00411000)
> > libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0054b000)
> > libz.so.1 => /usr/lib/libz.so.1 (0x00101000)
> > /lib/ld-linux.so.2 (0x00bea000)
> > libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00578000)
> > libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00573000)
> > libselinux.so.1 => /lib/libselinux.so.1 (0x00dde000)
> > libsepol.so.1 => /lib/libsepol.so.1 (0x00d96000)
> >
> > It looks quite different from your version.
>
> Well, it likely looks differently because install paths might be
> different. Is that listing complete? libldap(_r) seems to be missing.
>
> You should check with e.g.
> rpm -qf /usr/lib/liblber-2.3.so.0
> if these files are part of a RPM package and of which version your
> OpenLDAP installation is.
>
> Hmm, another point popping up from your lib listing above:
> Any SE Linux policy prohibiting execution/linking of shared libs?
>
> Ciao, Michael.
|
|
From: Michael S. <mi...@st...> - 2008-04-28 16:51:41
|
Ron Teitelbaum wrote:
>
> Here are the results:
Ron, it seems I can't help much. Did you compile python-ldap from
source? Any chance that there is a library/header mismatch between
compile and run time with other software on your system?
Also note that OpenLDAP 2.3.27 is quite old (2006/08/19) and there has
been many fixes also to libldap since then which might be important for
you. Unfortunately Red Hat does not support their OpenLDAP package very
well.
OpenLDAP 2.3's file CHANGES lists the following fixes for libldap since
2.3.27:
Fixed libldap ppolicy control creation (ITS#5103)
Fixed libldap ldap_add_result_entry (ITS#5056)
Fixed libldap referral chasing loop (ITS#4955)
Fixed libldap response code handling on rebind (ITS#4924)
Fixed libldap SASL_MAX_BUFF_SIZE (ITS#4935)
Fixed libldap cldap assert (ITS#4992)
Fixed libldap_r thread debug issues (ITS#4972)
Fixed libldap time_t signedness (ITS#4872)
Fixed libldap_r tpool reset (ITS#4855,#4899)
Fixed libldap missing get_option(TLS CipherSuite) (ITS#4815)
Fixed libldap ldap_pvt_put_filter syntax checks (ITS#4648)
Fixed libldap unchased referral leak (ITS#4545)
Fixed libldap tls callback (ITS#4723)
Fixed liblber/libldap error codes on Windows (ITS#4606)
Fixed libldap string length assert (ITS#4740)
Fixed libldap ldap.conf max line length (ITS#4669)
Fixed libldap use keepalive for syncrepl (ITS#4708)
Likely not everything is relevant for everybody but some issues look
serious in general.
Ciao, Michael.
|
|
From: Ron T. <Ro...@US...> - 2008-04-28 16:49:17
|
I'm sorry I did it wrong again.
We are running our actual server on VMWare image. I forgot to connect to
that first before checking. Here are the right values:
ldd _ldap.so
linux-gate.so.1 => (0x00d5e000)
libldap_r-2.4.so.2 => /usr/local/openldap/lib/libldap_r-2.4.so.2
(0x00bfe000)
liblber-2.4.so.2 => /usr/local/openldap/lib/liblber-2.4.so.2
(0x00ae2000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00aaf000)
libssl.so.6 => /lib/libssl.so.6 (0x00165000)
libcrypto.so.6 => /lib/libcrypto.so.6 (0x00427000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00e92000)
libc.so.6 => /lib/libc.so.6 (0x00259000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00df1000)
libdl.so.2 => /lib/libdl.so.2 (0x00111000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00115000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00143000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00d73000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x0015c000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0065d000)
libz.so.1 => /usr/lib/libz.so.1 (0x001aa000)
/lib/ld-linux.so.2 (0x0023e000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00c63000)
Sorry about that,
Ron
> -----Original Message-----
> From: Michael Ströder [mailto:mi...@st...]
> Sent: Monday, April 28, 2008 11:42 AM
> To: Ro...@US...
> Cc: pyt...@li...
> Subject: Re: Killed Python2.4
>
> Ron Teitelbaum wrote:
> > ldd libldap.so
> > linux-gate.so.1 => (0x002d7000)
> > liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00176000)
> > libresolv.so.2 => /lib/libresolv.so.2 (0x002f7000)
> > libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0089a000)
> > libssl.so.6 => /lib/libssl.so.6 (0x00652000)
> > libcrypto.so.6 => /lib/libcrypto.so.6 (0x00416000)
> > libc.so.6 => /lib/libc.so.6 (0x00c0c000)
> > libdl.so.2 => /lib/libdl.so.2 (0x00d4e000)
> > libcrypt.so.1 => /lib/libcrypt.so.1 (0x0399c000)
> > libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0058d000)
> > libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x005bd000)
> > libcom_err.so.2 => /lib/libcom_err.so.2 (0x00411000)
> > libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0054b000)
> > libz.so.1 => /usr/lib/libz.so.1 (0x00101000)
> > /lib/ld-linux.so.2 (0x00bea000)
> > libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00578000)
> > libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00573000)
> > libselinux.so.1 => /lib/libselinux.so.1 (0x00dde000)
> > libsepol.so.1 => /lib/libsepol.so.1 (0x00d96000)
> >
> > It looks quite different from your version.
>
> Well, it likely looks differently because install paths might be
> different. Is that listing complete? libldap(_r) seems to be missing.
>
> You should check with e.g.
> rpm -qf /usr/lib/liblber-2.3.so.0
> if these files are part of a RPM package and of which version your
> OpenLDAP installation is.
>
> Hmm, another point popping up from your lib listing above:
> Any SE Linux policy prohibiting execution/linking of shared libs?
>
> Ciao, Michael.
|
|
From: Michael S. <mi...@st...> - 2008-04-28 16:56:22
|
Ron Teitelbaum wrote:
> Here are the right values:
>
> ldd _ldap.so
> linux-gate.so.1 => (0x00d5e000)
> libldap_r-2.4.so.2 => /usr/local/openldap/lib/libldap_r-2.4.so.2
> (0x00bfe000)
> liblber-2.4.so.2 => /usr/local/openldap/lib/liblber-2.4.so.2
> (0x00ae2000)
Did you specify these OpenLDAP libs and the accompanying header files
correctly in your setup.cfg before invoking the build? Which exact
version of OpenLDAP is this?
Fixes to libldap mentioned in file CHANGES of not yet released
OpenLDAP 2.4.9:
Fixed libldap to use unsigned port (ITS#5436)
Fixed libldap error message for missing close paren (ITS#5458)
Fixed libldap_r tpool pause checks (ITS#5364, #5407)
Fixed libldap extended decoding (ITS#5304)
Fixed libldap filter abort (ITS#5300)
Fixed libldap ldap_parse_sasl_bind_result (ITS#5263)
Fixed libldap result codes for open (ITS#5338)
Fixed libldap search timeout crash (ITS#5291)
Fixed libldap paged results crash (ITS#5315)
Fixed libldap cipher suite with GnuTLS (ITS#5341)
Fixed libldap_r threaded library linking (ITS#4982)
Fixed libldap use of %n (ITS#5324)
Fixed liblber socket library linking (ITS#5224)
Ciao, Michael.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X