SSSD / sssd

#378 Async resolver does not detect changes to resolv.conf
Closed: Fixed Opened by sgallagh.

Closed: Fixed
Reopen Issue

The LDAP server that I use for user identity is located inside a VPN. When I log onto my laptop, I perform an offline auth, then connect to the VPN once I am at the desktop.

The backend providers should be able to detect that I am now online and start performing online requests, but the logs instead indicate:

Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [fo_resolve_service_send] (4): Trying to resolve service 'LDAP'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [get_server_status] (7): Status of server 'ldap.bos.redhat.com' is 'name not resolved'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [get_port_status] (7): Port status of port 389 for server 'ldap.bos.redhat.com' is 'neutral'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [get_server_status] (7): Status of server 'ldap.bos.redhat.com' is 'name not resolved'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [resolv_gethostbyname_send] (4): Trying to resolve A record of 'ldap.bos.redhat.com'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [set_server_common_status] (4): Marking server 'ldap.bos.redhat.com' as 'resolving name'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [fo_resolve_service_done] (1): Failed to resolve server 'ldap.bos.redhat.com': DNS server returned answer with no data
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [set_server_common_status] (4): Marking server 'ldap.bos.redhat.com' as 'not working'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [be_resolve_server_done] (6): Couldn't resolve server (ldap.bos.redhat.com), resolver returned (1)
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [be_resolve_server_done] (6): Trying with the next one!
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [fo_resolve_service_send] (4): Trying to resolve service 'LDAP'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [get_server_status] (7): Status of server 'ldap.bos.redhat.com' is 'not working'
(Wed Jan  6 07:07:02 2010) [sssd[be[redhat.com]]] [fo_resolve_service_send] (1): No available servers for service 'LDAP'

The SSSD monitors /etc/resolv.conf with inotify on platforms that support it, or poll it on platforms that do not and issues a res_init() call in all SSSD processes to ensure that glibc functions that perform name lookups will be referencing the correct list of resolvers. However, the async DNS resolver needs to be told that it too must update its resolver list.

Fields changed

milestone: SSSD 1.0.1 => SSSD 1.0.2

Fixed by 830380e05ffc2fcc085fd6894f315073fd2f4cb7

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

Fields changed

coverity: =>
patch: => 0
tests: 1 => 0
testsupdated: 0 => 1
upgrade: => 0

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- 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/1420

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
None
None
None
Lowest
defect
Async Resolver
1.0.0
None
1
0
0
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.