From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 30993@debbugs.gnu.org
Subject: bug#30993: OpenSSH sshd killed by Shepherd 0.4.0
Date: Tue, 28 Aug 2018 11:47:12 +0200 [thread overview]
Message-ID: <874lfen7q7.fsf@gnu.org> (raw)
In-Reply-To: <20180329200803.GA15842@jasmine.lan> (Leo Famulari's message of "Thu, 29 Mar 2018 16:08:03 -0400")
Hi Leo,
Leo Famulari <leo@famulari.name> skribis:
> Since the update to Shepherd 0.4.0, I've found that OpenSSH's sshd is
> killed almost immediately after it starts with signal 15. I confirmed
> the issue started with the Shepherd upgrade by bisecting our Git
> history.
>
> I can reproduce the issue from commit
> b6beda1d6b9093a8493b5c3cde33ed522242c451 (gnu: Add botan.).
I’m “happy” to say that I experienced this on a server—not having ssh
access to a remote server is fairly annoying, I definitely sympathize…
What I see is this:
--8<---------------cut here---------------start------------->8---
Aug 6 07:56:40 localhost shepherd[1]: Service loopback has been started.
[...]
Aug 6 07:56:51 localhost sshd[606]: Server listening on 0.0.0.0 port 22.
[...]
Aug 6 07:57:05 localhost shepherd[1]: Service ssh-daemon could not be started.
[...]
Aug 6 07:57:46 localhost vmunix: [ 10.049791] random: ssh-keygen: uninitialized urandom read (32 bytes read)
--8<---------------cut here---------------end--------------->8---
(Note that the last message was pulled from /dev/kmsg by syslogd, but
it’s about an event that actually occurred before the first message.)
It waited for ~15 seconds, although ‘%pid-file-timeout’ in (shepherd
service) is only 5 seconds.
The SIGTERM you were seeing very likely comes from this bit:
--8<---------------cut here---------------start------------->8---
(match (read-pid-file pid-file
#:max-delay pid-file-timeout)
(#f
(catch-system-error (kill pid SIGTERM))
#f)
((? integer? pid)
pid))
--8<---------------cut here---------------end--------------->8---
On another machine:
--8<---------------cut here---------------start------------->8---
Aug 28 09:10:49 localhost sshd[435]: Server listening on 0.0.0.0 port 22.
Aug 28 09:10:49 localhost sshd[435]: Server listening on :: port 22.
[...]
Aug 28 09:10:50 localhost shepherd[1]: Service ssh-daemon has been started.
--8<---------------cut here---------------end--------------->8---
I wonder if this has to do with IPv6 (the failing case lacks the “Server
listening on ::” line), or if it’s just sshd occasionally taking a long
time to start.
Is it easily reproducible for you? Did you eventually gather more
details?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-08-28 9:48 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
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 [this message]
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=874lfen7q7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30993@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.