Unix/Linux Go Back    


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

Sssd not starting- failed

SuSE


Tags
ldap authentication, ldapclient, openldap, sssd

Closed    
 
Thread Tools Search this Thread Display Modes
    #8  
Old Unix and Linux 03-26-2017   -   Original Discussion by Sridaran
drysdalk's Unix or Linux Image
drysdalk drysdalk is offline
Registered User
 
Join Date: Feb 2017
Last Activity: 25 May 2018, 6:09 AM EDT
Location: United Kingdom
Posts: 242
Thanks: 12
Thanked 83 Times in 73 Posts
Hi,

You shouldn't really need to try different versions of things, that's what's odd. Whatever comes as standard in the default SLES 11 SP3 repo should work. SSSD and its dependencies certainly seem to be part of the package repository from what I can see. Whatever YaST/zypper gives you should be correct for your distro, as long as you've not done anything non-standard to your configured software repos. Are you just using the default repos for your exact release of SLES, or have you customised them in any way ?
Sponsored Links
    #9  
Old Unix and Linux 03-26-2017   -   Original Discussion by Sridaran
Sridaran's Unix or Linux Image
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 there is a centralized repo server which is updated w.r.t to kernel version 3.0.101, Its not connected to SUSE. I have compared the existing glibc libraries which is lesser version compared with centralized repo.

Also, I tried below:



Code:
zypper in -f *sssd*
zypper in -f libldb1
Zypper rm *sssd* -y
zypper rm libldb1
zypper in libldb1
zypper in *sssd* -y

Still same error message.
Sponsored Links
    #10  
Old Unix and Linux 03-26-2017   -   Original Discussion by Sridaran
drysdalk's Unix or Linux Image
drysdalk drysdalk is offline
Registered User
 
Join Date: Feb 2017
Last Activity: 25 May 2018, 6:09 AM EDT
Location: United Kingdom
Posts: 242
Thanks: 12
Thanked 83 Times in 73 Posts
Hi,

Just to make sure I understand you correctly then, is it the case that your system is running different versions of the kernel and glibc compared to a default SLES 11 SP3 install ?
    #11  
Old Unix and Linux 03-26-2017   -   Original Discussion by Sridaran
Sridaran's Unix or Linux Image
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
Repo is with recently available kernel version 3.0.101-0.47.90 but the server is with older kernel which might be causing the issue?

The kernel version are available in SUSE site:
Support | Table of Kernel Versions for SUSE Linux Enterprise Server
Sponsored Links
    #12  
Old Unix and Linux 03-26-2017   -   Original Discussion by Sridaran
drysdalk's Unix or Linux Image
drysdalk drysdalk is offline
Registered User
 
Join Date: Feb 2017
Last Activity: 25 May 2018, 6:09 AM EDT
Location: United Kingdom
Posts: 242
Thanks: 12
Thanked 83 Times in 73 Posts
Hi,

I don't think the kernel is likely to be suspect here, due to the nature of the error messages you're getting. Still, you could always do an update on the system to bring all packages up to the latest available version and see if that helps.

Fundamentally, some package somewhere in the chain must not be from the same source as the others. If everything was the default SUSE packages, then you wouldn't be getting very unusual messages like this, as they're all designed to work together.

Have you upgraded or replaced any other packages on which these ones depend ? Do you have multiple instances of the same libraries on the system, maybe ? Any funny entries in /etc/ld.so.conf ? Somewhere in the dependency chain or set of packages on your system is something that doesn't belong, and it's causing issues with other things further up the chain, so to speak.

If it comes to it I suppose you could always build SSSD from source, but that would really be a solution of absolute last resort.

Last edited by drysdalk; 03-26-2017 at 05:09 PM..
The Following User Says Thank You to drysdalk For This Useful Post:
Sridaran (03-26-2017)
Sponsored Links
    #13  
Old Unix and Linux 03-26-2017   -   Original Discussion by Sridaran
Sridaran's Unix or Linux Image
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
Hi,

No upgrade has been done on other packages as far as I could see.
ld.so.conf output:



