Thanks for the confirmation @tronde, much appreciated.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1771340
Title:
sshd failed on config reload
To manage notifications about this bug go
@tronde, I just tried and the fix worked for me.
With the proposed package:
root@xenial-ssh-reload:~# ps fxaw
PID TTY STAT TIME COMMAND
1 ?Ss 0:02 /sbin/init
55 ?Ss 0:00 /lib/systemd/systemd-journald
...
2443 ?Ss 0:00 /usr/sbin/sshd -D
Note the
** Changed in: openssh (Ubuntu Xenial)
Assignee: Karl Stenerud (kstenerud) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1771340
Title:
sshd failed on
** Changed in: openssh (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1771340
Title:
sshd failed on config reload
To manage notifications ab
marking as fix released in the devel task, since the fix is in cosmic.
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Released
** Changed in: openssh (Ubuntu)
Assignee: Karl (kstenerud) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
The issue is reload, not restart.
You should:
- get a working normal sshd_config
- issue reload, confirm it works
- add an invalid option to sshd_config
- issue reload
The broken system will kill sshd, whereas the fixed one will refuse to
reload but sshd will still be running.
--
You received t
Confirmed fixed in >= artful. We have two ExecReload items under [Service]:
[Service]
...
ExecReload=/usr/sbin/sshd -t
ExecReload=/bin/kill -HUP $MAINPID
** Tags added: bitesize
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecide
