Difference between revisions of "PVE Troubleshooting"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== qm commands fail hard == | == qm commands fail hard == | ||
Example: | Example: | ||
<syntaxhighlight lang="sh"> | <syntaxhighlight lang="sh"> | ||
root@proxmox-pve:~# qm list | root@proxmox-pve:~# qm list | ||
Revision as of 13:17, 17 July 2022
For some reason, the denizens of the Internet assume that all difficulties when using PVE stem from screwing up your cluster. This is kind of odd when you consider that, sometimes, PVE servers run on their own...
qm commands fail hard
Example:
root@proxmox-pve:~# qm list
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused
Nearly every Google hit is discussion about how to get your cluster working again... :|
The actual problem, OTOH... Appears to be that, if your hostname doesn't match what's in /etc/hosts qm gets lost...
Take a look at /etc/hostname
In our example, it'll look like:
proxmox-pve
Now, if /etc/hosts contains:
127.0.0.1 localhost.localdomain localhost
192.168.1.2 pve.tinkernet.ca pve
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
poor PVE is gonna be confused.
That second line should be:
192.168.1.2 proxmox-pve.tinkernet.ca proxmox-pve