From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#30993: OpenSSH sshd killed by Shepherd 0.4.0 Date: Thu, 3 May 2018 12:38:08 -0400 Message-ID: <20180503163808.GA1019@jasmine.lan> References: <20180329200803.GA15842@jasmine.lan> <877epk3fuy.fsf@gnu.org> <20180406124101.GB1883@jasmine.lan> <87r2mvnm29.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fEHGC-0008RW-68 for bug-guix@gnu.org; Thu, 03 May 2018 12:39:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fEHG2-0000r0-KT for bug-guix@gnu.org; Thu, 03 May 2018 12:39:12 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:40535) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fEHG2-0000qj-8X for bug-guix@gnu.org; Thu, 03 May 2018 12:39:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fEHG1-0006oW-Nc for bug-guix@gnu.org; Thu, 03 May 2018 12:39:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: 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: Martin Castillo Cc: 30993@debbugs.gnu.org --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 03, 2018 at 05:16:32PM +0200, Martin Castillo wrote: >=20 >=20 > On 01.05.2018 22:43, Ludovic Court=C3=A8s wrote: > >> Maybe one could somehow strace herd, or change the make-kill-destructor > >> to log every time it is being executed? > >=20 > > =E2=80=98herd status sshd=E2=80=99 displays the last time sshd was resp= awned, but the > > info =E2=80=98herd=E2=80=99 receives actually includes the dates of all= the respawns, > > not just the last one. Is that what you=E2=80=99re asking for? > >=20 >=20 > My idea was that maybe make-kill-destructor is being called from > somewhere else. If this is being > logged, one could rule that out. >=20 > 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? >=20 > Or does linux provide a way to log all sent signals so one could find > the sending process? I haven't had time to debug this yet, and Shepherd 0.3 still works. Since nobody else can reproduce the bug, and since I expect OpenSSH to be commonly used, I suspect some non-deterministic Guile mis-compilation or filesystem corruption =E2=80=94 the system in question is using ext4. --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlrrOu0ACgkQJkb6MLrK fwjwEw/9GWU0ObLtXCmd3jJ/JXagYqRmUnVaKvTlfohnlucPrliNzQ6z5Dx6E3He ETjXbEQZ6U9ZGebIrSHunCNHialLW4gQ6cijnoAASIkGNb0gtA4rOr0pQHuxk9Do c3x3IdW3kO8mzL1JQVo+ZBidYw50bccq0HcNMGIkLRDClZxkrK19AnMS5O9Jx3MI 4N0Vz5a0FZE3MwEDxycR6LA0X5DVVAv9QbiHPpzopFiTwfQLUDfnD8zbQhvIWmJX nap6HPk5sg3Nyo5pOb9rbZUmEvwUwA5YFFqfmRS5g2ZZ6RdrE3zlC9zEEEO05UDv wlAyRfalmpGw69XWarULwUn7DMnZ4/cO8TpAiEajOb/+rsP71oJ+8Qa1QQTyNCOG G5FTUb2xodiw/kfY2x2HSf0Ct/IMbq4Qhnx6GfawxB7C1c8OFh3hiWN7j2hWR+Po rnMZ7btY7E+dRh7iTo/+A5a+/vaRSPYoCS9aPUZzsxSTscrD6yzCaDA/mu9yIL/X Dv2vC+V439PaqI8YSH3la6aWvlTWr4VqG5ADYtNtswUv9jJgPRYiagau6ZBYrlw2 sz2TT/GJUozWyIl1RcJTTqa8nNBeYgsx+DK9dG3K7qtODDgD/W+iOptkPug+8t0f +RlvKTWqB2urmxpXes/Kb6fYaybL75JGhqEpdSD9BzSRrj1N0tE= =/ead -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5--