Univention Bugzilla – Full Text Bug Listing |
Summary: | stuck connections with ssh reboot using systemd | ||
---|---|---|---|
Product: | UCS | Reporter: | Ingo Sieverdingbeck <sieverdingbeck> |
Component: | PAM | Assignee: | Jannik Ahlers <ahlers> |
Status: | CLOSED FIXED | QA Contact: | Arvid Requate <requate> |
Severity: | normal | ||
Priority: | P5 | CC: | damrose, hahn, requate |
Version: | UCS 4.3 | Keywords: | systemd |
Target Milestone: | UCS 4.4-0-errata | Flags: | hahn:
Patch_Available+
|
Hardware: | Other | ||
OS: | Linux | ||
URL: | https://serverfault.com/questions/706475/ssh-sessions-hang-on-shutdown-reboot | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=49614 | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 4: Minor Usability: Impairs usability in secondary scenarios |
Who will be affected by this bug?: | 5: Will affect all installed domains | How will those affected feel about the bug?: | 2: A Pain – users won’t like this once they notice it |
User Pain: | 0.229 | Enterprise Customer affected?: | Yes |
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | Usability | |
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 49045, 49910, 49941 |
Description
Ingo Sieverdingbeck
2018-06-22 11:20:39 CEST
The real bug is that "libpam-systemd" is installed by default via Recommends by "systemd" and "openssh-server", but it is not included in "/etc/pam.d/common-session" as the UCR template is out-of-date. echo "session optional pam_systemd.so" >>base/univention-pam/conffiles/etc/pam.d/common-session.d/10univention-pam_common I added the line that Philipp proposed. Now when shutting down your ssh session gets closed. 70460a4 Bug #47233: yaml 7fa3c41 Bug #47233: yaml fa47957 Bug #47233: close ssh connection properly when shutting down Successful build Package: univention-pam Version: 12.0.2-1A~4.4.0.201903141201 Branch: ucs_4.4-0 Scope: errata4.4-0 Verified: * Code * Function * Advisory We also need a backport for 4.3-3 (In reply to Arvid Requate from comment #4) > We also need a backport for 4.3-3 What about the rule to create a different bug with a different target mile stone? At least "announce_errata" needs a matching TM. > What about the rule to create a different bug with a different target mile stone? At least "announce_errata" needs a matching TM.
I don't know if there is a rule other than that the tool checks this, which my be overridden AFAIK? But the assignee may create a new bug to keep things as simple as possible.
I've simply cloned the bug for 4.3, and will set this back to verified. |