ssh sessions are not cleanly terminated on shutdown/restart with systemd
Bug #1645002 reported by
Zsolt Ero
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openssh (Debian) |
Fix Released
|
Unknown
|
|||
| openssh (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
Won't Fix
|
Undecided
|
Unassigned | ||
| Yakkety |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
In Ubuntu 16.04, a "reboot" command does not terminate the ssh session. This results in clients hanging, until timing out (sometimes as much as 120 seconds).
This also introduces bugs to all orchestration / automation tools which work over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 hosts. For example, have a look at this issue for Fabric:
https:/
The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6.
There is a very detailed discussion in their bug tracker:
https:/
Revision history for this message
| Nish Aravamudan (nacc) wrote | #1 |
| Changed in openssh (Ubuntu Yakkety): | |
| status: | New → Fix Released |
| Changed in openssh (Ubuntu): | |
| status: | New → Fix Released |
| Changed in openssh (Ubuntu Xenial): | |
| status: | New → Triaged |
| Changed in openssh (Debian): | |
| status: | Unknown → Fix Released |
Revision history for this message
| Paride Legovini (paride) wrote | #2 |
| Changed in openssh (Ubuntu Xenial): | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
As noted, this was fixed in Debian in 1:7.2p2-6. Both 16.10 and 17.04 have later versions, so this just needs an SRU to 16.04.