#381 SSSD can't handle a DNS timeout
Closed: Fixed Opened by mnagy.

When the DNS server doesn't respond, SSSD will get stuck. From the logs:

(Mon Jan 11 14:28:08 2010) [sssd[be[LDAP]]] [fo_resolve_service_send] (4): Trying to resolve service 'LDAP'
(Mon Jan 11 14:28:08 2010) [sssd[be[LDAP]]] [get_server_status] (7): Status of server 'nonexisting.address.dfjofisja.com' is 'name not resolved'
(Mon Jan 11 14:28:08 2010) [sssd[be[LDAP]]] [get_port_status] (7): Port status of port 389 for server 'nonexisting.address.dfjofisja.com' is 'neutral'
(Mon Jan 11 14:28:08 2010) [sssd[be[LDAP]]] [get_server_status] (7): Status of server 'nonexisting.address.dfjofisja.com' is 'name not resolved'
(Mon Jan 11 14:28:08 2010) [sssd[be[LDAP]]] [resolv_gethostbyname_send] (4): Trying to resolve A record of 'nonexisting.address.dfjofisja.com'
(Mon Jan 11 14:28:08 2010) [sssd[be[LDAP]]] [set_server_common_status] (4): Marking server 'nonexisting.address.dfjofisja.com' as 'resolving name'

This is caused by the fact that the async resolver only calls c-ares processing function when there is an activity on a file descriptor used by c-ares. If there is a timeout, however, the function is never called, since there is no activity on the FD.


Fixed by 77abf4061b4374fabc88771058916443e49d5032

fixedin: => 1.0.2
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @mnagy:
- Issue assigned to mnagy
- Issue set to the milestone: SSSD 1.0.2

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/1423

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata