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.
Description of problem:
vhostmd-0.4-2.el5_3
While doing some RAS test cases I noticed a wrong behaviour of the vhostmd
startup script '/etc/init.d/vhostmd'.
# kill -11 vhostmd
# service vhostmd status
vhostmd dead but pid file exists
# service vhostmd stop
# service vhostmd start
Starting vhostmd: [ OK ]
# service vhostmd status
vhostmd dead but subsys locked
I noticed that the ' /etc/init.d/vhostmd' stop() function has logic to remove
the PID file in /var/run/.
However it is not executed during stop action, because an addtional status
check is done.
stop)
rh_status_q || exit 0
$1
;;
We have RAS logic that relies on the correct behaviour of the service startup
scripts.
Version-Release number of selected component (if applicable):vhostmd-0.4-2.el5_3
How reproducible:
start vmhost
Steps to Reproduce:
1.
2.
3.
Actual results:
see above
Expected results:
vmhost should delet PID file in /var/run/
Additional info:
IBM Tester: thomas.weber.com
IBM Project Manager: ralf.thelen.com (opening this bug)
We think, we know what needs to be done in vhostmd. If you need this technical information let Ralf Thelen (know).
Description of problem: vhostmd-0.4-2.el5_3 While doing some RAS test cases I noticed a wrong behaviour of the vhostmd startup script '/etc/init.d/vhostmd'. # kill -11 vhostmd # service vhostmd status vhostmd dead but pid file exists # service vhostmd stop # service vhostmd start Starting vhostmd: [ OK ] # service vhostmd status vhostmd dead but subsys locked I noticed that the ' /etc/init.d/vhostmd' stop() function has logic to remove the PID file in /var/run/. However it is not executed during stop action, because an addtional status check is done. stop) rh_status_q || exit 0 $1 ;; We have RAS logic that relies on the correct behaviour of the service startup scripts. Version-Release number of selected component (if applicable):vhostmd-0.4-2.el5_3 How reproducible: start vmhost Steps to Reproduce: 1. 2. 3. Actual results: see above Expected results: vmhost should delet PID file in /var/run/ Additional info: IBM Tester: thomas.weber.com IBM Project Manager: ralf.thelen.com (opening this bug) We think, we know what needs to be done in vhostmd. If you need this technical information let Ralf Thelen (know).