#1929 Junk character in sssd_domain.log for domain string when sssd tries to go online from offline mode
Closed: Fixed None Opened 6 years ago by ksiddiqu.

I have seen following junk chacracter for domain string in sssd.log when sssd tries to go online from offline mode and it causes authentication failures.

excerpt from sssd_domain.log
============================
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [check_if_online] (0x2000): Trying to go back online!
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [set_srv_data_status] (0x0100): Marking SRV lookup of service 'IPA' as 'neutral'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [set_server_common_status] (0x0100): Marking server 'f18-ipa-master.testrelm.com' as 'name not resolved'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_set_port_status] (0x0100): Marking port 0 of server 'f18-ipa-master.testrelm.com' as 'neutral'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_resolve_service_send] (0x0100): Trying to resolve service 'IPA'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [get_server_status] (0x1000): Status of server 'f18-ipa-master.testrelm.com' is 'name not resolved'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_resolve_service_activate_timeout] (0x2000): Resolve timeout set to 5 seconds
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolve_srv_send] (0x0200): The status of SRV lookup is neutral
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolv_discover_srv_next_domain] (0x0400): SRV resolution of service 'ldap'. Will use DNS discovery domain '@�'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolv_getsrv_send] (0x0100): Trying to resolve SRV record of '_ldap._tcp.@�'

sssd version:
=============
[root@f18-ipa-client1 ~]# rpm -q sssd
sssd-1.9.93-0.20130513T1456Zgit31c1f3a.fc18.x86_64
[root@f18-ipa-client1 ~]#

Fields changed

description: I have seen following junk chacracter for domain string in sssd.log when sssd tries to go online from offline mode and it causes authentication failures.

excerpt from sssd_domain.log

(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [check_if_online] (0x2000): Trying to go back online!
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [set_srv_data_status] (0x0100): Marking SRV lookup of service 'IPA' as 'neutral'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [set_server_common_status] (0x0100): Marking server 'f18-ipa-master.testrelm.com' as 'name not resolved'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_set_port_status] (0x0100): Marking port 0 of server 'f18-ipa-master.testrelm.com' as 'neutral'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_resolve_service_send] (0x0100): Trying to resolve service 'IPA'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [get_server_status] (0x1000): Status of server 'f18-ipa-master.testrelm.com' is 'name not resolved'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_resolve_service_activate_timeout] (0x2000): Resolve timeout set to 5 seconds
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolve_srv_send] (0x0200): The status of SRV lookup is neutral
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolv_discover_srv_next_domain] (0x0400): SRV resolution of service 'ldap'. Will use DNS discovery domain '@�'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolv_getsrv_send] (0x0100): Trying to resolve SRV record of '_ldap._tcp.@�'

sssd version:

[root@f18-ipa-client1 ~]# rpm -q sssd
sssd-1.9.93-0.20130513T1456Zgit31c1f3a.fc18.x86_64
[root@f18-ipa-client1 ~]# => I have seen following junk chacracter for domain string in sssd.log when sssd tries to go online from offline mode and it causes authentication failures.

{{{
excerpt from sssd_domain.log
============================
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [check_if_online] (0x2000): Trying to go back online!
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [set_srv_data_status] (0x0100): Marking SRV lookup of service 'IPA' as 'neutral'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [set_server_common_status] (0x0100): Marking server 'f18-ipa-master.testrelm.com' as 'name not resolved'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_set_port_status] (0x0100): Marking port 0 of server 'f18-ipa-master.testrelm.com' as 'neutral'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_resolve_service_send] (0x0100): Trying to resolve service 'IPA'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [get_server_status] (0x1000): Status of server 'f18-ipa-master.testrelm.com' is 'name not resolved'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [fo_resolve_service_activate_timeout] (0x2000): Resolve timeout set to 5 seconds
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolve_srv_send] (0x0200): The status of SRV lookup is neutral
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolv_discover_srv_next_domain] (0x0400): SRV resolution of service 'ldap'. Will use DNS discovery domain '@�'
(Wed May 15 17:43:55 2013) [sssd[be[testrelm.com]]] [resolv_getsrv_send] (0x0100): Trying to resolve SRV record of '_ldap._tcp.@�'

sssd version:

[root@f18-ipa-client1 ~]# rpm -q sssd
sssd-1.9.93-0.20130513T1456Zgit31c1f3a.fc18.x86_64
[root@f18-ipa-client1 ~]#

}}}

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.0
rhbz: => 0

I tried to reproduce this bug, but even with the same IPA configuration and using sssd.conf you provided, I didn't hit this issue, I tried the 1.9.93 and current master, and both are acting fine.
I was thinking, if this might be a server-side issue, but code-wise it's impossible.

Are you able to reproduce this every time?
Could you please state the exact version of ipaserver and architecture for both server and client machine?

owner: somebody => okos
status: new => assigned

I was able to reproduce this bug.

Valgrind output

---------------
==15649== Invalid read of size 1
==15649==    at 0x3924047DE8: vfprintf (vfprintf.c:1615)
==15649==    by 0x3924107ECF: __vsnprintf_chk (vsnprintf_chk.c:63)
==15649==    by 0x3926C061F8: talloc_vasprintf (stdio2.h:77)
==15649==    by 0x3926C06396: talloc_asprintf (talloc.c:2251)
==15649==    by 0x42D56D: resolv_discover_srv_next_domain (async_resolv_utils.c:235)
==15649==    by 0x42E442: resolv_discover_srv_send (async_resolv_utils.c:201)
==15649==    by 0x425407: fo_discover_srv_send (fail_over_srv.c:55)
==15649==    by 0x425637: fo_resolve_srv_dns_discover (fail_over_srv.c:613)
==15649==    by 0x4266A6: fo_resolve_srv_dns_send (fail_over_srv.c:527)
==15649==    by 0x4237B6: fo_resolve_service_send (fail_over.c:1198)
==15649==    by 0x4153FD: be_resolve_server_send (data_provider_fo.c:547)
==15649==    by 0xD631051: sdap_cli_resolve_next (sdap_async_connection.c:1460)
==15649==  Address 0x57cd650 is 96 bytes inside a block of size 123 free'd
==15649==    at 0x4A077E6: free (vg_replace_malloc.c:446)
==15649==    by 0x3926C03608: _talloc_free (talloc.c:942)
==15649==    by 0x4240A6: resolve_srv_done (fail_over.c:1258)
==15649==    by 0x42500F: fo_discover_srv_done (fail_over_srv.c:139)
==15649==    by 0x42D7B6: resolv_discover_srv_done (async_resolv_utils.c:299)
==15649==    by 0x428DA0: resolv_getsrv_done (async_resolv.c:1663)
==15649==    by 0x392540BEAD: qcallback (ares_query.c:180)
==15649==    by 0x392540A7D9: end_query (ares_process.c:1266)
==15649==    by 0x392540B521: process_answer.part.1 (ares_process.c:611)
==15649==    by 0x392540B785: read_udp_packets (ares_process.c:547)
==15649==    by 0x392540BAC6: processfds (ares_process.c:152)
==15649==    by 0x428EC1: fd_input_available (async_resolv.c:148)

changelog: =>
owner: okos => lslebodn
status: assigned => new

Fields changed

patch: 0 => 1

Fields changed

milestone: SSSD 1.10.0 => SSSD 1.10 beta

Fields changed

resolution: => fixed
status: new => closed

Metadata Update from @ksiddiqu:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.10 beta

2 years ago

Login to comment on this ticket.

Metadata