[Freeipa-users] SSS problems with eDirectory

Sumit Bose sbose at redhat.com
Thu Jul 22 21:24:34 UTC 2010


On Thu, Jul 22, 2010 at 04:19:53PM -0400, Scott Duckworth wrote:
> On Thu, Jul 22, 2010 at 12:38 PM, Stephen Gallagher <sgallagh at redhat.com>wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 07/22/2010 11:47 AM, Scott Duckworth wrote:
> > >
> > > "yum localinstall libcollection-0.5.0-21.fc14.*
> > > libini_config-0.6.0-21.fc14.* sssd-1.2.91-21.fc14.*
> > > sssd-client-1.2.91-21.fc14.*" requires python 2.7.  Adding
> > > python-2.7-3.fc14.* and python-libs-2.7-3.fc14.* results in a slew of
> > > dependency resolution errors.
> > >
> > > If I get the chance in the few days, I'll try it under rawhide.
> > >
> >
> > Sorry, that was the wrong package. Please try:
> > http://koji.fedoraproject.org/koji/buildinfo?buildID=182852
> >
> > The one Sumit sent you mistakenly was from an in-progress rebuild of
> > python for Fedora 14. This one uses Python 2.6 and should install
> > cleanly on Fedora 13.
> >
> 
> Updated:
> 
> [root at duck2 ~]# rpm -qa | grep fc14 | sort
> libcollection-0.5.0-20.fc14.i686
> libcollection-0.5.0-20.fc14.x86_64
> libdhash-0.4.0-20.fc14.i686
> libdhash-0.4.0-20.fc14.x86_64
> libini_config-0.6.0-20.fc14.i686
> libini_config-0.6.0-20.fc14.x86_64
> libpath_utils-0.2.0-20.fc14.i686
> libpath_utils-0.2.0-20.fc14.x86_64
> libref_array-0.1.0-20.fc14.i686
> libref_array-0.1.0-20.fc14.x86_64
> sssd-1.2.91-20.fc14.x86_64
> sssd-client-1.2.91-20.fc14.i686
> sssd-client-1.2.91-20.fc14.x86_64
> 
> But I'm still having the same issue.
> 
> (Thu Jul 22 16:12:49 2010) [sssd[be[CLEMSONU]]] [simple_bind_send] (4):
> Executing simple bind as: cn=SDUCKWO,ou=s,ou=EMPLOYEE,o=CLEMSONU
> (Thu Jul 22 16:12:49 2010) [sssd[be[CLEMSONU]]] [simple_bind_send] (8): ldap
> simple bind sent, msgid = 2

So the next line in the log still looks like:

(Wed Jul 21 12:32:24 2010) [sssd[be[CLEMSONU]]] [sdap_process_result] (4):
ldap_result gave -1, something bad happend!

?

> 
> I have a feeling that a real LDAP error message would provide more insight
> into the situation.

Can you find anything in the server logs?

I can prepare a special build for you which prints the
LDAP_OPT_DIAGNOSTIC_MESSAGE LDAP option and let you use wireshark. But
I'm afraid this has to wait until tomorrow, it's nearly half to
midnight, here.

bye,
Sumit


> 
> - --
> > Stephen Gallagher
> > RHCE 804006346421761
> >
> > Delivering value year after year.
> > Red Hat ranks #1 in value among software vendors.
> > http://www.redhat.com/promo/vendor/
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.14 (GNU/Linux)
> > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
> >
> > iEYEARECAAYFAkxIdB8ACgkQeiVVYja6o6MpMQCfch5jTZlOHvuWaBNePVFVLK7s
> > Fg4AoItYQ6rNj8lwxwLb0pSgZfYdzhtL
> > =jdnq
> > -----END PGP SIGNATURE-----
> >
> > _______________________________________________
> > Freeipa-users mailing list
> > Freeipa-users at redhat.com
> > https://www.redhat.com/mailman/listinfo/freeipa-users
> >




More information about the Freeipa-users mailing list