On (06/02/18 11:37), Iaroslav wrote: >We have many workstation with fedora 27 and freeipa, and every 10-18 days one >of user can't log in. I do not understand why this happens. Reinstalling >free-ipa, cleaning /var/lib/sssd folder does not help, only totally reinstall >with / wipe (user /home does not change) solve this problem. > >Some logs with debug 9 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [cache_req_search_send] (0x0400): CR >#2: Returning [[email protected]] from cache >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [cache_req_search_ncache_filter] >(0x0400): CR #2: This request type does not support filtering result by >negative cache >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [cache_req_create_and_add_result] >(0x0400): CR #2: Found 2 entries in domain example.com >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [cache_req_done] (0x0400): CR #2: >Finished: Success >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pd_set_primary_name] (0x0400): User's >primary name is [email protected] >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_initgr_cache_set] (0x2000): >[test1] added to PAM initgroup cache >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_dp_send_req] (0x0100): Sending >request with the following data: >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): command: >SSS_PAM_ACCT_MGMT >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): domain: >example.com >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): user: >[email protected] >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): service: >login >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): tty: tty4 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): ruser: not >set >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): rhost: not >set >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): authtok >type: 0 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): newauthtok >type: 0 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): priv: 1 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): cli_pid: 3012 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_print_data] (0x0100): logon name: >test1 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [sbus_add_timeout] (0x2000): >0x55f5f30fb5d0 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_dom_forwarder] (0x0100): >pam_dp_send_req returned 0 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [sbus_remove_timeout] (0x2000): >0x55f5f30fb5d0 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [sbus_dispatch] (0x4000): dbus conn: >0x55f5f30e7620 >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [sbus_dispatch] (0x4000): Dispatching. >(Tue Feb 6 13:13:43 2018) [sssd[pam]] [pam_dp_process_reply] (0x0200): >received: [4 (System error)][example.com]
PAM system error is an unexpected situation in sssd with authentication. Unfortunately there are missing domain log files in this mail thread. Could you provide them? https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html#troubleshooting-general-authentication-problems LS _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
