Bug 1135960
| Summary: | sssd does not start after ipa-server-install and reboot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | James Chang <refrain5> | ||||
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Kaushik Banerjee <kbanerje> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.5 | CC: | abokovoy, grajaiya, jgalipea, lslebodn, mkosek, pbrezina, preichl, rcritten, refrain5 | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-09-02 20:07:37 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Attached logs show that sssd was enabled and also started: =================================================================== 2014-08-30T08:47:27Z DEBUG args=/usr/sbin/authconfig --enablesssdauth --update --enablesssd 2014-08-30T08:47:27Z DEBUG stdout= 2014-08-30T08:47:27Z DEBUG stderr= 2014-08-30T08:47:27Z INFO SSSD enabled 2014-08-30T08:47:28Z DEBUG args=/sbin/service sssd restart 2014-08-30T08:47:28Z DEBUG stdout=Stopping sssd: .[60G[.[0;31mFAILED.[0;39m] Starting sssd: .[60G[.[0;32m OK .[0;39m] .[60G[.[0;32m OK .[0;39m] 2014-08-30T08:47:28Z DEBUG stderr=cat: /var/run/sssd.pid: No such file or directory 2014-08-30T08:47:28Z DEBUG args=/sbin/service sssd status 2014-08-30T08:47:28Z DEBUG stdout=sssd (pid 6840) is running... 2014-08-30T08:47:28Z DEBUG stderr= 2014-08-30T08:47:28Z DEBUG args=/sbin/chkconfig sssd on 2014-08-30T08:47:28Z DEBUG stdout= 2014-08-30T08:47:28Z DEBUG stderr= =================================================================== I wonder if /var/log/messages after reboot contained some startup error associated with SSSD? I see 2 client installations in the logs and both ended with success: 2014-08-30T08:47:27Z INFO SSSD enabled 2014-08-30T08:47:28Z DEBUG args=/sbin/service sssd restart 2014-08-30T08:47:28Z DEBUG stdout=Stopping sssd: ^[[60G[^[[0;31mFAILED^[[0;39m]^M Starting sssd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^[[60G[^[[0;32m OK ^[[0;39m]^M 2014-08-30T08:47:28Z DEBUG stderr=cat: /var/run/sssd.pid: No such file or directory 2014-08-30T08:47:28Z DEBUG args=/sbin/service sssd status 2014-08-30T08:47:28Z DEBUG stdout=sssd (pid 6840) is running... 2014-08-30T08:47:28Z DEBUG stderr= 2014-08-30T08:47:28Z DEBUG args=/sbin/chkconfig sssd on 2014-08-30T08:47:28Z DEBUG stdout= ... 2014-08-30T08:47:28Z INFO Client configuration complete. 2014-08-30T09:14:26Z DEBUG args=/sbin/service sssd restart 2014-08-30T09:14:26Z DEBUG stdout=Stopping sssd: ^[[60G[^[[0;32m OK ^[[0;39m]^M Starting sssd: ^[[60G[^[[0;32m OK ^[[0;39m]^M^[[60G[^[[0;32m OK ^[[0;39m]^M 2014-08-30T09:14:26Z DEBUG stderr= 2014-08-30T09:14:26Z DEBUG args=/sbin/service sssd status 2014-08-30T09:14:26Z DEBUG stdout=sssd (pid 5108) is running... 2014-08-30T09:14:26Z DEBUG stderr= 2014-08-30T09:14:27Z DEBUG args=getent passwd admin 2014-08-30T09:14:27Z DEBUG stdout=admin:*:1414600000:1414600000:Administrator:/home/admin:/bin/bash 2014-08-30T09:14:27Z DEBUG stderr= Also, ipa-server-install sees the client installation as successful: 2014-08-30T08:47:29Z DEBUG args=/usr/sbin/ipa-client-install --on-master --unattended --domain linux. verusfinancial.com --server control.linux.verusfinancial.com --realm LINUX.VERUSFINANCIAL.COM --hostname control.linux.verusfinancial.com 2014-08-30T08:47:29Z DEBUG stdout= 2014-08-30T08:47:29Z DEBUG stderr=Hostname: control.linux.verusfinancial.com Realm: LINUX.VERUSFINANCIAL.COM DNS Domain: linux.verusfinancial.com IPA Server: control.linux.verusfinancial.com BaseDN: dc=linux,dc=verusfinancial,dc=com New SSSD config will be created Configured /etc/sssd/sssd.conf trying https://control.linux.verusfinancial.com/ipa/xml Forwarding 'env' to server u'https://control.linux.verusfinancial.com/ipa/xml' Adding SSH public key from /etc/ssh/ssh_host_dsa_key.pub Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub Forwarding 'host_mod' to server u'https://control.linux.verusfinancial.com/ipa/xml' SSSD enabled Configured /etc/openldap/ldap.conf Configured /etc/ssh/ssh_config Configured /etc/ssh/sshd_config Client configuration complete. 2014-08-30T08:47:29Z DEBUG args=/sbin/chkconfig ipa on So as Alexander pointed out, this will be most probably a problem with sssd service not starting after reboot. As such, moving to sssd component. However, without additional data, we cannot proceed with investigation. I need to know few facts: 1) Is sssd running after reboot? service sssd status 2) If sssd is running then we will need to see sssd log files. A) Please put "debug_level = 7" into doman, nss and pam sections in /etc/sssd/sssd.conf B) Restart sssd (or reboot machine) C) Try to authenticate D) Provide log files Sorry guys, false alarm, I have not been able to duplicate the issue after reinstalling it a few times. (In reply to James Chang from comment #6) > Sorry guys, false alarm, I have not been able to duplicate the issue after > reinstalling it a few times. I'm glad everything works now! |
Created attachment 933296 [details] ipa-server/ipa-client install logs from ipa server Description of problem: On the IPA server, ipa-join fails after reboot with fresh install of ipa-server. Version-Release number of selected component (if applicable): ipa-server-3.0.0-37.el6.x86_64 How reproducible: After installing ipa-server, add a user and reboot machine Steps to Reproduce: 1. install ipa-server 2. add user 3. reboot Actual results: Cannot login as any user other than root Expected results: Can login as user that was added before reboot Additional info: Adding "server" entry into /etc/ipa/default.conf fixes the issue and allows ipa-join to work: server=control.linux.verusfinancial.com