Bug 783935

Would you please set debug_level = 4 in both the [sssd] section and [domain/MYDOMAIN] section of /etc/sssd/sssd.conf, restart SSSD and reproduce the error? Then attach /var/log/sssd/sssd.log and /var/log/sssd/sssd_MYDOMAIN.log (sanitized as needed) as private attachments to this bug?

Also, could you please use ABRT to report the crash, so we can get the backtrace and identify what's causing it.

I was waiting for this to happen again but it didn't till now. Main problem here is that module sssd[be[MYDOMAIN]] is not being reset correctly after crash. When I reported this for the first time only sssd[pam] was being restarted after crash now it looks that something was fixed since also sssd[nss] is rebooting according to logs (question is why this is happening 4 times for pam and nss modules? see logs above from Jan 21 23:32:00 and Jan 22 01:02:00 and why between pam module reset and nss module reset there is 1.5 hour gap ? )

I just realized that I put wrong link to the bug in my first post. It should be:

https://bugzilla.redhat.com/show_bug.cgi?id=740501

So those are logs from sssd 1.5.1-34.el6_1.3.x86_64

Oct 11 10:07:28 MYSERVER sssd[be[MYDOMAIN]]: Shutting down
Oct 11 10:07:28 MYSERVER  sssd[be[MYDOMAIN]]: Starting up
Oct 11 10:07:40 MYSERVER  sssd[nss]: Starting up
Oct 11 10:07:41 MYSERVER  sssd[nss]: Starting up
Oct 11 10:07:42 MYSERVER  sssd[nss]: Starting up
Oct 11 10:07:43 MYSERVER  sssd[nss]: Starting up

and those after crash when I' on version 1.5.1-66.el6_2.1.x86_64
Jan 21 23:31:27 hostname sssd[pam]: Shutting down
Jan 21 23:31:29 hostname sssd[be[MYDOMAIN]]: Shutting down
Jan 21 23:32:29 hostname sssd[pam]: Starting up
Jan 21 23:32:30 hostname sssd[pam]: Starting up
Jan 21 23:32:31 hostname sssd[pam]: Starting up
Jan 21 23:32:32 hostname sssd[pam]: Starting up
Jan 22 01:02:52 hostname sssd[nss]: Starting up
Jan 22 01:02:53 hostname sssd[nss]: Starting up
Jan 22 01:02:54 hostname sssd[nss]: Starting up
Jan 22 01:02:55 hostname sssd[nss]: Starting up

Upstream ticket:
https://fedorahosted.org/sssd/ticket/1154

Kemot1000, I requested in Comment #2 two pieces of information: the SSSD logs and the ABRT backtraces. Without that information, there is nothing I can do to help you.

All you're seeing in /var/log/messages is our automatic restart after an error. We try four times and then give up.

In addition to the information I mentioned in Comment #2, please also add debug_level = 4 to the [nss] and [pam] sections and include /var/log/sssd_nss.log and /var/log/sssd_pam.log.

Furthermore, please check /var/log/audit/audit.log for any SELinux denials that may have occurred at the same timestamp as those /var/log/messages "Starting up" lines.

I setup debug_level = 4 on all parts of sssd.conf. Will post output once I get this error again.

(In reply to comment #6)
> All you're seeing in /var/log/messages is our automatic restart after an error.
> We try four times and then give up.

Why there is such a long time between sssd[pam] restart and sssd[nss] (this has not been sanitized this is how I see those in the log with 1.5 hour gap)

> Jan 21 23:32:32 hostname sssd[pam]: Starting up
> Jan 22 01:02:52 hostname sssd[nss]: Starting up

(In reply to comment #7)
> I setup debug_level = 4 on all parts of sssd.conf. Will post output once I get
> this error again.
> 
> (In reply to comment #6)
> > All you're seeing in /var/log/messages is our automatic restart after an error.
> > We try four times and then give up.
> 
> Why there is such a long time between sssd[pam] restart and sssd[nss] (this has
> not been sanitized this is how I see those in the log with 1.5 hour gap)
> 
> > Jan 21 23:32:32 hostname sssd[pam]: Starting up
> > Jan 22 01:02:52 hostname sssd[nss]: Starting up

Hmm, I have no idea why that would be happening. That's very strange.

Still waiting on those debug logs

Will past all the logs once I replicate it.