Bug 33633 - openssh-2.5.2p2 upgrade kills master sshd, won't restart
Summary: openssh-2.5.2p2 upgrade kills master sshd, won't restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: openssh
Version: 1.0
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
: 33122 33851 33912 33977 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-28 17:50 UTC by Pekka Savola
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-30 01:59:17 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2001:041 0 normal SHIPPED_LIVE : Updated openssh packages available 2001-03-30 05:00:00 UTC

Description Pekka Savola 2001-03-28 17:50:49 UTC
openssh-2.5.2p2-1.7
initscripts-5.49-1

After upgrading from 2.3.0p4, I get to the syslog:

Mar 28 20:08:57 xxx sshd[761]: Received signal 15; terminating.
Mar 28 20:08:57 xxx sshd: sshd shutdown succeeded
Mar 28 20:08:59 xxx sshd: RSA key generation succeeded

At this point, master sshd daemon has been killed and /var/run/sshd.pid
deleted.

Now, 'service sshd start' won't start the daemon; no error messages are
printed.  This
is caused by some bug in 'daemon' code of initscripts (misdetecting current
ssh connections
as the master process?), as '/usr/sbin/sshd' works fine.

There are two ways the next step happens:
 1) if you're on console, 'service sshd restart' kills _ONE_ connected ssh
client and otherwise
restarts gracefully.
 2) if you're connected with ssh, 'service sshd restart' kills your
connection but won't start a new
one.  Time to walk to the console..

The fact that all systems AFAIR had at least one incoming sshd client
process running at the time sshd was restarted might have been crucial.

This has been replicated on 5+ systems.

Comment 1 Preston Brown 2001-03-28 19:53:10 UTC
Bill, this definitely has to be a problem with the "daemon" initscripts 
function.


Comment 2 Bill Nottingham 2001-03-28 20:38:15 UTC
Yes. It was fixed between 7.0 and one of the various betas (the betas
don't have this problem...)

Comment 3 Bill Nottingham 2001-03-29 15:54:03 UTC
*** Bug 33851 has been marked as a duplicate of this bug. ***

Comment 4 Jeremy Katz 2001-03-29 19:58:42 UTC
*** Bug 33912 has been marked as a duplicate of this bug. ***

Comment 5 Jeremy Katz 2001-03-30 01:59:13 UTC
*** Bug 33977 has been marked as a duplicate of this bug. ***

Comment 6 Nalin Dahyabhai 2001-04-02 23:59:19 UTC
Fixed in openssh-2.5.2p2-1.7.2.

Comment 7 Pekka Savola 2001-04-14 20:44:14 UTC
*** Bug 33122 has been marked as a duplicate of this bug. ***


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