[Bug 1684295] Re: sssd fails with 'Exiting the SSSD. Could not restart critical service [tpad].

[Andreas Hasenack]

It's only xenial that is affected, that is, version 1.13.4 and perhaps
earlier. Trusty, zesty and higher are OK.

** Description changed:

- This is Ubuntu 16.04.2 LTS
+ [Impact]
  
- sssd is configured to connect to two domains, our TPAD directory and
- Active Directory.  sssd starts up at boot time.  As soon as I ssh login
- (with any id, AD, TPAD or local), sssd fails with the error message in
- the title. After that, we can only login with local ids, not TPAD or AD
- ids.
+  * An explanation of the effects of the bug on users and
  
- ****************
- Here is the output from systemctl status sssd after the failure:
- root at dcmilphlum128:~# systemctl status sssd
- â sssd.service - System Security Services Daemon
-    Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled)
-    Active: failed (Result: exit-code) since Wed 2017-04-19 16:40:08 EDT; 7min ago
-   Process: 119143 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
-  Main PID: 119145 (code=exited, status=1/FAILURE)
+  * justification for backporting the fix to the stable release.
  
- Apr 19 16:39:47 dcmilphlum128.edc.nam.gm.com sssd[be[119187]: Starting up
- Apr 19 16:39:51 dcmilphlum128.edc.nam.gm.com sssd[be[119191]: Starting up
- Apr 19 16:39:57 dcmilphlum128.edc.nam.gm.com sssd[be[119206]: Starting up
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com sssd[119145]: Exiting the SSSD. Could not restart critical service [tpad].
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com sssd[119149]: Shutting down
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com sssd[119148]: Shutting down
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com sssd[be[119146]: Shutting down
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com systemd[1]: sssd.service: Unit entered failed state.
- Apr 19 16:40:08 dcmilphlum128.edc.nam.gm.com systemd[1]: sssd.service: Failed with result 'exit-code'.
+  * In addition, it is helpful, but not required, to include an
+    explanation of how the upload fixes this bug.
  
- ******************
- Also, in kern.log I have four of these (I have retries set to 3):
- Apr 19 16:39:59 dcmilphlum128 kernel: [ 6205.937807] sssd_be[12218]: segfault at 0 ip 00007fecb32b6b94 sp 00007ffce49a2230 error 4 in libsss_util.so[7fecb32a2000+6c000]
- Apr 19 16:40:02 dcmilphlum128 kernel: [ 6206.980725] sssd_be[12253]: segfault at 0 ip 00007f302de29b94 sp 00007fffca943cc0 error 4 in libsss_util.so[7f302de15000+6c000]
- Apr 19 16:40:05 dcmilphlum128 kernel: [ 6211.036205] sssd_be[12256]: segfault at 0 ip 00007fd196169b94 sp 00007ffd624249f0 error 4 in libsss_util.so[7fd196155000+6c000]
- Apr 19 16:40:07 dcmilphlum128 kernel: [ 6225.081902] sssd_be[12257]: segfault at 0 ip 00007fd1f669bb94 sp 00007ffdd8e5bf80 error 4 in libsss_util.so[7fd1f6687000+6c000]
+ [Test Case]
  
- *******************
- My sssd package are at 1.13.4:
- sssd                               1.13.4-1ubuntu1.1               amd64        
- sssd-ad                            1.13.4-1ubuntu1.1               amd64        
- sssd-ad-common                     1.13.4-1ubuntu1.1               amd64        
- sssd-common                        1.13.4-1ubuntu1.1               amd64        
- sssd-ipa                           1.13.4-1ubuntu1.1               amd64        
- sssd-krb5                          1.13.4-1ubuntu1.1               amd64        
- sssd-krb5-common                   1.13.4-1ubuntu1.1               amd64        
- sssd-ldap                          1.13.4-1ubuntu1.1               amd64        
- sssd-proxy                         1.13.4-1ubuntu1.1               amd64        
- sssd-tools                         1.13.4-1ubuntu1.1               amd64        
+  * detailed instructions how to reproduce the bug
  
- ***************
- I upgraded all the sssd packages to 1.13.4-1ubuntu1.4 and had the same problem.
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
  
- I downgraded them to 1.12.5-2 and was NOT able to reproduce the problem.
+ [Regression Potential]
  
- I attached my sssd.conf file.
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
+  * and address these questions in advance

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1684295

Title:
  sssd fails with 'Exiting the SSSD.  Could not restart critical service
  [tpad].

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1684295/+subscriptions