From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Castillo Subject: bug#30993: OpenSSH sshd killed by Shepherd 0.4.0 Date: Thu, 3 May 2018 17:16:32 +0200 Message-ID: References: <20180329200803.GA15842@jasmine.lan> <877epk3fuy.fsf@gnu.org> <20180406124101.GB1883@jasmine.lan> <87r2mvnm29.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fEFyk-0004L2-Ux for bug-guix@gnu.org; Thu, 03 May 2018 11:17:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fEFyf-00033u-Vs for bug-guix@gnu.org; Thu, 03 May 2018 11:17:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:40477) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fEFyf-00033k-RC for bug-guix@gnu.org; Thu, 03 May 2018 11:17:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fEFyf-0002xB-Kt for bug-guix@gnu.org; Thu, 03 May 2018 11:17:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r2mvnm29.fsf@gnu.org> Content-Language: en-US List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 30993@debbugs.gnu.org On 01.05.2018 22:43, Ludovic Courtès wrote: >> Maybe one could somehow strace herd, or change the make-kill-destructor >> to log every time it is being executed? > > ‘herd status sshd’ displays the last time sshd was respawned, but the > info ‘herd’ receives actually includes the dates of all the respawns, > not just the last one. Is that what you’re asking for? > My idea was that maybe make-kill-destructor is being called from somewhere else. If this is being logged, one could rule that out. Another wild idea would be sshd killing itself for some reason. stracing sshd would tell us, if that's the case. How would one do that? Does shepherd provide some debugging functions? Or does linux provide a way to log all sent signals so one could find the sending process? Martin -- GPG: 7FDE 7190 2F73 2C50 236E 403D CC13 48F1 E644 08EC