Bug 10440 - Upgrade through SSH doomed to fail: systemd restarts sshd
Summary: Upgrade through SSH doomed to fail: systemd restarts sshd
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-06-05 21:11 CEST by Panos Christeas
Modified: 2013-08-11 11:16 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Panos Christeas 2013-06-05 21:11:26 CEST 
Maybe dup of 5363

I tried to upgrade from mga2 to mga3, but "glibc" triggered an "systemd restart", which in turn killed the ssh connection I was upgrading from.

This left "glibc" to a broken state, so I had to do "urpmi --replacepkgs glibc" to fix it.

Shouldn't we make sure sshd doesn't kill active connections?
David Walser 2013-08-11 00:26:29 CEST

CC: (none) => mageia

Comment 1 Sander Lepik 2013-08-11 10:57:31 CEST 
Did you fix your sshd conf before upgrade?

https://wiki.mageia.org/en/Mageia_2_Errata#SSH_daemon_issues

CC: (none) => mageia

Sander Lepik 2013-08-11 10:59:09 CEST

Keywords: (none) => NEEDINFO

Comment 2 Panos Christeas 2013-08-11 11:03:59 CEST 
@Sander Lepik:

yes, it was the known issue about UsePAM=no 

Fixed it through the sshd configuration, you may close the bug.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 Sander Lepik 2013-08-11 11:16:38 CEST 
Tip for next time: if you run such things over SSH then use screen ;)
Note You need to log in before you can comment on or make changes to this bug.