#3111 sssd doesn't start on IPA client if IPA server VM is paused
Closed: Fixed None Opened 5 years ago by jhrozek.

Looks like the responder starts before back end is ready and aborts completely:

(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [dp_get_options] (0x0400): Option dyndns_iface has no value                                                                                               [280/640]
(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [dp_get_options] (0x0400): Option dyndns_ttl has value 1200
(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [dp_get_options] (0x0400): Option dyndns_update_ptr is FALSE
(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [dp_get_options] (0x0400): Option dyndns_force_tcp is FALSE
(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [dp_get_options] (0x0400): Option dyndns_auth has value gss-tsig
(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [dp_get_options] (0x0400): Option dyndns_server has no value 
(Tue Jul 26 15:13:02 2016) [sssd[be[ipa.test]]] [ipa_init_dyndns] (0x0100): Dynamic DNS updates are of.






ldb: unable to dlopen /usr/lib64/ldb/modules/ldb/memberof.la : /usr/lib64/ldb/modules/ldb/memberof.la: invalid ELF header
ldb: unable to dlopen /usr/lib64/ldb/modules/ldb/memberof.la : /usr/lib64/ldb/modules/ldb/memberof.la: invalid ELF header
ldb: unable to dlopen /usr/lib64/ldb/modules/ldb/memberof.la : /usr/lib64/ldb/modules/ldb/memberof.la: invalid ELF header
ldb: unable to dlopen /usr/lib64/ldb/modules/ldb/memberof.la : /usr/lib64/ldb/modules/ldb/memberof.la: invalid ELF header
(Tue Jul 26 15:13:07 2016) [sssd[ssh]] [sss_dp_init] (0x0010): Failed to connect to monitor services.
(Tue Jul 26 15:13:07 2016) [sssd[ssh]] [sss_process_init] (0x0010): fatal error setting up backend connector
(Tue Jul 26 15:13:07 2016) [sssd[ssh]] [ssh_process_init] (0x0010): sss_process_init() failed
(Tue Jul 26 15:13:07 2016) [sssd[sudo]] [sss_dp_init] (0x0010): ldb: unable to dlopen /usr/lib64/ldb/modules/ldb/memberof.la : /usr/lib64/ldb/modules/ldb/memberof.la: invalid ELF header
Failed to connect to monitor services.
(Tue Jul 26 15:13:07 2016) [sssd[sudo]] [sss_process_init] (0x0010): (Tue Jul 26 15:13:07 2016) [sssd[ifp]] [sss_dp_init] (0x0010): fatal error setting up backend connector
(Tue Jul 26 15:13:07 2016) [sssd[sudo]] [sudo_process_init] (0x0010): Failed to connect to monitor services.
(Tue Jul 26 15:13:07 2016) [sssd[ifp]] [sss_process_init] (0x0010): fatal error setting up backend connector
sss_process_init() failed
(Tue Jul 26 15:13:07 2016) [sssd[ifp]] [ifp_process_init] (0x0010): sss_process_init() failed
(Tue Jul 26 15:13:07 2016) [sssd[pam]] [sss_dp_init] (0x0010): Failed to connect to monitor services.
(Tue Jul 26 15:13:07 2016) [sssd[pam]] [sss_process_init] (0x0010): fatal error setting up backend connector
(Tue Jul 26 15:13:07 2016) [sssd[pam]] [pam_process_init] (0x0010): ldb: unable to dlopen /usr/lib64/ldb/modules/ldb/memberof.la : /usr/lib64/ldb/modules/ldb/memberof.la: invalid ELF header

I reproduced this by simply pausing a server VM and starting the client.


Fields changed

rhbz: => todo

I suspect this was caused by the DP refactoring, so assigning to Pavel who knows the most about the DP code.

owner: somebody => pbrezina

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.1

It hangs in ldap in gethostbyname call for several seconds due to IPA unavailability:

(gdb) bt
#0  0x00007fbd0c05bc30 in __poll_nocancel () from /lib64/libc.so.6
#1  0x00007fbd0b6f3062 in __libc_res_nsend () from /lib64/libresolv.so.2
#2  0x00007fbd0b6f0d06 in __libc_res_nquery () from /lib64/libresolv.so.2
#3  0x00007fbd0b6f1841 in __libc_res_nsearch () from /lib64/libresolv.so.2
#4  0x00007fbd03c3c716 in _nss_dns_gethostbyname3_r () from /lib64/libnss_dns.so.2
#5  0x00007fbd03c3c9e4 in _nss_dns_gethostbyname_r () from /lib64/libnss_dns.so.2
#6  0x00007fbd0c07abfb in gethostbyname_r@@GLIBC_2.2.5 () from /lib64/libc.so.6
#7  0x00007fbd0ed0edee in ldap_pvt_gethostbyname_a () from /lib64/libldap-2.4.so.2
#8  0x00007fbd0ed0eff0 in ldap_pvt_get_fqdn () from /lib64/libldap-2.4.so.2
#9  0x00007fbd0ed0d397 in ldap_int_initialize () from /lib64/libldap-2.4.so.2
#10 0x00007fbd0ed0dea9 in ldap_set_option () from /lib64/libldap-2.4.so.2
#11 0x00007fbd075fe6b1 in setup_tls_config (basic_opts=0x16e3340) at /local-home/sssd/src/providers/ldap/sdap.c:823
#12 0x00007fbd08106f8e in ipa_init_misc (be_ctx=0x16b65d0, ipa_options=0x16dff60, ipa_id_ctx=0x16e0470, sdap_id_ctx=0x16e0500) at /local-home/sssd/src/providers/ipa/ipa_init.c:593
#13 0x00007fbd08107633 in sssm_ipa_init (mem_ctx=0x16d3170, be_ctx=0x16b65d0, provider=0x16d24d0, module_name=0x16cff90 "ipa", _module_data=0x16d3180) at /local-home/sssd/src/providers/ipa/ipa_init.c:687
#14 0x00000000004150b3 in dp_module_run_constructor (module=0x16d3170, be_ctx=0x16b65d0, provider=0x16d24d0) at /local-home/sssd/src/providers/data_provider/dp_modules.c:83
#15 0x0000000000415454 in dp_module_create (mem_ctx=0x16d1b90, be_ctx=0x16b65d0, provider=0x16d24d0, name=0x16cfea0 "ipa") at /local-home/sssd/src/providers/data_provider/dp_modules.c:160
#16 0x00000000004155cf in dp_load_module (mem_ctx=0x16d1b90, be_ctx=0x16b65d0, provider=0x16d24d0, modules=0x16d1b90, name=0x16cfea0 "ipa") at /local-home/sssd/src/providers/data_provider/dp_modules.c:200
#17 0x0000000000416548 in dp_target_init (be_ctx=0x16b65d0, provider=0x16d24d0, modules=0x16d1b90, target=0x16cee80) at /local-home/sssd/src/providers/data_provider/dp_targets.c:348
#18 0x0000000000416b96 in dp_load_targets (be_ctx=0x16b65d0, provider=0x16d24d0, targets=0x16d1c50, modules=0x16d1b90) at /local-home/sssd/src/providers/data_provider/dp_targets.c:484
#19 0x0000000000416d3d in dp_init_targets (mem_ctx=0x16d24d0, be_ctx=0x16b65d0, provider=0x16d24d0, modules=0x16d1b90) at /local-home/sssd/src/providers/data_provider/dp_targets.c:530
#20 0x0000000000414c3a in dp_init (ev=0x16ad1b0, be_ctx=0x16b65d0, uid=0, gid=0) at /local-home/sssd/src/providers/data_provider/dp.c:103
#21 0x000000000040878a in be_process_init (mem_ctx=0x16ae600, be_domain=0x16a2f70 "IPA.PB", uid=0, gid=0, ev=0x16ad1b0, cdb=0x16ae710) at /local-home/sssd/src/providers/data_provider_be.c:450
#22 0x0000000000409092 in main (argc=10, argv=0x7ffea4d2b4e8) at /local-home/sssd/src/providers/data_provider_be.c:562

Responders can't connect to backend because backend bus is not yet setup since it's initialized after module with current master. Before DP patches we initialized the bus first.

Fix is to initialize backend bus as soon as possible.

Fields changed

patch: 0 => 1
status: new => assigned

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: todo => 0

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.14.1

4 years ago

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

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.

Login to comment on this ticket.

Metadata