gpg: Signature made Wed Aug 18 10:28:51 2021 UTC
gpg: using DSA key 0E4236CB52951E14536066222099B64CBF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andrew James Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>" [unknown]
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>" [unknown]
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>" [unknown]
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>" [unknown]
Hello,
On Wed, Aug 18, 2021 at 08:00:18AM +0100, Conrad Wood wrote:
> During the upgade ssh connections don't work (connection refused) for
> some time (>1 hour in my case), which is a bit scary. I used telnet-
> over-vpn for some machines.
This is mentioned in the release notes:
https://www.debian.org/releases/bullseye/mips64el/release-notes/ch-information.en.html#ssh-not-available
I'm not sure what the proper procedure would be to upgrade
openssh-server first. I guess download the .deb file manually and
install it before doing the "apt upgrade"?
If this is the relevant bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990069
then it seems like ssh must be restarted after a new libc is
installed, so I don't see how upgrading ssh first avoids that, but
maybe I misunderstand. The fix at the end of that bug is to glibc
making it aware that it has to restart ssh:
* debian/script.in/nsscheck.sh: restart openssh-server even if it
has been deconfigured during the upgrade. Closes: #990069.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
