View source for PVE Troubleshooting

For some reason, the denizens of the Internet assume that all difficulties when using PVE stem from screwing up your cluster.&nbsp; This is kind of odd when you consider that, sometimes, PVE servers run on their own...
== qm commands fail hard ==
Example:
<syntaxhighlight lang="sh">
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
</syntaxhighlight>

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 <code>/etc/hostname</code>

In our example, it'll look like:
<syntaxhighlight lang="ini">
proxmox-pve
</syntaxhighlight>

Now, if <code>/etc/hosts</code> contains:
<syntaxhighlight lang="ini">
127.0.0.1 localhost.localdomain localhost
192.168.1.2 pve.nerdmage.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
</syntaxhighlight>

poor PVE is gonna be confused.

That second line should be:
<syntaxhighlight lang="ini">
192.168.1.2 proxmox-pve.nerdmage.ca proxmox-pve
</syntaxhighlight>

Once that's fixed, restarting the machine should get things back to a working state.