×
UNIX.COM Login
Username:
Password:  
Show Password






👤


SuSE

SUSE Linux is a major operating system. The developer rights are owned by Novell, Inc.

Sssd not starting- failed

ldap authentication, ldapclient, openldap, sssd

👤 Login to reply
 
Thread Tools Search this Thread Display Modes
    #1  
Old 03-25-2017
Sridaran Sridaran is offline
Registered User
 
Join Date: Jul 2016
Last Activity: 27 March 2017, 10:29 AM EDT
Location: Bangalore
Posts: 15
Thanks: 6
Thanked 0 Times in 0 Posts
Sssd not starting- failed

Hi,

I am unable to start sssd as its getting failed with below error.

[CODE]OS: SLES 11
Version: 3

Code:
# uname -r
2.6.32.59-0.7-default

Code:
# sssd -d4
ldb: unable to dlopen /usr/lib64/ldb/tdb.so : /usr/lib64/ldb/tdb.so: undefined symbol: tdb_transaction_prepare_commit

Code:
# /etc/init.d/sssd restart
Shutting down sssd done
Starting sssd failed

Code:
# rpm -qf /usr/lib64/ldb/tdb.so
libldb1-3.6.3-64.1

Code:
# rpm -Vv libldb1-3.6.3-64.1
........ /usr/lib64/ldb
........ /usr/lib64/ldb/asq.so
........ /usr/lib64/ldb/ldap.so
........ /usr/lib64/ldb/libldb-cmdline.so
........ /usr/lib64/ldb/paged_results.so
........ /usr/lib64/ldb/paged_searches.so
........ /usr/lib64/ldb/rdn_name.so
........ /usr/lib64/ldb/sample.so
........ /usr/lib64/ldb/server_sort.so
........ /usr/lib64/ldb/skel.so
........ /usr/lib64/ldb/tdb.so
........ /usr/lib64/libldb.so.1
........ /usr/lib64/libldb.so.1.0.2
........ /usr/lib64/libpyldb-util.so.1
........ /usr/lib64/libpyldb-util.so.1.0.2
~:/var/lib #

Could anyone help on this?

Regards,
Sridaran G


Moderator's Comments:
Sssd not starting- failed Please use CODE tags as required by forum rules!

Last edited by Sridaran; 03-26-2017 at 03:40 AM.. Reason: Added CODE tags.
Sponsored Links
    #2  
Old 03-25-2017
drysdalk drysdalk is offline
Registered User
 
Join Date: Feb 2017
Last Activity: 16 July 2018, 11:20 AM EDT
Location: United Kingdom
Posts: 242
Thanks: 12
Thanked 83 Times in 73 Posts
Hi,

I would start by looking at the install of SSSD itself. This seems to imply that there is some kind of version mismatch between the functionaltiy that tdb.so is able to provide, and the functionality that your SSSD installation expects it to provide.

How was SSSD installed ? Are you sure the packages are absolutely correct for your version of SLES and libldb ? If you run the ld command on the sssd binary, what output do you get ? My suspicion is that the package or source you've installed SSSD from doesn't quite match the versions of the pre-requisites that are in fact installed on your system.
The Following User Says Thank You to drysdalk For This Useful Post:
Sridaran (03-26-2017)
Sponsored Links
    #3  
Old 03-25-2017
jim mcnamara jim mcnamara is offline Forum Staff  
...@...
 
Join Date: Feb 2004
Last Activity: 16 July 2018, 11:10 PM EDT
Location: NM
Posts: 11,439
Thanks: 637
Thanked 1,176 Times in 1,082 Posts
ld or ldd? I think ldd might be more useful to list expected shared library versions.
The Following 2 Users Say Thank You to jim mcnamara For This Useful Post:
drysdalk (03-25-2017), Sridaran (03-26-2017)
    #4  
Old 03-25-2017
drysdalk drysdalk is offline
Registered User
 
Join Date: Feb 2017
Last Activity: 16 July 2018, 11:20 AM EDT
Location: United Kingdom
Posts: 242
Thanks: 12
Thanked 83 Times in 73 Posts
Hi,

Sorry, yes - quite right. I'm not having a good day today !
Sponsored Links
    #5  
Old 03-26-2017
Sridaran Sridaran is offline
Registered User
 
Join Date: Jul 2016
Last Activity: 27 March 2017, 10:29 AM EDT
Location: Bangalore
Posts: 15
Thanks: 6
Thanked 0 Times in 0 Posts
Hello,

