Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1187113 - sssd deamon was not running after RHEL 7.1 upgrade.
sssd deamon was not running after RHEL 7.1 upgrade.
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd (Show other bugs)
7.1
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: SSSD Maintainers
Kaushik Banerjee
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-01-29 06:31 EST by Nirupama Karandikar
Modified: 2016-05-05 00:36 EDT (History)
13 users (show)

See Also:
Fixed In Version: sssd-1.12.2-58.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 05:35:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0441 normal SHIPPED_LIVE sssd bug fix and enhancement update 2015-03-05 10:05:27 EST

  None (edit)
Description Nirupama Karandikar 2015-01-29 06:31:25 EST
Description of problem:
sssd deamon was not running after RHEL 7.1 upgrade.

Version-Release number of selected component (if applicable):
sssd-1.12.2-52.el7.x86_64

How reproducible:
Always

Steps to Reproduce:

1. Install RHEL 7.0 fresh VM.

# rpm -q sssd
sssd-1.11.2-65.el7.x86_64

2. Join system to windows 2012 AD.

3. User/group lookup and Auth was working correctly.

4. Upgrade the whole system to fro RHEL 7.0 to RHEL 7.1.

# yum update 

5. After upgrade sssd service was not running.

# systemctl status sssd.service 
sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
  Drop-In: /etc/systemd/system/sssd.service.d
           └─journal.conf
   Active: failed (Result: exit-code) since Wed 2015-01-28 16:52:12 IST; 24h ago
 Main PID: 671 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/sssd.service

Jan 28 16:52:05 dhcp207-65.lab.eng.pnq.redhat.com systemd[1]: Starting System Security Services Daemon...
Jan 28 16:52:05 dhcp207-65.lab.eng.pnq.redhat.com sssd[8801]: Starting up
Jan 28 16:52:06 dhcp207-65.lab.eng.pnq.redhat.com sssd[be[sssdad2012.com]][8802]: Starting up
Jan 28 16:52:12 dhcp207-65.lab.eng.pnq.redhat.com sssd[be[sssdad2012.com]][8809]: Starting up
Jan 28 16:52:12 dhcp207-65.lab.eng.pnq.redhat.com systemd[1]: sssd.service: control process exited, code=exited status=1
Jan 28 16:52:12 dhcp207-65.lab.eng.pnq.redhat.com systemd[1]: Failed to start System Security Services Daemon.
Jan 28 16:52:12 dhcp207-65.lab.eng.pnq.redhat.com systemd[1]: Unit sssd.service entered failed state.

6. From domian log.

(Wed Jan 28 16:52:12 2015) [sssd[be[sssdad2012.com]]] [sbus_new_server] (0x0400): D-BUS Server listening on unix:path=/var/lib/sss/pipes/private/sbus-dp_sssdad2012.com.8809,guid=3d0f7d0339b3ceb8272864c054c8c664
(Wed Jan 28 16:52:12 2015) [sssd[be[sssdad2012.com]]] [sbus_add_watch] (0x2000): 0x7f82e7fdca80/0x7f82e7fde200 (16), R/- (enabled)
(Wed Jan 28 16:52:12 2015) [sssd[be[sssdad2012.com]]] [load_backend_module] (0x1000): Loading backend [ad] with path [/usr/lib64/sssd/libsss_ad.so].
(Wed Jan 28 16:52:12 2015) [sssd[be[sssdad2012.com]]] [load_backend_module] (0x0010): Unable to load ad module with path (/usr/lib64/sssd/libsss_ad.so), error: /usr/lib64/samba/libreplace.so: version `SAMBA_4.1.1' not found (required by /lib64/libwbclient.so.0)


Actual results:
 
After upgrade sssd service was not running.

# systemctl status sssd.service 
sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
  Drop-In: /etc/systemd/system/sssd.service.d
           └─journal.conf
   Active: failed (Result: exit-code) since Wed 2015-01-28 16:52:12 IST; 24h ago
 Main PID: 671 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/sssd.service

Expected results:
sssd service should be running

Additional info:
If you manually do "systemctl start sssd.service", it works fine.
Comment 1 Lukas Slebodnik 2015-01-29 06:50:02 EST
Could you provide output of commands after uprade?
  rpm -qa *libwbclient*
  update-alternatives --display libwbclient.so.0.11-64
Comment 2 Nirupama Karandikar 2015-01-29 06:58:17 EST
Hi,

Here is the requested details,

# rpm -qa *libwbclient*
libwbclient-4.1.12-18.el7.x86_64

#  update-alternatives --display libwbclient.so.0.11-64
libwbclient.so.0.11-64 - status is auto.
 link currently points to /usr/lib64/samba/wbclient/libwbclient.so.0.11
/usr/lib64/samba/wbclient/libwbclient.so.0.11 - priority 10
Current `best' version is /usr/lib64/samba/wbclient/libwbclient.so.0.11.

Niru
Comment 6 Jenny Galipeau 2015-01-30 12:22:16 EST
Hopefully this will resolve the dependency issues customers will see when trying to install ..

=== InstallTest =====================
Install test FAILED
Output from RPM Command:
error: Failed dependencies:
	libwbclient-devel < 4.1.12 conflicts with sssd-libwbclient-devel-1.12.2-56.el7.ppc64
	libwbclient < 4.1.12 conflicts with sssd-libwbclient-1.12.2-56.el7.ppc64
	libwbclient-devel < 4.1.12 conflicts with sssd-libwbclient-devel-1.12.2-56.el7.ppc
