all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 06 Apr 2018 10:21:09 +0200	[thread overview]
Message-ID: <877epk3fuy.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.).
>
> One interesting tidbit is that the PID file '/var/run/sshd.pid' is not
> created anymore. And if I create an empty PID file by hand, it is
> removed after trying to start the ssh-daemon service. Also, the sshd
> user's home '/var/run/sshd' does not exist, and is similarly removed if
> it does exist.

Weird.  On my laptop /var/run/sshd.pid exists and contains the right
PID.  /var/run/sshd does not exist, though.

When I run the config you posted in ‘guix system vm’, ‘ssh-daemon’ is
correctly started and I see a correct ssh.pid and /var/run/sshd exists
as well.

> I ran the OpenSSH system test `make check-system TESTS=openssh` and it
> failed when it could not find the PID file. It passed on another
> non-GuixSD machine. The failing machine is relatively slow and lacks
> KVM: a ThinkPad x200s.

FWIW on my x86_64 laptop, I’ve run it several times in a row (using
“guix build /gnu/store/…-openssh.drv --check”), and it always succeeds.

> I modified the sshd invocation to print some debug output ('-d -E
> /tmp/sshd.log') and this is what it shows:
>
> ------
> debug1: sshd version OpenSSH_7.6, OpenSSL 1.0.2o  27 Mar 2018
> debug1: private host key #0: ssh-rsa SHA256:REDACTED
> debug1: private host key #1: ssh-dss SHA256:REDACTED
> debug1: private host key #2: ecdsa-sha2-nistp256 SHA256:REDACTED
> debug1: private host key #3: ssh-ed25519 SHA256:REDACTED
> debug1: rexec_argv[0]='/gnu/store/az7vib8gk16fybhshh5xpkljmgxyrs4k-openssh-7.6p1/sbin/sshd'
> debug1: rexec_argv[1]='-D'
> debug1: rexec_argv[2]='-d'
> debug1: rexec_argv[3]='-E'
> debug1: rexec_argv[4]='/tmp/sshd.log'
> debug1: rexec_argv[5]='-f'
> debug1: rexec_argv[6]='/gnu/store/miy7xg5j4fg3mn04mcl27awmcl6s97ss-sshd_config'
> debug1: Set /proc/self/oom_score_adj from 0 to -1000
> debug1: Bind to port 22 on 0.0.0.0.
> Server listening on 0.0.0.0 port 22.
> debug1: Bind to port 22 on ::.
> Server listening on :: port 22.
> Received signal 15; terminating.
> ------

Hmm, where could that SIGTERM come from?  ‘make-kill-destructor’ uses it
when a service is stopped, and otherwise it’s sent when we’re shutting
the system down.  But here?…

Thanks,
Ludo’.

  reply	other threads:[~2018-04-06  8:22 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 [this message]
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
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=877epk3fuy.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.