Can not start VM

[jerim]

Executing HA start for VM 100 Member KNTCLCN001 trying to enable pvevm:100...Aborted;

This is the error I get when trying to start a VM through the Promox GUI. When I execute the command 'clusvcadm -e pvevm:101 -m KNTCLCN001' on server KNTCLCN001, I get this error message:

Member KNTCLCN001 trying to enable pvevm:101...Aborted; service failed​

 

[dietmar]

Does it trigger another task log (on the GUI) for the VM start?

 

[jerim]

Executing HA start for VM 100
Member KNTCLCN001 trying to enable pvevm:100...Aborted; service failed
TASK ERROR: command 'clusvcadm -e pvevm:100 -m KNTCLCN001' failed: exit code 254

 

[dietmar]

So there is no other task there? Does it start manually:

# qm start 100

on node KNTCLCN001?

 

[dietmar]

Are there any hints in /var/log/cluster/rgmanager.log?

 

[jerim]

When I try 'qm start 100' on node KNTCLCN001:

Executing HA start for VM 100
Member KNTCLCN001 trying to enable pvevm:100...Aborted; service failed
command 'clusvcadm -e pvevm:100 -m KNTCLCN001' failed: exit code 254

The entire contents of /var/log/cluster/rgmanager.log:
Jun 12 23:24:22 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 12 23:24:22 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 12 23:28:34 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 12 23:28:34 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 12 23:30:56 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 12 23:30:56 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 12 23:32:42 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 12 23:32:42 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 12 23:34:44 rgmanager #43: Service pvevm:101 has failed; can not start.
Jun 12 23:34:44 rgmanager #13: Service pvevm:101 failed to stop cleanly
Jun 12 23:36:52 rgmanager #43: Service pvevm:101 has failed; can not start.
Jun 12 23:36:52 rgmanager #13: Service pvevm:101 failed to stop cleanly
Jun 12 23:38:10 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 12 23:38:10 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 13 00:05:40 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 13 00:05:40 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 13 00:41:07 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 13 00:41:07 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 13 18:28:20 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 13 18:28:20 rgmanager #13: Service pvevm:100 failed to stop cleanly
Jun 13 18:28:52 rgmanager #43: Service pvevm:100 has failed; can not start.
Jun 13 18:28:52 rgmanager #13: Service pvevm:100 failed to stop cleanly

 

[jerim]

What is weird is that these nodes had previously been working. I just recently switch out the storage for GFS2 clustered storage solution that is offering up an NFS share. I was able to upload .iso files fine.

 

[jerim]

SOLVED - I just rebooted all my nodes at once. Problem is fixed.

 

[dietmar]

Seems the service was in failed state, because stopped failed. Please make first sure that you can shutdown the VM cleanly.

The only way to restart a failed service is to disable it first:

# clusvcadm -d pvevm:100

After that you can start it again.

see

# man rgmanager
# man clusvcadm