Code:
# cat /etc/ld.so.conf
/usr/X11R6/lib64/Xaw3d
/usr/X11R6/lib64
/usr/lib64/Xaw3d
/usr/X11R6/lib/Xaw3d
/usr/X11R6/lib
/usr/lib/Xaw3d
/usr/x86_64-suse-linux/lib
/usr/local/lib
/opt/kde3/lib
/lib64
/lib
/usr/lib64
/usr/lib
/usr/local/lib64
/opt/kde3/lib64
include /etc/ld.so.conf.d/*.conf

Also,



Code:
# rpm -qR sssd-1.9.4-0.26.1
pam-config
/sbin/ldconfig
/bin/sh
/bin/sh
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
/bin/sh
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.8)(64bit)
libcares.so.2()(64bit)
libcollection.so.2()(64bit)
libcom_err.so.2()(64bit)
libcrypto.so.0.9.8()(64bit)
libdbus-1.so.3()(64bit)
libdhash.so.1()(64bit)
libdl.so.2()(64bit)
libdl.so.2(GLIBC_2.2.5)(64bit)
libglib-2.0.so.0()(64bit)
libini_config.so.2()(64bit)
libk5crypto.so.3()(64bit)
libkeyutils.so.1()(64bit)
libkeyutils.so.1(KEYUTILS_0.3)(64bit)
libkrb5.so.3()(64bit)
libkrb5.so.3(krb5_3_MIT)(64bit)
liblber-2.4.so.2()(64bit)
libldap-2.4.so.2()(64bit)
libldb.so.1()(64bit)
libnl.so.1()(64bit)
libpam.so.0()(64bit)
libpam.so.0(LIBPAM_1.0)(64bit)
libpam.so.0(LIBPAM_EXTENSION_1.0)(64bit)
libpam.so.0(LIBPAM_MODUTIL_1.0)(64bit)
libpcre.so.0()(64bit)
libpopt.so.0()(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
libpthread.so.0(GLIBC_2.4)(64bit)
libresolv.so.2()(64bit)
libsss_idmap.so.0()(64bit)
libtalloc.so.2()(64bit)
libtdb.so.1()(64bit)
libtevent.so.0()(64bit)
libz.so.1()(64bit)
rpmlib(PayloadIsLzma) <= 4.4.6-1

strace output:



Code:
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1, 0x7fffe42dad64, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn(0xffffffffffffffff)        = 0
rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER|SA_RESTART, 0x7f05893529e0}, {0x4356f0, [], SA_RESTORER|SA_RESTART, 0x7f05893529e0}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
fcntl(1, F_GETFD)                       = 0
fcntl(1, F_DUPFD, 10)                   = 10
fcntl(1, F_GETFD)                       = 0
fcntl(10, F_SETFD, FD_CLOEXEC)          = 0
close(1)                                = 0
dup2(2, 1)                              = 1
fcntl(2, F_GETFD)                       = 0
write(1, "\0337\33[?25l\r\33[155C\33[10D\33[1;31mfaile"..., 46                                                                                  failed
) = 46
close(1)                                = 0
dup2(10, 1)                             = 1
fcntl(10, F_GETFD)                      = 0x1 (flags FD_CLOEXEC)
close(10)                               = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
read(255, "rc_exit\n\n", 1785)          = 9
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
exit_group(7)                           = ?

So, better to update the packages excluding kernel?
Sponsored Links
    #14  
Old Unix and Linux 03-27-2017   -   Original Discussion by Sridaran
bakunin's Unix or Linux Image
bakunin bakunin is offline Forum Staff  
Bughunter Extraordinaire
 
Join Date: May 2005
Last Activity: 23 June 2018, 2:50 AM EDT
Location: In the leftmost byte of /dev/kmem
Posts: 5,782
Thanks: 112
Thanked 1,698 Times in 1,248 Posts
I am by no means a SuSE-expert but this:

Quote:
Originally Posted by Sridaran View Post


Code:
# rpm -Vv libldb1-3.6.3-64.1
........ /usr/lib64/ldb
........ /usr/lib64/ldb/asq.so
seems not to align all too well with this:

Quote:
Originally Posted by Sridaran View Post


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
Might it be that there is a 32-bit/64-bit mismatch in oyur libraries and application programs?

I hope this helps.

bakunin
The Following User Says Thank You to bakunin For This Useful Post:
Sridaran (03-27-2017)
Sponsored Links
Closed

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Linux 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 04:10 PM.