[PVE-User] proxmox-ve: 5.4-2 can't access webinterface after update

[Thomas Lamprecht]

Hi,

On 11/25/19 6:14 AM, kai at zimmer.net wrote:
> Hi,
> i updated my Proxmox VE Host (via 'apt-get update; apt-get upgrade').

That's the wrong way to upgrade a Proxmox VE host[0] and is probably the
cause for your problems. Use

apt-get update
apt-get dist-upgrade

or the more modern interface:
apt update
apt full-upgrade

[0]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_system_software_updates

> Now the web interface is not accessible anymore. Additionally i have
> disconnected network devices in the webinterface before the update. I
> can start the VMs via 'qm start 100', but they cannot get network (and i
> don't know how to fix this on the command line).
> To fix the web interface i tried 'service pveproxy restart' and 'service
> pvedaemon restart' - with no success.
> To fix the network in the VMs i tried 'qm set 100 --net0
> model=virtio,link_down=1' and 'qm set 100 --net0
> model=virtio,link_down=0' - also without success.

> proxmox-ve: 5.4-2 (running kernel: 4.15.18-7-pve)

Proxmox VE 5.4-2 is latest from this year, ok, but

> pve-manager: 5.2-10 (running version: 5.2-10/6f892b40)

this manager version is from fall 2018, and highly probable incompatible
with the rest of the stack - other packages may have this issue too..

> pve-kernel-4.15: 5.2-10
> pve-kernel-4.13: 5.2-2
> pve-kernel-4.15.18-7-pve: 4.15.18-27
> pve-kernel-4.15.18-4-pve: 4.15.18-23
> pve-kernel-4.13.16-4-pve: 4.13.16-51
> pve-kernel-4.13.16-1-pve: 4.13.16-46
> pve-kernel-4.13.13-4-pve: 4.13.13-35
> pve-kernel-4.4.98-3-pve: 4.4.98-103
> corosync: 2.4.4-pve1
> criu: 2.11.1-1~bpo90
> glusterfs-client: 3.8.8-1
> ksm-control-daemon: 1.2-2
> libjs-extjs: 6.0.1-2
> libpve-access-control: 5.0-8
> libpve-apiclient-perl: 2.0-5
> libpve-common-perl: 5.0-41
> libpve-guest-common-perl: 2.0-18
> libpve-http-server-perl: 2.0-14
> libpve-storage-perl: 5.0-30
> libqb0: 1.0.3-1~bpo9
> lvm2: 2.02.168-pve6
> lxc-pve: 3.1.0-7
> lxcfs: 3.0.3-pve1
> novnc-pve: 1.0.0-3
> proxmox-widget-toolkit: 1.0-28
> pve-cluster: 5.0-38
> pve-container: 2.0-29
> pve-docs: 5.4-2
> pve-firewall: 3.0-22
> pve-firmware: 2.0-7
> pve-ha-manager: 2.0-9
> pve-i18n: 1.1-4
> pve-libspice-server1: 0.14.1-2
> pve-qemu-kvm: 3.0.1-4
> pve-xtermjs: 3.12.0-1
> qemu-server: 5.0-38
> smartmontools: 6.5+svn4324-1
> spiceterm: 3.0-5
> vncterm: 1.5-3
> # service pveproxy status
> ● pveproxy.service - PVE API Proxy Server
> Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor
> preset: enabled)
> Active: active (running) since Mon 2019-11-25 05:10:18 CET; 24min ago
> Process: 7797 ExecStop=/usr/bin/pveproxy stop (code=exited,
> status=0/SUCCESS)
> Process: 7803 ExecStart=/usr/bin/pveproxy start (code=exited,
> status=0/SUCCESS)
> Main PID: 7830 (pveproxy)
> Tasks: 4 (limit: 19660)
> Memory: 123.4M
> CPU: 2.107s
> CGroup: /system.slice/pveproxy.service
> ├─7830 pveproxy
> ├─7833 pveproxy worker
> ├─7834 pveproxy worker
> └─7835 pveproxy worker
> Nov 25 05:31:36 holodoc pveproxy[7835]: Can't locate object method
> "set_request_host" via package "PVE::RPCEnvironment" at
> /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1206.
> Nov 25 05:31:41 holodoc pveproxy[7835]: problem with client
> 192.168.1.86; Connection timed out
> # service pvedaemon status
> ● pvedaemon.service - PVE API Daemon
> Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor
> preset: enabled)
> Active: active (running) since Mon 2019-11-25 05:11:16 CET; 25min ago
> Process: 7991 ExecStop=/usr/bin/pvedaemon stop (code=exited,
> status=0/SUCCESS)
> Process: 8001 ExecStart=/usr/bin/pvedaemon start (code=exited,
> status=0/SUCCESS)
> Main PID: 8021 (pvedaemon)
> Tasks: 4 (limit: 19660)
> Memory: 114.8M
> CPU: 1.791s
> CGroup: /system.slice/pvedaemon.service
> ├─8021 pvedaemon
> ├─8024 pvedaemon worker
> ├─8025 pvedaemon worker
> └─8026 pvedaemon worker
> Nov 25 05:11:15 holodoc systemd[1]: Starting PVE API Daemon...
> Nov 25 05:11:16 holodoc pvedaemon[8021]: starting server
> Nov 25 05:11:16 holodoc pvedaemon[8021]: starting 3 worker(s)
> Nov 25 05:11:16 holodoc pvedaemon[8021]: worker 8024 started
> Nov 25 05:11:16 holodoc pvedaemon[8021]: worker 8025 started
> Nov 25 05:11:16 holodoc pvedaemon[8021]: worker 8026 started
> Nov 25 05:11:16 holodoc systemd[1]: Started PVE API Daemon.
> Any ideas how to fix this?
> Best regards,
> Kai
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user