Learn more about these different git repos.
Other Git URLs
Logs from the error: http://fpaste.org/151535/
This appears to only occur on CentOS 5, I haven't had the issue on CentOS 6. We just recently updated to CentOS 5.11, this symptom was not resolved (it was a preexisting issue).
There is no known cause for this. After the failure (at the end of the logs, the repeated ping fail message), sssd will no longer respond to anything, so ssh ceases to function.
Replying to [ticket:2496 acidrainfall]:
The contents of this paste have been hidden
cc: => lslebodn@redhat.com
Sorry, I haven't used fpaste before. Try this URL. http://fpaste.org/151535/41625444/
sssd_ssh.log: http://fpaste.org/151913/
sssd_pam.log: http://fpaste.org/151917/
sssd_nss.log: http://fpaste.org/151915/
sssd_default.log: http://fpaste.org/151918/
sssd_ssh.log before the failure: http://fpaste.org/151923/
sssd_pam.log before the failure: http://fpaste.org/151922/
These are the only two entries that exist prior to the explosion in the 17:00 hour.
I've spread out some more debug_level = 8 settings on a bunch of centos5 systems, I'm hoping one fails soon and we can put this to bed.
Fields changed
owner: somebody => lslebodn
I apologise for late response. Unfortunately, it is not possible to say where exactly is the problem.
Do you have a log files with higher debug level. I would be interested in domain log file (sssd_default.log) and monitor log file(sssd.log)
Which version of sssd do you use?
Apologies - I thought I had updated this previously.
I run sssd-1.9.6-0.el5
Since ~7 weeks ago I've had a dragnet set up to try to catch the error and none of the systems have failed. We also recently upgraded to CentOS 5.11, which actually may have fixed it. I don't know if it will happen again, but go ahead and close this ticket.
OK, I'm going to close the ticket.
Thank you very much for reporting the issue nonetheless. If you run across the problem again, don't hesitate to open a new ticket or reopen this one.
resolution: => worksforme status: new => closed
Metadata Update from @acidrainfall: - Issue assigned to lslebodn - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3538
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.