Hi List,
Facing another issue on RHEL-6. After server reboot, the sssd is
unable to go online. Messages like:
(Fri Jul 3 06:13:36 2015) [sssd[be[default]]] [be_run_online_cb]
(0x0080): Going online. Running callbacks.
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[fo_resolve_service_timeout] (0x0080): Service resolving timeout reached
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[sdap_id_op_connect_done] (0x0020): Failed to connect, going offline
(5 [Input/output error])
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]] [be_run_offline_cb]
(0x0080): Going offline. Running callbacks.
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[ad_subdomains_get_conn_done] (0x0080): No AD server is available,
cannot get the subdomain list while offline
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[sdap_dyndns_get_addrs_done] (0x0080): No LDAP server is available,
dynamic DNS update is skipped in offline mode.
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[sdap_dyndns_update_addrs_done] (0x0040): Can't get addresses for DNS
update
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[ad_dyndns_sdap_update_done] (0x0040): Dynamic DNS update failed
[1432158230]: Dynamic DNS update not possible while offline
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[ad_dyndns_nsupdate_done] (0x0040): Updating DNS entry failed
[1432158230]: Dynamic DNS update not possible while offline
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]]
[fo_resolve_service_timeout] (0x0080): Service resolving timeout reached
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]] [be_ptask_enable]
(0x0080): Task [Check if online (periodic)]: already enabled
(Fri Jul 3 06:13:42 2015) [sssd[be[default]]] [be_run_offline_cb]
(0x0080): Going offline. Running callbacks.
(Fri Jul 3 06:14:52 2015) [sssd[be[default]]] [be_run_online_cb]
(0x0080): Going online. Running callbacks.
(Fri Jul 3 06:14:58 2015) [sssd[be[default]]]
[fo_resolve_service_timeout] (0x0080): Service resolving timeout reached
(Fri Jul 3 06:14:58 2015) [sssd[be[default]]] [be_run_offline_cb]
(0x0080): Going offline. Running callbacks.
(Fri Jul 3 06:15:00 2015) [sssd[be[default]]]
[sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect
request failed.
(Fri Jul 3 06:15:00 2015) [sssd[be[default]]] [sdap_sys_connect_done]
(0x0020): sdap_async_connect_call request failed.
(Fri Jul 3 06:15:06 2015) [sssd[be[default]]]
[sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect
request failed.
And strangely also:
(Fri Jul 3 06:19:37 2015) [sssd[be[default]]]
[be_resolve_server_process] (0x0080): Couldn't resolve server (SRV
lookup meta-server), resolver returned (1432158227)
(Fri Jul 3 06:19:37 2015) [sssd[be[default]]]
[be_resolve_server_process] (0x0080): Couldn't resolve server
(xxx.yyy.zzz), resolver returned (5)
(Fri Jul 3 06:19:37 2015) [sssd[be[default]]]
[be_resolve_server_process] (0x0080): Couldn't resolve server
(xxx2.yyy.zzz), resolver returned (5)
Looks like DNS issue but I am pretty sure DNS worked just fine. After
sssd restart everything goes just fine.
sssd-1.11.7-4.el6
Thanks,
Ondrej
-----
The information contained in this e-mail and in any attachments is confidential and is
designated solely for the attention of the intended recipient(s). If you are not an
intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or
any part thereof. If you have received this e-mail in error, please notify the sender by
return e-mail and delete all copies of this e-mail from your computer system(s). Please
direct any additional queries to: communications(a)s3group.com. Thank You. Silicon and
Software Systems Limited (S3 Group). Registered in Ireland no. 378073. Registered Office:
South County Business Park, Leopardstown, Dublin 18.
_______________________________________________
sssd-users mailing list
sssd-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-users Hello,
does this happen every time you reboot the server or was it one time event?
If you reboot the machine and network is not working SSSD will go
offline, but it will periodically try to connect to the LDAP server and
will go online when network/DNS starts working again.