From: Martin Castillo <castilma@uni-bremen.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30993@debbugs.gnu.org
Subject: bug#30993: OpenSSH sshd killed by Shepherd 0.4.0
Date: Thu, 3 May 2018 17:16:32 +0200 [thread overview]
Message-ID: <b1b51eb6-77f1-0b53-4f18-3a83fe7ef24c@uni-bremen.de> (raw)
In-Reply-To: <87r2mvnm29.fsf@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
next prev parent reply other threads:[~2018-05-03 15:17 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 [this message]
2018-05-03 16:38 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1b51eb6-77f1-0b53-4f18-3a83fe7ef24c@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=30993@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.