Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMiroslav Vadkerti
2011-04-21 18:14:15 UTC
Description of problem:
Finally I have a reproducer issue that was hunting me last months. I'm glad it is not that serious and looks like it has been in openssh-server package forever. I can reproduce it on both EL5 and EL6.
The reproducer is very simple:
# service sshd restart
Stopping sshd: [ OK ]
Starting sshd: [ OK ]
# netstat -putna | grep sshd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 19565/sshd
tcp 0 0 :::22 :::* LISTEN 19565/sshd
# /usr/sbin/sshd -p 133
# netstat -putna | grep sshd
tcp 0 0 0.0.0.0:133 0.0.0.0:* LISTEN 19571/sshd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 19565/sshd
tcp 0 0 :::133 :::* LISTEN 19571/sshd
tcp 0 0 :::22 :::* LISTEN 19565/sshd
# service sshd restart
Stopping sshd: [ OK ]
Starting sshd: [ OK ]
# netstat -putna | grep sshd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 19565/sshd
tcp 0 0 :::22 :::* LISTEN 19565/sshd
# service sshd restart
Stopping sshd: [FAILED]
Starting sshd: [ OK ]
# netstat -putna | grep sshd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 19565/sshd
tcp 0 0 :::22 :::* LISTEN 19565/sshd
As you can see the restarting the sshd service when also sshd on port 133 is running kills this instance and the previous instance is still running. The next restarts fail.
Version-Release number of selected component (if applicable):
openssh-5.3p1-52.el6
How reproducible:
100%
Steps to Reproduce:
see description
Actual results:
service sshd restart kills incorrect sshd instance and then begins to fail.
Expected results:
service sshd restart restarts correct sshd instance and doesn't fail if original instance still running. This makes impossible to restart ssh daemon with new configuration for example.
Changes in the init script causes regressions. It is likely that there may even cause regressions on customers. Since this bug is internal error only I recommend to revert this change.
Comment 4Miroslav Vadkerti
2011-07-26 13:10:17 UTC
This bug can be dropped from the errata. If you want to run more sshd daemons you have to make sure they use separate pid files using the -o 'PidFile pid-file' or other configuration file.