Hi, I had reporeted while back indicating that sssd subprocess ldap and nss stops working under heavy load. Looks like even after restart, its getting SIGKILL. Running on centos 6.5 and SSSD 1.9.2-129. I looked through the recent release notes for 1.9. branch but wasn't sure if this has been reported/fixed yet. Could you please advise ? Thanks
from sssd.log
Wed Oct 29 15:44:43:453121 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [nss]: [10]
(Wed Oct 29 15:44:43:453191 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:44:43:453206 2014) [sssd] [start_service] (0x0100): Queueing service nss for startup
(Wed Oct 29 15:44:43:669185 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [LDAP]: [10]
(Wed Oct 29 15:44:43:669300 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [LDAP]: [60]
(Wed Oct 29 15:44:43:669332 2014) [sssd] [start_service] (0x0100): Queueing service LDAP for startup
(Wed Oct 29 15:44:47:042335 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:44:48:769082 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Adding connection 0x69ae40.
(Wed Oct 29 15:44:49:704634 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 69AE40
(Wed Oct 29 15:45:35:868409 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:45:35:868510 2014) [sssd] [service_send_ping] (0x0100): Pinging pam
(Wed Oct 29 15:45:35:868773 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [nss]: [10]
(Wed Oct 29 15:45:35:868824 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:45:35:868844 2014) [sssd] [start_service] (0x0100): Queueing service nss for startup
(Wed Oct 29 15:45:35:869539 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:45:35:869580 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Adding connection 0x69c820.
(Wed Oct 29 15:45:35:869596 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 69C820
(Wed Oct 29 15:45:35:869641 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:45:35:869803 2014) [sssd] [ping_check] (0x0100): Service pam replied to ping
(Wed Oct 29 15:45:38:543488 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:45:38:718699 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Adding connection 0x698910.
(Wed Oct 29 15:45:38:718740 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 698910
(Wed Oct 29 15:45:38:718795 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:45:45:006440 2014) [sssd] [service_send_ping] (0x0100): Pinging pam
(Wed Oct 29 15:45:45:006711 2014) [sssd] [ping_check] (0x0100): Service pam replied to ping
(Wed Oct 29 15:45:45:869420 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 69AE40
(Wed Oct 29 15:45:45:869534 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 69AE40
(Wed Oct 29 15:45:45:869609 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69AE40
(Wed Oct 29 15:45:45:870728 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 69C820
(Wed Oct 29 15:45:45:870765 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 69C820
(Wed Oct 29 15:45:45:870802 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69C820
(Wed Oct 29 15:45:48:721481 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 698910
(Wed Oct 29 15:45:48:721584 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 698910
(Wed Oct 29 15:45:48:721669 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 698910
from sssd-ldap.log
(Wed Oct 29 15:44:47:798536 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:44:47:798555 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6bb740.
(Wed Oct 29 15:44:47:798582 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6BB740
(Wed Oct 29 15:44:47:798614 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:44:50:226352 2014) [sssd[be[LDAP]]] [id_callback] (0x0010): The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]
(Wed Oct 29 15:45:36:489821 2014) [sssd[be[LDAP]]] [cleanup_users] (0x0200): User mapred is still logged in or a dummy entry, keeping data
(Wed Oct 29 15:46:01:521917 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_next] (0x0200): No more address families to retry
(Wed Oct 29 15:46:01:534696 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:46:01:534727 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6f0420.
(Wed Oct 29 15:46:01:534740 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6F0420
(Wed Oct 29 15:46:01:534763 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:46:01:654795 2014) [sssd[be[LDAP]]] [be_resolve_server_process] (0x0200): Found address for server server name: TTL 3600
(Wed Oct 29 15:46:01:712980 2014) [sssd[be[LDAP]]] [get_naming_context] (0x0200): Using value from [namingContexts] as naming context.
(Wed Oct 29 15:46:01:745392 2014) [sssd[be[LDAP]]] [sdap_get_server_opts_from_rootdse] (0x0200): No known USN scheme is supported by this server!
(Wed Oct 29 15:46:01:745419 2014) [sssd[be[LDAP]]] [sdap_get_server_opts_from_rootdse] (0x0200): Will use modification timestamp as usn!
(Wed Oct 29 15:46:09:017362 2014) [sssd[be[LDAP]]] [init_timeout] (0x0040): Client timed out before Identification [0x70fbf0]!
(Wed Oct 29 15:46:09:017415 2014) [sssd[be[LDAP]]] [sbus_disconnect] (0x0200): Disconnecting 6F0420
(Wed Oct 29 15:46:09:017452 2014) [sssd[be[LDAP]]] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 6F0420
(Wed Oct 29 15:46:09:017510 2014) [sssd[be[LDAP]]] [sbus_disconnect] (0x0200): Disconnected 6F0420
(Wed Oct 29 15:46:10:509589 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:46:10:509635 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6c7360.
(Wed Oct 29 15:46:10:509647 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6C7360
(Wed Oct 29 15:46:10:509676 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
from messages
Oct 29 15:44:43 hostname sssd[nss]: Shutting down
Oct 29 15:44:43 hostname sssd[be[LDAP]]: Shutting down
Oct 29 15:44:46 hostname sssd[nss]: Starting up
Oct 29 15:44:46 hostname sssd[be[LDAP]]: Starting up
Oct 29 15:45:38 hostname sssd[nss]: Starting up
On Tue, Nov 11, 2014 at 11:37:31AM -0800, Daniel Jung wrote:
Hi, I had reporeted while back indicating that sssd subprocess ldap and nss stops working under heavy load. Looks like even after restart, its getting SIGKILL. Running on centos 6.5 and SSSD 1.9.2-129. I looked through the recent release notes for 1.9. branch but wasn't sure if this has been reported/fixed yet. Could you please advise ? Thanks
I don't see a mention of the monitor sending SIG{TERM,KILL} in the log snippet you sent, did I miss something?
from sssd.log
Wed Oct 29 15:44:43:453121 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [nss]: [10]
(Wed Oct 29 15:44:43:453191 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:44:43:453206 2014) [sssd] [start_service] (0x0100): Queueing service nss for startup
(Wed Oct 29 15:44:43:669185 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [LDAP]: [10]
(Wed Oct 29 15:44:43:669300 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [LDAP]: [60]
(Wed Oct 29 15:44:43:669332 2014) [sssd] [start_service] (0x0100): Queueing service LDAP for startup
(Wed Oct 29 15:44:47:042335 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:44:48:769082 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Adding connection 0x69ae40.
(Wed Oct 29 15:44:49:704634 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 69AE40
(Wed Oct 29 15:45:35:868409 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:45:35:868510 2014) [sssd] [service_send_ping] (0x0100): Pinging pam
(Wed Oct 29 15:45:35:868773 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [nss]: [10]
(Wed Oct 29 15:45:35:868824 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:45:35:868844 2014) [sssd] [start_service] (0x0100): Queueing service nss for startup
(Wed Oct 29 15:45:35:869539 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:45:35:869580 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Adding connection 0x69c820.
(Wed Oct 29 15:45:35:869596 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 69C820
(Wed Oct 29 15:45:35:869641 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:45:35:869803 2014) [sssd] [ping_check] (0x0100): Service pam replied to ping
(Wed Oct 29 15:45:38:543488 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:45:38:718699 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Adding connection 0x698910.
(Wed Oct 29 15:45:38:718740 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 698910
(Wed Oct 29 15:45:38:718795 2014) [sssd] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:45:45:006440 2014) [sssd] [service_send_ping] (0x0100): Pinging pam
(Wed Oct 29 15:45:45:006711 2014) [sssd] [ping_check] (0x0100): Service pam replied to ping
(Wed Oct 29 15:45:45:869420 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 69AE40
(Wed Oct 29 15:45:45:869534 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 69AE40
(Wed Oct 29 15:45:45:869609 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69AE40
(Wed Oct 29 15:45:45:870728 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 69C820
(Wed Oct 29 15:45:45:870765 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 69C820
(Wed Oct 29 15:45:45:870802 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69C820
(Wed Oct 29 15:45:48:721481 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 698910
(Wed Oct 29 15:45:48:721584 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 698910
(Wed Oct 29 15:45:48:721669 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 698910
from sssd-ldap.log
(Wed Oct 29 15:44:47:798536 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:44:47:798555 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6bb740.
(Wed Oct 29 15:44:47:798582 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6BB740
(Wed Oct 29 15:44:47:798614 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:44:50:226352 2014) [sssd[be[LDAP]]] [id_callback] (0x0010): The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]
(Wed Oct 29 15:45:36:489821 2014) [sssd[be[LDAP]]] [cleanup_users] (0x0200): User mapred is still logged in or a dummy entry, keeping data
(Wed Oct 29 15:46:01:521917 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_next] (0x0200): No more address families to retry
(Wed Oct 29 15:46:01:534696 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:46:01:534727 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6f0420.
(Wed Oct 29 15:46:01:534740 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6F0420
(Wed Oct 29 15:46:01:534763 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:46:01:654795 2014) [sssd[be[LDAP]]] [be_resolve_server_process] (0x0200): Found address for server server name: TTL 3600
(Wed Oct 29 15:46:01:712980 2014) [sssd[be[LDAP]]] [get_naming_context] (0x0200): Using value from [namingContexts] as naming context.
(Wed Oct 29 15:46:01:745392 2014) [sssd[be[LDAP]]] [sdap_get_server_opts_from_rootdse] (0x0200): No known USN scheme is supported by this server!
(Wed Oct 29 15:46:01:745419 2014) [sssd[be[LDAP]]] [sdap_get_server_opts_from_rootdse] (0x0200): Will use modification timestamp as usn!
(Wed Oct 29 15:46:09:017362 2014) [sssd[be[LDAP]]] [init_timeout] (0x0040): Client timed out before Identification [0x70fbf0]!
(Wed Oct 29 15:46:09:017415 2014) [sssd[be[LDAP]]] [sbus_disconnect] (0x0200): Disconnecting 6F0420
(Wed Oct 29 15:46:09:017452 2014) [sssd[be[LDAP]]] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 6F0420
(Wed Oct 29 15:46:09:017510 2014) [sssd[be[LDAP]]] [sbus_disconnect] (0x0200): Disconnected 6F0420
(Wed Oct 29 15:46:10:509589 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:46:10:509635 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6c7360.
(Wed Oct 29 15:46:10:509647 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6C7360
(Wed Oct 29 15:46:10:509676 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
from messages
Oct 29 15:44:43 hostname sssd[nss]: Shutting down
Oct 29 15:44:43 hostname sssd[be[LDAP]]: Shutting down
Oct 29 15:44:46 hostname sssd[nss]: Starting up
Oct 29 15:44:46 hostname sssd[be[LDAP]]: Starting up
Oct 29 15:45:38 hostname sssd[nss]: Starting up
sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
I thought the following line meant it nss got SIGTERM no?
(Wed Oct 29 15:44:43:453191 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:44:43:453206 2014) [sssd] [start_service] (0x0100): Queueing service nss for startup
On Tue, Nov 11, 2014 at 11:39 AM, Jakub Hrozek jhrozek@redhat.com wrote:
On Tue, Nov 11, 2014 at 11:37:31AM -0800, Daniel Jung wrote:
Hi, I had reporeted while back indicating that sssd subprocess ldap and nss stops working under heavy load. Looks like even after restart, its
getting
SIGKILL. Running on centos 6.5 and SSSD 1.9.2-129. I looked through the recent release notes for 1.9. branch but wasn't sure if this has been reported/fixed yet. Could you please advise ? Thanks
I don't see a mention of the monitor sending SIG{TERM,KILL} in the log snippet you sent, did I miss something?
from sssd.log
Wed Oct 29 15:44:43:453121 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [nss]: [10]
(Wed Oct 29 15:44:43:453191 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:44:43:453206 2014) [sssd] [start_service] (0x0100):
Queueing
service nss for startup
(Wed Oct 29 15:44:43:669185 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [LDAP]: [10]
(Wed Oct 29 15:44:43:669300 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [LDAP]: [60]
(Wed Oct 29 15:44:43:669332 2014) [sssd] [start_service] (0x0100):
Queueing
service LDAP for startup
(Wed Oct 29 15:44:47:042335 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Entering.
(Wed Oct 29 15:44:48:769082 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Adding connection 0x69ae40.
(Wed Oct 29 15:44:49:704634 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 69AE40
(Wed Oct 29 15:45:35:868409 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Got a connection
(Wed Oct 29 15:45:35:868510 2014) [sssd] [service_send_ping] (0x0100): Pinging pam
(Wed Oct 29 15:45:35:868773 2014) [sssd] [get_ping_config] (0x0100): Time between service pings for [nss]: [10]
(Wed Oct 29 15:45:35:868824 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:45:35:868844 2014) [sssd] [start_service] (0x0100):
Queueing
service nss for startup
(Wed Oct 29 15:45:35:869539 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Entering.
(Wed Oct 29 15:45:35:869580 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Adding connection 0x69c820.
(Wed Oct 29 15:45:35:869596 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 69C820
(Wed Oct 29 15:45:35:869641 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Got a connection
(Wed Oct 29 15:45:35:869803 2014) [sssd] [ping_check] (0x0100): Service
pam
replied to ping
(Wed Oct 29 15:45:38:543488 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Entering.
(Wed Oct 29 15:45:38:718699 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Adding connection 0x698910.
(Wed Oct 29 15:45:38:718740 2014) [sssd] [sbus_init_connection] (0x0200): Adding connection 698910
(Wed Oct 29 15:45:38:718795 2014) [sssd]
[sbus_server_init_new_connection]
(0x0200): Got a connection
(Wed Oct 29 15:45:45:006440 2014) [sssd] [service_send_ping] (0x0100): Pinging pam
(Wed Oct 29 15:45:45:006711 2014) [sssd] [ping_check] (0x0100): Service
pam
replied to ping
(Wed Oct 29 15:45:45:869420 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 69AE40
(Wed Oct 29 15:45:45:869534 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default
destructor
on connection 69AE40
(Wed Oct 29 15:45:45:869609 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69AE40
(Wed Oct 29 15:45:45:870728 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 69C820
(Wed Oct 29 15:45:45:870765 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default
destructor
on connection 69C820
(Wed Oct 29 15:45:45:870802 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69C820
(Wed Oct 29 15:45:48:721481 2014) [sssd] [sbus_disconnect] (0x0200): Disconnecting 698910
(Wed Oct 29 15:45:48:721584 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default
destructor
on connection 698910
(Wed Oct 29 15:45:48:721669 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 698910
from sssd-ldap.log
(Wed Oct 29 15:44:47:798536 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:44:47:798555 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6bb740.
(Wed Oct 29 15:44:47:798582 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6BB740
(Wed Oct 29 15:44:47:798614 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:44:50:226352 2014) [sssd[be[LDAP]]] [id_callback]
(0x0010):
The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]
(Wed Oct 29 15:45:36:489821 2014) [sssd[be[LDAP]]] [cleanup_users] (0x0200): User mapred is still logged in or a dummy entry, keeping data
(Wed Oct 29 15:46:01:521917 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_next] (0x0200): No more address families to retry
(Wed Oct 29 15:46:01:534696 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:46:01:534727 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6f0420.
(Wed Oct 29 15:46:01:534740 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6F0420
(Wed Oct 29 15:46:01:534763 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
(Wed Oct 29 15:46:01:654795 2014) [sssd[be[LDAP]]] [be_resolve_server_process] (0x0200): Found address for server server
name:
TTL 3600
(Wed Oct 29 15:46:01:712980 2014) [sssd[be[LDAP]]] [get_naming_context] (0x0200): Using value from [namingContexts] as naming context.
(Wed Oct 29 15:46:01:745392 2014) [sssd[be[LDAP]]] [sdap_get_server_opts_from_rootdse] (0x0200): No known USN scheme is supported by this server!
(Wed Oct 29 15:46:01:745419 2014) [sssd[be[LDAP]]] [sdap_get_server_opts_from_rootdse] (0x0200): Will use modification timestamp as usn!
(Wed Oct 29 15:46:09:017362 2014) [sssd[be[LDAP]]] [init_timeout]
(0x0040):
Client timed out before Identification [0x70fbf0]!
(Wed Oct 29 15:46:09:017415 2014) [sssd[be[LDAP]]] [sbus_disconnect] (0x0200): Disconnecting 6F0420
(Wed Oct 29 15:46:09:017452 2014) [sssd[be[LDAP]]] [sbus_default_connection_destructor] (0x0200): Invoking default
destructor
on connection 6F0420
(Wed Oct 29 15:46:09:017510 2014) [sssd[be[LDAP]]] [sbus_disconnect] (0x0200): Disconnected 6F0420
(Wed Oct 29 15:46:10:509589 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Entering.
(Wed Oct 29 15:46:10:509635 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Adding connection 0x6c7360.
(Wed Oct 29 15:46:10:509647 2014) [sssd[be[LDAP]]] [sbus_init_connection] (0x0200): Adding connection 6C7360
(Wed Oct 29 15:46:10:509676 2014) [sssd[be[LDAP]]] [sbus_server_init_new_connection] (0x0200): Got a connection
from messages
Oct 29 15:44:43 hostname sssd[nss]: Shutting down
Oct 29 15:44:43 hostname sssd[be[LDAP]]: Shutting down
Oct 29 15:44:46 hostname sssd[nss]: Starting up
Oct 29 15:44:46 hostname sssd[be[LDAP]]: Starting up
Oct 29 15:45:38 hostname sssd[nss]: Starting up
sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
On Tue, Nov 11, 2014 at 11:48:18AM -0800, Daniel Jung wrote:
I thought the following line meant it nss got SIGTERM no?
(Wed Oct 29 15:44:43:453191 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:44:43:453206 2014) [sssd] [start_service] (0x0100): Queueing service nss for startup
No, this is merely a configuration notice that if a process is sent SIGTERM and doesn't quit in 60 seconds after that, it's forcibly shut down with SIGKILL.
The reason we try SIGTERM first is that in some cases (like, database write in progress), SIGKILL might corrupt the database. SIGTERM allows for a more graceful shutdown.
So if you're seeing issues, I'm afraid these are not the symptoms...
Would the following meaning that connection between sssd and nss is gone? I no longer see health check between nss or ldap after 15:45. I surmised that this was where nss/ldap sub process had died.
(Wed Oct 29 15:45:45:869534 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 69AE40
(Wed Oct 29 15:45:45:869609 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69AE40
On Tue, Nov 11, 2014 at 12:05 PM, Jakub Hrozek jhrozek@redhat.com wrote:
On Tue, Nov 11, 2014 at 11:48:18AM -0800, Daniel Jung wrote:
I thought the following line meant it nss got SIGTERM no?
(Wed Oct 29 15:44:43:453191 2014) [sssd] [get_ping_config] (0x0100): Time between SIGTERM and SIGKILL for [nss]: [60]
(Wed Oct 29 15:44:43:453206 2014) [sssd] [start_service] (0x0100):
Queueing
service nss for startup
No, this is merely a configuration notice that if a process is sent SIGTERM and doesn't quit in 60 seconds after that, it's forcibly shut down with SIGKILL.
The reason we try SIGTERM first is that in some cases (like, database write in progress), SIGKILL might corrupt the database. SIGTERM allows for a more graceful shutdown.
So if you're seeing issues, I'm afraid these are not the symptoms... _______________________________________________ sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
On Tue, Nov 11, 2014 at 12:29:07PM -0800, Daniel Jung wrote:
Would the following meaning that connection between sssd and nss is gone? I no longer see health check between nss or ldap after 15:45. I surmised that this was where nss/ldap sub process had died.
(Wed Oct 29 15:45:45:869534 2014) [sssd] [sbus_default_connection_destructor] (0x0200): Invoking default destructor on connection 69AE40
(Wed Oct 29 15:45:45:869609 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69AE40
No, sorry, this is pretty normal as well. If you want to look for failures only, you can grep the logs with:
grep -E "(0x00[1-9]0)" *.log
Dont see any under sssd.log but under sssd-LDAP.log and sssd-pam.log
I see some failures.
(Tue Nov 4 03:33:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:33:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:34:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:34:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:35:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:35:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:36:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:36:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Oct 28 14:48:03:490957 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Tue Oct 28 14:48:03:491014 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
(Tue Oct 28 14:48:07:518039 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:48:07:518310 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:48:11:522881 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:48:11:522936 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:48:11:522958 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Tue Oct 28 14:48:11:523009 2014) [sssd[be[LDAP]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(Tue Oct 28 14:49:40:093732 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Tue Oct 28 14:49:40:209212 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
(Tue Oct 28 14:49:43:837338 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:49:43:837379 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:49:47:342083 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:49:47:342124 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:49:47:342142 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Tue Oct 28 14:49:47:342177 2014) [sssd[be[LDAP]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(Tue Oct 28 14:50:52:260602 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Tue Oct 28 14:50:52:260663 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
(Tue Oct 28 14:50:56:013535 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:50:56:013594 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:50:59:392558 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:50:59:392638 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:50:59:392661 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Tue Oct 28 14:50:59:392738 2014) [sssd[be[LDAP]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(Tue Oct 28 14:51:40:436085 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:51:40:436164 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:51:44:314180 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:51:44:314248 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:51:48:193674 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:51:48:193744 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:51:48:193766 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Wed Oct 29 15:44:47:798303 2014) [sssd[be[LDAP]]] [be_process_init] (0x0020): No selinux module provided for [LDAP] !!
(Wed Oct 29 15:44:47:798367 2014) [sssd[be[LDAP]]] [be_process_init] (0x0020): No host info module provided for [LDAP] !!
(Wed Oct 29 15:44:47:798426 2014) [sssd[be[LDAP]]] [be_process_init] (0x0020): Subdomains are not supported for [LDAP] !!
(Wed Oct 29 15:44:50:226352 2014) [sssd[be[LDAP]]] [id_callback] (0x0010): The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]
(Wed Oct 29 15:46:09:017362 2014) [sssd[be[LDAP]]] [init_timeout] (0x0040): Client timed out before Identification [0x70fbf0]!
(Thu Oct 30 05:00:20:566558 2014) [sssd[be[LDAP]]] [sdap_process_result] (0x0040): ldap_result error: [Can't contact LDAP server]
(Thu Oct 30 07:02:05:012462 2014) [sssd[be[LDAP]]] [sdap_process_result] (0x0040): ldap_result error: [Can't contact LDAP server]
(Sat Nov 1 05:48:00:962410 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Sat Nov 1 05:48:00:962468 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
On Tue, Nov 11, 2014 at 12:37 PM, Jakub Hrozek jhrozek@redhat.com wrote:
On Tue, Nov 11, 2014 at 12:29:07PM -0800, Daniel Jung wrote:
Would the following meaning that connection between sssd and nss is
gone? I
no longer see health check between nss or ldap after 15:45. I surmised
that
this was where nss/ldap sub process had died.
(Wed Oct 29 15:45:45:869534 2014) [sssd]
[sbus_default_connection_destructor]
(0x0200): Invoking default destructor on connection 69AE40
(Wed Oct 29 15:45:45:869609 2014) [sssd] [sbus_disconnect] (0x0200): Disconnected 69AE40
No, sorry, this is pretty normal as well. If you want to look for failures only, you can grep the logs with:
grep -E "(0x00[1-9]0)" *.log _______________________________________________ sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
On Tue, Nov 11, 2014 at 01:42:12PM -0800, Daniel Jung wrote:
Dont see any under sssd.log but under sssd-LDAP.log and sssd-pam.log
I see some failures.
(Tue Nov 4 03:33:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:33:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:34:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:34:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:35:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:35:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:36:08 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
(Tue Nov 4 03:36:38 2014) [sssd[pam]] [pam_dp_reconnect_init] (0x0010): Could not reconnect to LDAP provider.
The above messages from the PAM responder indicate that the sssd_be process crashed and had to be restarted by the sssd monitor process. Can you check your syslog for crashes? Or enable the abrt service?
Alternatively, check the sssd_LDAP.log for 'server_setup' function - it's usually the first function called after a new sssd_be process starts up, whatever precedes server_setup is either a graceful shutdown or a point where sssd_be crashed.
(Tue Oct 28 14:48:03:490957 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Tue Oct 28 14:48:03:491014 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
(Tue Oct 28 14:48:07:518039 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:48:07:518310 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
This line indicates DNS problems. There is not enough context in the logs you sent, but in the complete logs you should see what hostname did SSSD try to resolve.
(Tue Oct 28 14:48:11:522881 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:48:11:522936 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:48:11:522958 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Tue Oct 28 14:48:11:523009 2014) [sssd[be[LDAP]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(Tue Oct 28 14:49:40:093732 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Tue Oct 28 14:49:40:209212 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
(Tue Oct 28 14:49:43:837338 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:49:43:837379 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:49:47:342083 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:49:47:342124 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:49:47:342142 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Tue Oct 28 14:49:47:342177 2014) [sssd[be[LDAP]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(Tue Oct 28 14:50:52:260602 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Tue Oct 28 14:50:52:260663 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
(Tue Oct 28 14:50:56:013535 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:50:56:013594 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:50:59:392558 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:50:59:392638 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:50:59:392661 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Tue Oct 28 14:50:59:392738 2014) [sssd[be[LDAP]]] [sdap_id_op_connect_done] (0x0020): Failed to connect, going offline (5 [Input/output error])
(Tue Oct 28 14:51:40:436085 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:51:40:436164 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:51:44:314180 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:51:44:314248 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:51:48:193674 2014) [sssd[be[LDAP]]] [resolv_gethostbyname_done] (0x0040): querying hosts database failed [5]: Input/output error
(Tue Oct 28 14:51:48:193744 2014) [sssd[be[LDAP]]] [fo_resolve_service_done] (0x0020): Failed to resolve server 'hostname': Timeout while contacting DNS servers
(Tue Oct 28 14:51:48:193766 2014) [sssd[be[LDAP]]] [fo_resolve_service_send] (0x0020): No available servers for service 'LDAP'
(Wed Oct 29 15:44:47:798303 2014) [sssd[be[LDAP]]] [be_process_init] (0x0020): No selinux module provided for [LDAP] !!
(Wed Oct 29 15:44:47:798367 2014) [sssd[be[LDAP]]] [be_process_init] (0x0020): No host info module provided for [LDAP] !!
(Wed Oct 29 15:44:47:798426 2014) [sssd[be[LDAP]]] [be_process_init] (0x0020): Subdomains are not supported for [LDAP] !!
(Wed Oct 29 15:44:50:226352 2014) [sssd[be[LDAP]]] [id_callback] (0x0010): The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]
(Wed Oct 29 15:46:09:017362 2014) [sssd[be[LDAP]]] [init_timeout] (0x0040): Client timed out before Identification [0x70fbf0]!
(Thu Oct 30 05:00:20:566558 2014) [sssd[be[LDAP]]] [sdap_process_result] (0x0040): ldap_result error: [Can't contact LDAP server]
(Thu Oct 30 07:02:05:012462 2014) [sssd[be[LDAP]]] [sdap_process_result] (0x0040): ldap_result error: [Can't contact LDAP server]
(Sat Nov 1 05:48:00:962410 2014) [sssd[be[LDAP]]] [sss_ldap_init_sys_connect_done] (0x0020): sdap_async_sys_connect request failed.
(Sat Nov 1 05:48:00:962468 2014) [sssd[be[LDAP]]] [sdap_sys_connect_done] (0x0020): sdap_async_connect_call request failed.
sssd-users@lists.fedorahosted.org
-
Daniel Jung -
Jakub Hrozek