Bug#946997: marked as done (/usr/sbin/sshd: sshd doesn't restart after dying)
Your message dated Fri, 20 Dec 2019 14:32:16 +0000
with message-id <20191220143215.GR3701@riva.ucam.org>
and subject line Re: Bug#946997: /usr/sbin/sshd: sshd doesn't restart after dying
has caused the Debian Bug report #946997,
regarding /usr/sbin/sshd: sshd doesn't restart after dying
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
946997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946997
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:7.9p1-10+deb10u1
Severity: normal
File: /usr/sbin/sshd
Hi,
When sshd dies, it doesn't restart which makes the machine unreachable.
E.g. try "sudo killall sshd", and voilà you can't use a headless machine anymore.
Could this be fixed ?
Thanks,
Xav
-- System Information:
Debian Release: 10.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openssh-server depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii dpkg 1.19.7
ii libaudit1 1:2.8.4-3
ii libc6 2.28-10
ii libcom-err2 1.44.5-1+deb10u2
ii libgssapi-krb5-2 1.17-3
ii libkrb5-3 1.17-3
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam0g 1.3.1-5
ii libselinux1 2.8-1+b1
ii libssl1.1 1.1.1d-0+deb10u2
ii libsystemd0 241-7~deb10u2
ii libwrap0 7.6.q-28
ii lsb-base 10.2019051400
ii openssh-client 1:7.9p1-10+deb10u1
ii openssh-sftp-server 1:7.9p1-10+deb10u1
ii procps 2:3.3.15-2
ii ucf 3.0038+nmu1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages openssh-server recommends:
ii libpam-systemd [logind] 241-7~deb10u2
ii ncurses-term 6.1+20181013-2+deb10u2
ii xauth 1:1.0.10-1
Versions of packages openssh-server suggests:
pn molly-guard <none>
pn monkeysphere <none>
pn rssh <none>
pn ssh-askpass <none>
pn ufw <none>
-- debconf information:
openssh-server/permit-root-login: true
openssh-server/password-authentication: true
--- End Message ---
--- Begin Message ---
On Fri, Dec 20, 2019 at 09:45:16AM +0100, Xavier Bestel wrote:
> Indeed, I have been in a case where sshd has died mysteriously - my
> server had some troubles with a game server I'm writing basically
> turning into a fork bomb, and afterwards everything going amok.
>
> In short I didn't understand why I couldn't ssh anymore into my
> machine, and I thought I reproduced the problem via a killall sshd.
> But TIL systemd is too smart for that.
>
> Please close, I'll reopen if I manage to reproduce it correctly.
OK, done with this message; thanks.
--
Colin Watson [cjwatson@debian.org]
--- End Message ---
Reply to: