Hi Thomas, Thank you for taking the time to file a bug report.
The systemd service is indeed restarted throughout the package upgrade process. This means that sshd is supposed to halt (and cease listening on port 22) before the service is started again. How are you starting the ssh server? Would you mind providing your configuration file as well (make sure there is no sensitive data being shared if you decide to do so). Providing logs will also help us identify the issue you have been experiencing. As for the second issue reported, regarding creation of the /run/sshd directory when starting the service through systemd, this is actually performed through the RuntimeDirectory directive in the ssh unit files. Finally, would you be able to provide a reproducer for the issue? Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