Comment 7 Sumit Bose 2015-01-30 12:43:36 EST
The current samba/libwbclient version is samba-4.1.12-18.el7. If you call 'yum update sssd' if will pull the newer samba/libwbclient version as well. You cannot update sssd without updating the needed dependencies as well.
Comment 8 Kaushik Banerjee 2015-01-30 16:20:49 EST
Upgrade still did not work. sssd stopped after upgrade from 7.0 to 7.1(sssd-1.12.2-56).

# cat /var/log/yum.log | grep Updated | grep samba
Jan 31 02:27:45 Updated: samba-libs-4.1.12-18.el7.x86_64
Jan 31 02:27:46 Updated: samba-common-4.1.12-18.el7.x86_64
# cat /var/log/yum.log | grep Updated | grep libwbclient
Jan 31 02:27:46 Updated: libwbclient-4.1.12-18.el7.x86_64
# cat /var/log/yum.log | grep Updated | grep sssd
Jan 31 02:27:53 Updated: sssd-client-1.12.2-56.el7.x86_64
Jan 31 02:28:34 Updated: sssd-krb5-common-1.12.2-56.el7.x86_64
Jan 31 02:28:34 Updated: sssd-common-1.12.2-56.el7.x86_64
Jan 31 02:28:35 Updated: sssd-common-pac-1.12.2-56.el7.x86_64
Jan 31 02:28:35 Updated: sssd-ipa-1.12.2-56.el7.x86_64
Jan 31 02:28:35 Updated: sssd-ad-1.12.2-56.el7.x86_64
Jan 31 02:28:35 Updated: sssd-krb5-1.12.2-56.el7.x86_64
Jan 31 02:28:36 Updated: sssd-proxy-1.12.2-56.el7.x86_64
Jan 31 02:28:36 Updated: sssd-ldap-1.12.2-56.el7.x86_64
Jan 31 02:28:44 Updated: python-sssdconfig-1.12.2-56.el7.noarch
Jan 31 02:28:45 Updated: sssd-1.12.2-56.el7.x86_64


The domain log shows:
(Sat Jan 31 02:30:56 2015) [sssd[be[sssdad2012.com]]] [load_backend_module] (0x0010): Unable to load ad module with path (/usr/lib64/sssd/libsss_ad.so), error: libwbclient.so.0: cannot open shared object file: No such file or directory
(Sat Jan 31 02:30:56 2015) [sssd[be[sssdad2012.com]]] [be_process_init] (0x0010): fatal error initializing data providers
(Sat Jan 31 02:30:56 2015) [sssd[be[sssdad2012.com]]] [main] (0x0010): Could not initialize backend [79]
Comment 10 Jakub Hrozek 2015-02-03 08:45:53 EST
Here is what happens -- we are switching to alternatives with some sssd dependencies (libwbclient) so we need both samba and sssd to be in a consistent state when sssd is restarted.

However, some service (I haven't figured out which one yet, but looks like systemd) causes sssd to be restarted in the middle of the transaction, which fails. Then, when the try-restart is run, the sssd is not running, so the try-restart doesn't even try.
Comment 12 Nirupama Karandikar 2015-02-04 05:32:42 EST
Tested with sssd-1.12.2-58.el7.x86_64

1. Insatll RHEL 7.0 VM with minimal install.

2. Configured RHEL 7.0 repo.

3. To check GUI logins install GUI on the system.

# yum groupinstall "Server with GUI"

Reboot

4. Join system to AD domain. Check user lookup and Auth and GUI Login.

# getent passwd kau12@sssdad2012.com
kau12@sssdad2012.com:*:781329014:781200513:kau12:/home/sssdad2012.com/kau12:/bin/bash

# ssh -l kau1@sssdad2012.com localhost
kau1@sssdad2012.com@localhost's password: 
Last login: Wed Feb  4 15:25:46 2015 from localhost
[kau1@sssdad2012.com@dhcp207-122 ~]$ 

5. Do whole system upgrade.

# yum update

6. Once upgrade done. Recheck sssd service status

# systemctl status  sssd.service
sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
  Drop-In: /etc/systemd/system/sssd.service.d
           └─journal.conf
   Active: active (running) since Wed 2015-02-04 15:49:40 IST; 21min ago
  Process: 27524 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
 Main PID: 27525 (sssd)
   CGroup: /system.slice/sssd.service
           ├─27525 /usr/sbin/sssd -D -f
           ├─27526 /usr/libexec/sssd/sssd_be --domain sssdad2012.com --uid 0 --gid 0 --debug-to-files
           ├─27527 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --debug-to-files
           └─27528 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --debug-to-files

7. Check user lookup and Auth. Also checked GUI login which works fine.

# getent passwd kau12@sssdad2012.com
kau12@sssdad2012.com:*:781329014:781200513:kau12:/home/sssdad2012.com/kau12:/bin/bash

# ssh -l kau1@sssdad2012.com localhost
kau1@sssdad2012.com@localhost's password: 
Last login: Wed Feb  4 15:25:46 2015 from localhost
[kau1@sssdad2012.com@dhcp207-122 ~]$ 

Upgrade works fine.
Comment 14 errata-xmlrpc 2015-03-05 05:35:25 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0441.html

Note You need to log in before you can comment on or make changes to this bug.