Thanks alot for the reply.
Even I was checking for the respective kernel version package and tried installing different sssd version but no luck.

Code:
# rpm -qa |grep -i sssd
python-sssd-config-1.9.4-0.26.1
sssd-32bit-1.9.4-0.26.1
sssd-tools-1.9.4-0.26.1
sssd-1.9.4-0.26.1

ldd output:
Code:
# ldd /usr/sbin/sssd
        linux-vdso.so.1 =>  (0x00007fff612a5000)
        libnl.so.1 => /lib64/libnl.so.1 (0x00007f3c7b52a000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f3c7b327000)
        libtevent.so.0 => /usr/lib64/libtevent.so.0 (0x00007f3c7b11a000)
        libtalloc.so.2 => /usr/lib64/libtalloc.so.2 (0x00007f3c7af0f000)
        libpopt.so.0 => /lib64/libpopt.so.0 (0x00007f3c7ad06000)
        libldb.so.1 => /usr/lib64/libldb.so.1 (0x00007f3c7aadb000)
        libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f3c7a89d000)
        libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f3c7a66d000)
        libini_config.so.2 => /usr/lib64/libini_config.so.2 (0x00007f3c7a463000)
        libcollection.so.2 => /usr/lib64/libcollection.so.2 (0x00007f3c7a257000)
        libdhash.so.1 => /usr/lib64/libdhash.so.1 (0x00007f3c7a053000)
        liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f3c79e43000)
        libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f3c79bfa000)
        libtdb.so.1 => /usr/lib64/libtdb.so.1 (0x00007f3c799ec000)
        libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f3c79725000)
        libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007f3c79386000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f3c79182000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f3c78f6b000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f3c78c0d000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f3c789b7000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f3c787ad000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f3c78572000)
        libpath_utils.so.1 => /usr/lib64/libpath_utils.so.1 (0x00007f3c7836e000)
        libref_array.so.1 => /usr/lib64/libref_array.so.1 (0x00007f3c7816a000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f3c77f53000)
        libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f3c77d38000)
        libssl.so.0.9.8 => /usr/lib64/libssl.so.0.9.8 (0x00007f3c77ae1000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f3c7b7b1000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f3c778c4000)



Regards,
Sridaran

Last edited by Don Cragun; 03-26-2017 at 03:33 AM.. Reason: Add CODE and ICODE tags again.
Sponsored Links
    #6  
Old 03-26-2017
drysdalk drysdalk is offline
Registered User
 
Join Date: Feb 2017
Last Activity: 16 July 2018, 11:20 AM EDT
Location: United Kingdom
Posts: 242
Thanks: 12
Thanked 83 Times in 73 Posts
Hi,

The major version numbers of your packages seem to be what they should be for SLES 11 SP3, from what I can tell by looking at the relevant Web pages. Could you try completely un-installing all SSSD-related packages, and reinstalling them again from the main SLES package repo for SLES 11 SP3 ?
The Following User Says Thank You to drysdalk For This Useful Post:
Sridaran (03-26-2017)
Sponsored Links
    #7  
Old 03-26-2017
Sridaran Sridaran is offline
Registered User
 
Join Date: Jul 2016
Last Activity: 27 March 2017, 10:29 AM EDT
Location: Bangalore
Posts: 15
Thanks: 6
Thanked 0 Times in 0 Posts
Yes I have tried removing all the sssd packages below and tried reinstalling the grater version and lowerversion but still no luck.....

I guess as you mentioned we have to find the relevant version of sssd with respect to libldb1 version.

Code:
sssd-32bit-1.9.4-0.26.1
sssd-tools-1.9.4-0.26.1
sssd-1.9.4-0.26.1
libsss

Sponsored Links
👤 Login to reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
How to grep a line not starting with # from a file (there are two lines starting with # and normal)? Tanu UNIX for Dummies Questions & Answers 3 05-31-2016 04:33 PM
Authenticating with SSSD / Kerberos against Windows Server 2012 R2 Devyn UNIX for Advanced & Expert Users 2 09-04-2015 11:11 AM
Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display HarishKumarM Solaris 3 12-02-2010 03:44 PM
SFTP Failed---Request for subsystem 'sftp' failed on channel 0 mahiban AIX 0 07-25-2008 02:51 AM
Starting X? AMDPwred UNIX for Dummies Questions & Answers 2 03-14-2002 11:07 AM



All times are GMT -4. The time now is 05:39 AM.

Unix & Linux Forums Content Copyrightę1993-2018. All Rights Reserved.