Node down, can't see VM names (only numbers?)

[locusofself]

Hey folks,

I have a proxmox cluster and one node is having a problem, probably hardware related.

I can't see which VMs are down as a result, only the numbers, so I don't know if this is an urgent problem for me. Is there a way, from the nodes that are alive, to obtain the friendly VM names?

-Kevin

 

[dietmar]

Make sure server 'pvestatd' is running on that node.

Maybe there is an inaccessible storage on that node? Please check with

# pvesm status

 

[locusofself]

Make sure server 'pvestatd' is running on that node.

Maybe there is an inaccessible storage on that node? Please check with

# pvesm status

Thanks Dietmar, sorry I should have been more clear. The node is hard down, definitely some hardware problem. I'm just wondering , since it is part of a cluster (but H.A. is not configured), if I can obtain a list of the VM names that are on the down node, since currently I can only see them by number.

 

[dietmar]

You can inspect the config files directly (/etc/pve/nodes/<nodename>/qemu-server/*.conf).

 

[Okijames]

Sorry to revive an old thread, but I have a related question...

If other nodes in a cluster have access to CT/VM details like Name, then would it not be possible to display said info in the UI when logged into an active node?

FWIW an interesting observation: I am using Name as the sort key in the UI, and the VMs still look like they are sorted by Name, even though only the VMID is displayed.

 

[dcsapak]

If other nodes in a cluster have access to CT/VM details like Name, then would it not be possible to display said info in the UI when logged into an active node?

FWIW an interesting observation: I am using Name as the sort key in the UI, and the VMs still look like they are sorted by Name, even though only the VMID is displayed.

it only has a local view of those things, and if the other node is not in the same quorum partition, those infos are not reliable, e.g. if the current node is seperated from the remaining cluster, the vm name could have changed in the meantime