Web GUI and VMs doesnt work

[Patrik Olsson]

Ladies and Gentlemen,

I managed to make a little mistake.
On a Proxmox 3.1 I through bad knowledge assigned in the shell 'apt-get install qemu-kvm'
After that things went haywire and Web GUI stopped working. And no containers and VMs were working either.

After studying some serious Google results I managed to deinstall qemu-kvm (I think...).
And then I went through the procedure to reinstall Proxmox using the non enterprise repo for Debian Wheezy.

After the reinstall and reboot, containers are working fine (Open VZ), but the Web GUI and VMs are not working. Trying to start pveproxy and some other services reveals it is strange PERL errors stopping stuff from starting properly. For instance:

root@proxmox:~# /etc/init.d/pveproxy start
Starting PVE API Proxy Server: pveproxyUse of inherited AUTOLOAD for non-method PVE::CLIHandler::handle_cmd() is deprecated at /usr/bin/pveproxy line 150.
Can't call method "map_method_by_name" on unblessed reference at /usr/share/perl5/PVE/RESTHandler.pm line 278.
(warning).
root@proxmox:~#

and

root@proxmox:~# /etc/init.d/spiceproxy start
Starting PVE SPICE Proxy Server: spiceproxyUse of inherited AUTOLOAD for non-method PVE::CLIHandler::handle_cmd() is deprecated at /usr/bin/spiceproxy line 96.
Can't call method "map_method_by_name" on unblessed reference at /usr/share/perl5/PVE/RESTHandler.pm line 278.
(warning).
root@proxmox:~#

and

root@proxmox:~# /etc/init.d/pvedaemon start
Starting PVE Daemon: pvedaemonUse of inherited AUTOLOAD for non-method PVE::CLIHandler::handle_cmd() is deprecated at /usr/bin/pvedaemon line 86.
Can't call method "map_method_by_name" on unblessed reference at /usr/share/perl5/PVE/RESTHandler.pm line 278.
failed!
root@proxmox:~#

I guess I either have to manually resolve PERL errors, but I would like to reinstall Proxmox 3.1 and force its dependencies to get things working again. That said, I dont want existing VMs and Containers to be deleted, I need them working too.

Any ideas?

Thanks
Patrik

 

[LnxBil]

Why not update to the newest version of wheezy and Proxmox 3.4?

It'll be very hard to restore all your packages without knowing the exact version numbers - maybe impossible.

 

[Patrik Olsson]

I agree with your observation. It was a Proxmox 3.1 installation from the ISO disk. And a wheezy apt-get update && apt-get dist-upgrade today.

What disturbs me is how some perl PMs can be missing or not execute correctly when I reinstall Proxmox 3.1 and thought that dependencies and missing files would be installed.

Well, I managed to migrate all VMs and Containers to another Proxmox cluster, so I have free hands now. Will ty an upgrade to Proxmox 4.latest and see if I get a functional system. Or I will will reinstall form an ISO to get a fresh system to work with.

Thanks
Patrik

Attaching an output from dpkg -l (current state)

 

[Patrik Olsson]

After a sccessful migrationof VMs and Conatiners to another Proxmox 3.1 cluster, I upgraded the "broken" standalone Proxmox. Eventhough an update from 3.1 -> 3.4 did not solve my problem, an upgrade from 3.4 -> 4.latest did. I also kept a copy of the migrated VMs and they work! Containers of course dont work since there is a change from OpenVZ->LXC and it also a part of upgrade procedure to remove all comtainers (config and private area). All templates I had made for conatiners survived the upgrade and work, unless the template is depending on a kernel lower than the new upgraded kernel on the Proxmox 4.x system.

Just FYI. Thanks for reading!