-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/09/2015 05:32 AM, Petr Cech wrote:
On 11/04/2015 11:24 AM, Jakub Hrozek wrote:
> Hi,
>
> I created this patch to try to diagnose an issue where sssd
> would randomly restart on any of machines in a VM cluster without
> giving too much advise why. I think it might be useful to merge
> in general.
Hi Jakub,
I reviewed the patch. Code looks good to me. CI tests passed:
http://sssd-ci.duckdns.org/logs/job/32/25/summary.html
Then I tried to test new functionality.
Man pages are right, I found diag_cmd in sssd.conf.
And I really got the right message when I kill sss_pam: # (Mon Nov
9 04:30:47 2015) [sssd] [svc_child_info] (0x0040): Child [25767]
terminated with signal [9]
I would like to see output of pstack, but I don't know, how to get
the right state of SSSD. Can you help me, please?
Regards
Petr
There are problems inherent with passing the PID to the child process.
There's no guarantee that the process still exists. In the worst-case,
the PID could actually be reassigned to a new process and the output
you got back from something like pstack could be reading from a
different executable entirely.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlZA4zwACgkQeiVVYja6o6PjVQCgoTLJPxp46rdMzBmuTrbXi329
ZMEAn0fFVamHQugQAFjCNxQ4hCnTawmC
=VOCY
-----END PGP SIGNATURE-----