I had ran into some problems on my proxmox install and ended up formatting the HDDs and re-installing from the latest 3.2 ISO. The installation ran flawlessly, but when I went and ran "apt-get update pve-manager", it threw these errors:
After that it shows:
As if nothing had gone wrong....
I promptly went to check the web GUI and it fails to load giving an "ERR_CONNECTION_REFUSED". Great, now my node is useless and I have no clue what to do.
I tried "apt-get remove pve-manager" and it runs successfully, also it updates my kernel from 2.6.32-29 to 2.6.32-31. I restart the pvedaemon service and the pveproxy service, still no luck. Is this a bug with the latest pve-manager? Should I try to install an older one?
Code:
Restarting PVE Daemon: pvedaemon unabe to find handler for 'GET: /access/ticket' at usr/share/per15/PVE/RESTHandler.pm line260.
Compilation failed in require at /usr/bin/pvedaemon line 16.
Begin failed--compilation aborted at /usr/bin/pvedaemon line 16.
(warning).
Restarting PVE API Proxy unabe to find handler for 'GET: /access/ticket' at usr/share/per15/PVE/RESTHandler.pm line260.
Compilation failed in require at /usr/bin/pveproxy line 24.
Begin failed--compilation aborted at /usr/bin/pveproxy line 24.
(warning).Code:
Restarting PVE SPICE Proxy Server: spicepro.
Restarting PVE Status Daemon: pvestatd.I promptly went to check the web GUI and it fails to load giving an "ERR_CONNECTION_REFUSED". Great, now my node is useless and I have no clue what to do.
I tried "apt-get remove pve-manager" and it runs successfully, also it updates my kernel from 2.6.32-29 to 2.6.32-31. I restart the pvedaemon service and the pveproxy service, still no luck. Is this a bug with the latest pve-manager? Should I try to install an older one?