[SOLVED] [pvetest] Error when updating pve-manager from pvetest repo

SeerOfVoid

New Member
Aug 4, 2014
8
0
1
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:

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).

After that it shows:

Code:
Restarting PVE SPICE Proxy Server: spicepro.
Restarting PVE Status Daemon: pvestatd.
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?
 
Last edited:
OK, I went on my hunch and installed the 2nd latest pve-manager (3.2-4) from the pvetest repo, and no errors were thrown when it restarted the pvedaemon and pveproxy services, so thats's fixed. I'll have to file a bug report on pve-manager-3.2-18. Unfortunatly this means I can't take advantage of the new noVNC features, but I'm marking this as solved!
 
Last edited: