pveproxy not installed after upgrade to PVE 3.0

[be-team]

Hello experts,

after running pve-upgrade-2.3-to-3.0 I am left without web interface. Managing containers from the command line works. So far I figured out pveproxy has not been installed. There has been a certificate problem with winswitch, but I am not sure whether this is related to my problem.

root@proxmox:~# less pve-upgrade.log
Get:20 http://ftp.de.debian.org squeeze/main Sources [4541 kB]
Get:21 http://ftp.de.debian.org squeeze/contrib Sources [40.8 kB]
Get:22 http://ftp.de.debian.org squeeze/non-free Sources [73.3 kB]
Get:23 http://ftp.de.debian.org squeeze/main amd64 Packages [6540 kB]
Get:24 http://ftp.de.debian.org squeeze/contrib amd64 Packages [53.0 kB]
Get:25 http://ftp.de.debian.org squeeze/non-free amd64 Packages [102 kB]
Fetched 12.1 MB in 2s (4636 kB/s)
Reading package lists...
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://winswitch.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1367717527 KEYEXPIRED 1367717527 KEYEXPIRED 1367717527

W: Failed to fetch http://winswitch.org/dists/dists/squeeze/Release

W: Some index files failed to download, they have been ignored, or old ones used instead.
apt-get -f install
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 110 not upgraded.
apt-get install debian-archive-keyring

netstat -anp shows no prog listening on 8006. Accordingly, no web interface on https://myserver:8006. I also made sure apache was not running by # service apache2 stop.

Any help is appreciated!

Best regards
be-team

 

[be-team]

Solved: Purchased support subscription. Martin Maurer checked my upgrade log -> I had to update the winswitch key.

# echo "deb http://winswitch.org/ wheezy main" > /etc/apt/sources.list.d/winswitch.list;
# wget -O - http://winswitch.org/gpg.asc | apt-key add -

After that, re-run upgrade script. Yes, I have been told to remove unneeded non-proxmox packages from the system .

Thanks to Martin Maurer
be-team

 

[wahmed]

I did several upgrades from 2.3 to 3.0 on about 19 hosts. Never had this issue. I am not Linux savy enough to come to conclusion why the issue happened

 

[be-team]

Well, frankly, it was my fault. I installed some additional packages (among others from winswitch.org) meant to make life easier for me which caused the issue. The squeeze keys were not valid for wheezy, so the upgrade ran into errors. Anyway, fine support by Martin quickly identifying the problem.