Hide Forgot
Description of problem: There are two machine, machine1 and machine2. Run "ssh root@$remote_machine1_ip "service virt-who restart"" on machine2, check the virt-who service status on machine1, it will report "virt-who dead but pid file exists". Version-Release number of selected component (if applicable): virt-who-0.5-5.el5 subscription-manager-0.98.14-1.el5 How reproducible: always Steps to Reproduce: 1. Run "ssh root@$remote_machine1_ip "service virt-who restart"" on machine2 2. Check the virt-who service status on machine1 Actual results: virt-who dead but pid file exists Expected results: virt-who is running Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
This bug has been fixed in virt-who-0.7-1.el5.
Moving to verified. version: virt-who-0.7-4.el5 subscription-manager-firstboot-1.0.13-1.el5 subscription-manager-1.0.13-1.el5 subscription-manager-gui-1.0.13-1.el5 python-rhsm-1.0.5-1.el5 katello-headpin-all-0.2.13-1.el6_2.noarch candlepin-0.6.5-1.el6_2.noarch Step: 1. Run "ssh root@$remote_machine1_ip "service virt-who restart"" on machine2 # ssh 10.66.13.64 "service virt-who restart" root.13.64's password: Stopping virt-who: [ OK ] Starting virt-who: [ OK ] [root@localhost wanghui]# 2. Check the virt-who service status on machine1 # service virt-who status virt-who (pid 434) is running...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0072.html