Difference between revisions of "PVE Troubleshooting"
Jump to navigation
Jump to search
(Created page with "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: <code></code><pre> <code> 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 li...") |
|||
| Line 3: | Line 3: | ||
Example: | Example: | ||
<pre> | |||
root@proxmox-pve:~# qm list | root@proxmox-pve:~# qm list | ||
ipcc_send_rec[1] failed: Connection refused | ipcc_send_rec[1] failed: Connection refused | ||
| Line 10: | Line 9: | ||
ipcc_send_rec[3] failed: Connection refused | ipcc_send_rec[3] failed: Connection refused | ||
Unable to load access control list: Connection refused | Unable to load access control list: Connection refused | ||
</pre> | |||
Revision as of 14:00, 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