On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote:
No, this is not a normal phenomenon for bookworm upgrades. I've never heard of it happening to anyone before.
i disagree. i had the same problem b/c i also had dropbear installed. for some reason the dropbear daemon is started first in bookworm, so port 22 was already in use when sshd was started. reading the log file (aka systemd-journal) was very enlightening.
a simple
systemctl stop dropbear.service systemctl disable dropbear.service systemctl start ssh.servicewas enough to solve the problem. of course, one needs access to the console...
greetings...