Re: [SSSD-users] sssd going offline because of DNS errors?
On Mon, Nov 02, 2015 at 01:21:32PM +0000, Ondrej Valousek wrote:
Hi List,
I have a problem with sssd going randomly offline because of the following errors:
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]] [fo_resolve_service_send] (0x0100): Trying
to resolve service 'AD'
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]] [resolve_srv_send] (0x0200): The status of
SRV lookup is not resolved
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]] [fo_set_port_status] (0x0100): Marking
port 0 of server '(no name)' as 'not working'
~~~~~~~~~~~~~~~~~
Is there any context around that would tell why did sssd go offline?
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]]
[be_resolve_server_process] (0x0080): Couldn't resolve server (myserver.example.com),
resolver returned (5)
<repeat the above 4 lines multiple times>
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]] [be_resolve_server_process] (0x0040):
Failed to find a server after 10 attempts
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]] [be_ptask_enable] (0x0080): Task [Check if
online (periodic)]: already enabled
(Mon Nov 2 12:33:52 2015) [sssd[be[default]]] [be_run_offline_cb] (0x0080): Going
offline. Running callbacks.
It happens only from time to time - I am pretty sure my DNS is working correctly so not
sure what could be the problem.
What does it mean "resolver returned (5)"?
The older parts of SSSD use errno codes for everything. In this case the
the resolver returned EIO, which it internally uses to signal that "no
more servers are available". I would first look into why sssd is marking
servers as offline.