[main] crit: Unable to resolve node name 'prox' to a non-loopback IP address - missing entry in '/etc/hosts' or DNS?

[jlobao86]

I am trying to rescue my proxmox server after a hardware failure. The BIOS was no longer recognizing my nvme ssd as a drive, it was just absent from the BIOS. But I have removed the nvme ssd from that machine and have it loaded in another machine and it boots and is recognized.

Initially it would boot to the normal welcome to proxmox screen with the access url. After changing the networking config appropriately, I am no longer rebooting to the main screen and am just getting the root@prox command line.

I can ping correctly, but things like apt update and apt upgrade stay on 0%. After scouring forums for three days, I am looking at the journal for the pve-cluster service and am seeing this critical error.

This is really the only error I see when using journalctl -xeu pve-cluster.service

prox was the name of my node, not my domain or anything so I'm not even sure why its suggesting network related issues?

Can someone please help its been daysssssss. At this point if I can just get my VMs off this drive some other way and just save what I have so I can reinstall on some other drive or something I'd be ecstatic. Only installed proxmox for the first time 2 weeks ago.

 

[amcmahon01]

I know this is old but in case you're still having this issue, double check your /etc/hosts and /etc/hostname if you haven't already. I had a similar issue and realized I had just mismatched things with a new IP during a change. (For reference: https://pve.proxmox.com/wiki/Renaming_a_PVE_node)