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