Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=820908 (Red Hat Enterprise Linux 5)
Description of problem: We have setup SSSD to authenicate against a Win2008R2 AD domein. Every once in a while SSSD stops working and the logs displays: In the logging of the sssd daemon this appears: (Tue May 8 17:52:03 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:52:03 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:52:03 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) (Tue May 8 17:52:06 2012) [sssd[be[GXLOCAL]]] [check_for_valid_tgt] (3): TGT is valid. (Tue May 8 17:52:06 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:52:06 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:52:06 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) (Tue May 8 17:52:13 2012) [sssd[be[GXLOCAL]]] [check_for_valid_tgt] (3): TGT is valid. (Tue May 8 17:52:13 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:52:13 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:52:13 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) (Tue May 8 17:52:17 2012) [sssd[be[GXLOCAL]]] [check_for_valid_tgt] (3): TGT is valid. (Tue May 8 17:52:17 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:52:17 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:52:17 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) (Tue May 8 17:52:25 2012) [sssd[be[GXLOCAL]]] [check_for_valid_tgt] (3): TGT is valid. (Tue May 8 17:52:25 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:52:25 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:52:25 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) (Tue May 8 17:54:41 2012) [sssd[be[GXLOCAL]]] [sdap_get_initgr_user] (2): Expected one user entry and got 0 (Tue May 8 17:55:10 2012) [sssd[be[GXLOCAL]]] [sdap_get_initgr_user] (2): Expected one user entry and got 0 (Tue May 8 17:55:33 2012) [sssd[be[GXLOCAL]]] [check_for_valid_tgt] (3): TGT is valid. (Tue May 8 17:55:33 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:55:33 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:55:33 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) (Tue May 8 17:55:38 2012) [sssd[be[GXLOCAL]]] [check_for_valid_tgt] (3): TGT is valid. (Tue May 8 17:55:38 2012) [sssd[be[GXLOCAL]]] [fork_child] (1): fork failed [12][Cannot allocate memory]. (Tue May 8 17:55:38 2012) [sssd[be[GXLOCAL]]] [handle_child_send] (1): fork_child failed. (Tue May 8 17:55:38 2012) [sssd[be[GXLOCAL]]] [krb5_child_done] (1): child failed (12 [Cannot allocate memory]) In /var/log/secure this appears: May 8 17:52:03 sebulba sshd[25600]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d0046.gx.local user=USERNAME May 8 17:52:03 sebulba sshd[25600]: pam_sss(sshd:auth): received for user USERNAME: 4 (System error) May 8 17:52:04 sebulba sshd[25600]: Failed password for USERNAME from xxx.yyy.zzz.aaa port 53015 ssh2 May 8 17:52:06 sebulba sshd[25600]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d0046.gx.local user=USERNAME May 8 17:52:06 sebulba sshd[25600]: pam_sss(sshd:auth): received for user USERNAME: 4 (System error) May 8 17:52:09 sebulba sshd[25600]: Failed password for USERNAME from xxx.yyy.zzz.aaa port 53015 ssh2 May 8 17:52:13 sebulba sshd[25600]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d0046.gx.local user=USERNAME May 8 17:52:13 sebulba sshd[25600]: pam_sss(sshd:auth): received for user USERNAME: 4 (System error) May 8 17:52:15 sebulba sshd[25600]: Failed password for USERNAME from xxx.yyy.zzz.aaa port 53015 ssh2 May 8 17:52:17 sebulba sshd[25600]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d0046.gx.local user=USERNAME May 8 17:52:17 sebulba sshd[25600]: pam_sss(sshd:auth): received for user USERNAME: 4 (System error) May 8 17:52:20 sebulba sshd[25600]: Failed password for USERNAME from xxx.yyy.zzz.aaa port 53015 ssh2 May 8 17:52:25 sebulba sshd[25600]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d0046.gx.local user=USERNAME May 8 17:52:25 sebulba sshd[25600]: pam_sss(sshd:auth): received for user USERNAME: 4 (System error) May 8 17:52:27 sebulba sshd[25600]: Failed password for USERNAME from xxx.yyy.zzz.aaa port 53015 ssh2 Version-Release number of selected component (if applicable): [root@sebulba sssd]# rpm -qa | grep sssd sssd-client-1.5.1-49.el5_8.1.x86_64 sssd-1.5.1-49.el5_8.1.x86_64 How reproducible: It just happens over time. Steps to Reproduce: Not known Actual results: user cann't authenticate and therefor not login Expected results: User is logged in. Additional info:
I filed this ticket mostly for book keeping purposes. We had a user that ran into the bug on RHEL5 where it's not fixed yet, so I think it would be nice to track the problem upstream as well.
blockedby: => blocking: => coverity: => feature_milestone: => testsupdated: => 0
master: cdf4599
milestone: NEEDS_TRIAGE => SSSD 1.9.0 beta 1 resolution: => fixed status: new => closed
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.9.0 beta 1
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/2607
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.