Bug 29507 - sshd fails to properly restart requiring console intervention
sshd fails to properly restart requiring console intervention
Product: Red Hat Raw Hide
Classification: Retired
Component: openssh (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2001-02-25 22:41 EST by Matthew Galgoci
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-28 15:24:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Galgoci 2001-02-25 22:41:07 EST
A remote upgrade of sshd from the wolverine beta to the openssh version 2.5
in the 
20010225 build of rawhide fails to restart sshd after performing an
upgrade. I should
be able to remotely upgrade sshd without having to have sshd restarted from
physical console of the machine.
Comment 1 Nalin Dahyabhai 2001-02-26 16:35:23 EST
Was sshd running previously?  What messages did you get when you ran the
Comment 2 Matthew Galgoci 2001-02-26 16:39:11 EST
The machine was running a stock wolverine setup. sshd was running. I was sshed 
into the machine remotely playing around. I remotely upgraded the kernel to 
the rawhide kernel, and remotely rebooted the box. After the machien came back,
I ssh'd back in and did an rpm -Fhv openssh-* on the openssh rpms that I had 
downloaded from porkchop.

Is this enough info ?
Comment 3 Matthew Galgoci 2001-02-26 16:40:41 EST
Oh head. after the rpm -Fvh finished, sshd closed my connection and I had to 
get up from the couch, walk over, and restart sshd manually. extreme suckage.
Comment 4 Pekka Savola 2001-02-28 15:24:10 EST
The same happened to me, see #28611
Comment 5 Nalin Dahyabhai 2001-09-06 08:54:52 EDT
This appears to be fixed, at least as of rawhide-20010906.

Note You need to log in before you can comment on or make changes to this bug.