[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-12-25 Thread Launchpad Bug Tracker
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-26 Thread Andreas Hasenack
It's not entirely clear how you got yourself into that situation, so we can leave this bug marked as "incomplete" so that it will auto expire if there is no new information in a few weeks. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-26 Thread Andreas Hasenack
It's not entirely clear how you got yourself into that situation, so we can leave this bug marked as "incomplete" so that it will auto expire if there is no new information in a few weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-26 Thread Ulf Zimmermann
Thanks, Andreas! I've changed the port and was then able to finish the update installation by typing sudo dpkg --configure -a. After that I reverted back to my former port (it wasn't 22) and it works fine now. How can I close this "bug" report? Kind regards Ulf! -- You received this bug

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-26 Thread Andreas Hasenack
Well, restarting sshd remotely has been done for quite some time: $ ssh root@duo ... root@duo:~# pidof sshd 14132 2374 root@duo:~# systemctl restart sshd root@duo:~# pidof sshd 14286 14132 root@duo:~# Of course, now that your system is in a state where it's showing that error, care must be

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-26 Thread Andreas Hasenack
Well, restarting sshd remotely has been done for quite some time: $ ssh root@duo ... root@duo:~# pidof sshd 14132 2374 root@duo:~# systemctl restart sshd root@duo:~# pidof sshd 14286 14132 root@duo:~# Of course, now that your system is in a state where it's showing that error, care must be

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-25 Thread Ulf Zimmermann
syslog: Oct 25 23:47:23 zulu1451 systemd[1]: Stopped OpenBSD Secure Shell server. Oct 25 23:47:23 zulu1451 systemd[1]: Starting OpenBSD Secure Shell server... Oct 25 23:47:23 zulu1451 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Oct 25 23:47:23 zulu1451 systemd[1]:

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-22 Thread Andreas Hasenack
Thanks for filing this bug in Ubuntu. The 1:7.2p2-4ubuntu2.5 openssh update introduced a check in the systemd service file to prevent the daemon from stopping if there is a configuration syntax error (bug #1771340). This is done by calling "/usr/sbin/sshd -t". It looks like this call worked,

[Bug 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-22 Thread Andreas Hasenack
Thanks for filing this bug in Ubuntu. The 1:7.2p2-4ubuntu2.5 openssh update introduced a check in the systemd service file to prevent the daemon from stopping if there is a configuration syntax error (bug #1771340). This is done by calling "/usr/sbin/sshd -t". It looks like this call worked,