Created attachment 785379 [details] logs Description of problem: After interruption to vdsmd restart operation, vdsmd cannot be started Version-Release number of selected component (if applicable): vdsm-4.12.0-52.gitce029ba.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: On a host with running vdsmd service: - run: "service vdsmd restart" and interrupt it (during vdsmd start) with ctrl+c Actual results: vdsm does prepareForShutdown and after that starts the daemon. after the interruption, I checked the service status: [root@green-vdsa ~]# service vdsmd status VDS daemon dead but subsys locked [root@green-vdsa ~]# pgrep resp 21864 [root@green-vdsa ~]# ps -ww 21864 PID TTY STAT TIME COMMAND 21864 ? S 0:00 /bin/bash -e /usr/share/vdsm/respawn --minlifetime 10 --daemon --masterpid /var/run/vdsm/supervdsm_respawn.pid /usr/bin/python /usr/share/vdsm/supervdsmServer.pyc /var/run/vdsm/svdsm.sock There is no vdsm process: [root@green-vdsa ~]# pgrep vdsmd [root@green-vdsa ~]# start to vdsm: [root@green-vdsa ~]# service vdsmd start cannot start VDS daemon when another instance runs [FAILED] Workaround: host reboot Additional info: logs
NOTE: This bug has been marked by accident as a security bug and I'm unable to change it. Email was sent to security-response-team in order to remove the security keyword
Removed security keyword/group.
*** This bug has been marked as a duplicate of bug 994912 ***