Your message dated Mon, 4 Oct 2021 12:29:09 +0200
with message-id <yvrxdqblcurax...@aurel32.net>
and subject line Re: Bug#990069: Still broken in ssh 8.4p1-5, libc6 2.31-13
has caused the Debian Bug report #990069,
regarding openssh-server: Not accepting new connections during Debian 10 -> 11
upgrade
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 ow...@bugs.debian.org
immediately.)
--
990069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:8.4p1-5
Severity: normal
Dear Maintainer,
During a Debian 10 -> 11 upgrade, the SSH server doesn't appear to be accepting
new connections. IMO this is less than optimal, and not sure if this was always
the case.
Would it be possible to keep accepting connections, or at least to make the
time window in which SSH is down as short as possible?
Greetings,
Olaf
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-16-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/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
iu libc6 2.31-12
ii libcom-err2 1.44.5-1+deb10u3
ii libcrypt1 1:4.4.18-4
ii libgssapi-krb5-2 1.17-3+deb10u1
ii libkrb5-3 1.17-3+deb10u1
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam0g 1.3.1-5
ii libselinux1 3.1-3
ii libssl1.1 1.1.1d-0+deb10u6
ii libsystemd0 241-7~deb10u7
ii libwrap0 7.6.q-28
ii lsb-base 10.2019051400
iu openssh-client 1:8.4p1-5
iu openssh-sftp-server 1:8.4p1-5
ii procps 2:3.3.15-2
iu runit-helper 2.10.3
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~deb10u7
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 ssh-askpass <none>
pn ufw <none>
-- debconf information:
openssh-server/permit-root-login: true
openssh-server/password-authentication: true
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-13+deb11u1
Done: Aurelien Jarno <aure...@debian.org>
On 2021-10-04 21:04, Tim Connors wrote:
> reopen 990069
> thanks.
>
> With these packages installed:
>
> 24573,4> dpkg --get-selections | grep ssh
> clusterssh install
> libssh-4:amd64 install
> libssh-gcrypt-4:amd64 install
> libssh2-1:amd64 install
> openssh-client install
> openssh-server install
> openssh-sftp-server install
> ssh-askpass install
> sshfs install
>
> This particular system is sysv, but I think my other machines suffering
> this same problem were already on systemd by the time I upgraded.
>
>
> 24583,14> sudo grep -e ssh -e libc6 -e Restarting -e '^ [a-z]' -e Services
> /var/log/apt/term.log
> Replacing files in old package libc6:amd64 (2.28-10) ...
> Replacing files in old package libc6:i386 (2.28-10) ...
> Preparing to unpack .../06-openssh-sftp-server_1%3a8.4p1-5_amd64.deb ...
> Unpacking openssh-sftp-server (1:8.4p1-5) over (1:7.9p1-10+deb10u2) ...
> Preparing to unpack .../13-openssh-client_1%3a8.4p1-5_amd64.deb ...
> Unpacking openssh-client (1:8.4p1-5) over (1:7.9p1-10+deb10u2) ...
> Preparing to unpack .../15-openssh-server_1%3a8.4p1-5_amd64.deb ...
> Unpacking openssh-server (1:8.4p1-5) over (1:7.9p1-10+deb10u2) ...
> Preparing to unpack .../0-libc6-dev_2.31-13_amd64.deb ...
You are still using the old version which is not fixed. This is fixed
in 2.31-13+deb11u1, not in 2.31-13. This version in in
bullseye-proposed-updates and will be moved to bullseye during the next
point release.
Closing the bug again.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
