From: Leo Famulari <leo@famulari.name>
To: Martin Castillo <castilma@uni-bremen.de>
Cc: 30993@debbugs.gnu.org
Subject: bug#30993: OpenSSH sshd killed by Shepherd 0.4.0
Date: Thu, 3 May 2018 12:38:08 -0400 [thread overview]
Message-ID: <20180503163808.GA1019@jasmine.lan> (raw)
In-Reply-To: <b1b51eb6-77f1-0b53-4f18-3a83fe7ef24c@uni-bremen.de>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Thu, May 03, 2018 at 05:16:32PM +0200, Martin Castillo wrote:
>
>
> 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?
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 — the system in question is using ext4.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-03 16:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 20:08 bug#30993: OpenSSH sshd killed by Shepherd 0.4.0 Leo Famulari
2018-04-06 8:21 ` Ludovic Courtès
2018-04-06 12:41 ` Leo Famulari
2018-04-06 14:37 ` Ludovic Courtès
2018-05-01 13:13 ` Martin Castillo
2018-05-01 20:43 ` Ludovic Courtès
2018-05-03 15:16 ` Martin Castillo
2018-05-03 16:38 ` Leo Famulari [this message]
2018-05-04 2:01 ` Martin Castillo
2018-05-06 19:50 ` Leo Famulari
2018-05-07 19:10 ` Martin Castillo
2018-07-19 13:15 ` bug#32197: " Clément Lassieur
2018-07-19 14:26 ` Clément Lassieur
2018-07-19 16:57 ` Leo Famulari
2018-07-23 17:08 ` Martin Castillo
2018-08-28 9:47 ` Ludovic Courtès
2018-11-17 9:46 ` bug#30993: issue: ssh-daemon could not be started Taegil Bae
2018-11-19 21:22 ` Ludovic Courtès
2018-11-20 1:33 ` Taegil Bae
2019-05-14 13:33 ` bug#30993: OpenSSH sshd killed by Shepherd 0.4.0 Ludovic Courtès
2019-05-14 18:21 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180503163808.GA1019@jasmine.lan \
--to=leo@famulari.name \
--cc=30993@debbugs.gnu.org \
--cc=castilma@uni-bremen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).