Comment 5 for bug 1684295

Pamela Skutnik (pam-s) wrote :

Sorry, finally got back to working on this. Can I continue to post here or do I need to reopen?

I have set up a test server configured with only the one domain, tpad.
I also updated the sssd packages to 1.13.4-1ubuntu1.8, the highest I had.
It still crashes as soon as I login with any id (local or tpad).

root@dcmilphlum127:~# 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-10-04 15:52:08 EDT; 24min ago
  Process: 13480 ExecStart=/usr/sbin/sssd -i -f (code=exited, status=1/FAILURE)
 Main PID: 13480 (code=exited, status=1/FAILURE)

Oct 04 15:50:48 systemd[1]: Started System Security Services Daemon.
Oct 04 15:51:49 sssd[be[13528]: Starting up
Oct 04 15:51:52 sssd[be[13530]: Starting up
Oct 04 15:51:58 sssd[be[13531]: Starting up
Oct 04 15:52:08 sssd[13480]: Exiting the SSSD. Could not restart critical service [tpad].
Oct 04 15:52:08 sssd[13484]: Shutting down
Oct 04 15:52:08 sssd[13483]: Shutting down
Oct 04 15:52:08 systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE
Oct 04 15:52:08 systemd[1]: sssd.service: Unit entered failed state.
Oct 04 15:52:08 systemd[1]: sssd.service: Failed with result 'exit-code'.

root@dcmilphlum127:~# tail /var/log/all/kern.log

Oct 4 15:51:50 dcmilphlum127 kernel: [ 6814.060738] sssd_be[13528]: segfault at 0 ip 00007f302c49db94 sp 00007fff0b589cb0 error 4 in[7f302c489000+6c000]
Oct 4 15:51:54 dcmilphlum127 kernel: [ 6818.117855] sssd_be[13530]: segfault at 0 ip 00007f6e98ac0b94 sp 00007fffc35cae40 error 4 in[7f6e98aac000+6c000]
Oct 4 15:52:08 dcmilphlum127 kernel: [ 6832.177545] sssd_be[13531]: segfault at 0 ip 00007fb2b6ccdb94 sp 00007fff392e1e00 error 4 in[7fb2b6cb9000+6c000]

I attached my modified sssd.conf file.