Please help ! my proxmox broken after update

M

mfr

New Member
Feb 3, 2017
6
0
1
36
please help.

i ran update via web gui, after that the system update in new window console.
And my proxmox cannot access now.

root@vm:~# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: not correctly installed (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: not correctly installed
corosync-pve: not correctly installed
libqb0: 1.0-1
pve-cluster: not correctly installed
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: not correctly installed
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
root@vm:~# service pve-cluster restart
root@vm:~# syslog
-bash: syslog: command not found
 
Hi,

mfr said:
And my proxmox cannot access now.
Click to expand...

You cannot access the WebUI, or the node via ssh or both?
As you posted some command line output I guess the Webinterface.

Can you try to reload the page first with empty browser cache (Shift + F5 or CTRL + R should do this).

If that does not help please post the output of
Code: 
systemctl status pve-manager


As a note:
mfr said:
root@vm:~# syslog
-bash: syslog: command not found
Click to expand...

under Systemd you may want to use journalctl for looking into logs
Code: 
journalctl

You can quit with pressing q, navigate with the keys (tip pressing G (big) brings you to the end of the log, pressing g (small) twice to the beginning).
 
thanks for you respon,

i can't access proxmox via web gui, but i can access the server via ssh. all vm on my proxmox cannot access. i think the proxmox service not running

root@vm:~# systemctl status pve-manager
● pve-manager.service - PVE VM Manager
Loaded: loaded (/lib/systemd/system/pve-manager.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-02-03 15:50:47 WIB; 43min ago
Process: 1547 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=2)
Main PID: 1547 (code=exited, status=2)

Feb 03 15:50:47 vm systemd[1]: pve-manager.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Feb 03 15:50:47 vm systemd[1]: Failed to start PVE VM Manager.
Feb 03 15:50:47 vm systemd[1]: Unit pve-manager.service entered failed state.
root@vm:~#
 
Do you have a cluster or a single PVE node?

Some more output would be great to be able to help:
Code: 
systemctl status pveproxy.service pvedaemon.service pve-cluster

systemctl list-units --failed

And only if you run a cluster:
Code: 
pvecm status
 
I have single PVE node. Pleas help

t.lamprecht said:
systemctl status pveproxy.service pvedaemon.service pve-cluster
Click to expand...

root@vm:~# systemctl status pveproxy.service pvedaemon.service pve-cluster
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-02-03 15:50:46 WIB; 1h 10min ago
Process: 1540 ExecStart=/usr/bin/pveproxy start (code=exited, status=2)

Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 751.
Feb 03 15:50:46 vm systemd[1]: pveproxy.service: control process exited, code=exited status=2
Feb 03 15:50:46 vm systemd[1]: Failed to start PVE API Proxy Server.
Feb 03 15:50:46 vm systemd[1]: Unit pveproxy.service entered failed state.

● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: exit-code) since Fri 2017-02-03 15:50:46 WIB; 1h 10min ago
Process: 1532 ExecStart=/usr/bin/pvedaemon start (code=exited, status=2)

Feb 03 15:50:46 vm pvedaemon[1532]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pvedaemon[1532]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pvedaemon[1532]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pvedaemon[1532]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Feb 03 15:50:46 vm pvedaemon[1532]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8, <DATA> line 751.
Feb 03 15:50:46 vm pvedaemon[1532]: Compilation failed in require at /usr/bin/pvedaemon line 11, <DATA> line 751.
Feb 03 15:50:46 vm pvedaemon[1532]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11, <DATA> line 751.
Feb 03 15:50:46 vm systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Feb 03 15:50:46 vm systemd[1]: Failed to start PVE API Daemon.
Feb 03 15:50:46 vm systemd[1]: Unit pvedaemon.service entered failed state.

● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
Active: active (running) since Fri 2017-02-03 16:12:16 WIB; 48min ago
Process: 1947 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1943 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Main PID: 1945 (pmxcfs)
CGroup: /system.slice/pve-cluster.service
└─1945 /usr/bin/pmxcfs

Feb 03 16:12:16 vm systemd[1]: Started The Proxmox VE cluster filesystem.


root@vm:~# systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● pve-firewall.service loaded failed failed Proxmox VE firewall
● pve-ha-crm.service loaded failed failed PVE Cluster Ressource Manager Daemon
● pve-ha-lrm.service loaded failed failed PVE Local HA Ressource Manager Daemon
● pve-manager.service loaded failed failed PVE VM Manager
● pvedaemon.service loaded failed failed PVE API Daemon
● pveproxy.service loaded failed failed PVE API Proxy Server
● pvestatd.service loaded failed failed PVE Status Daemon
● spiceproxy.service loaded failed failed PVE SPICE Proxy Server
● udev-finish.service loaded failed failed Copy rules generated while the root was ro

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

9 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@vm:~#
 
mfr said:
Active: failed (Result: exit-code) since Fri 2017-02-03 15:50:46 WIB; 1h 10min ago
Process: 1540 ExecStart=/usr/bin/pveproxy start (code=exited, status=2)

Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Click to expand...

The beginning of the error is cut off, so I need another output - hopefully the last:
Code: 
journalctl --since "-3h" -u pveproxy.service

The first few lines of the error message would be interesting.

Also:
Code: 
cat /etc/apt/sources.list
do you have valid repos configured?
 
I ran apt-get upgrade -f, then the pveversion -v show this,

root@vm:~# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: not correctly installed (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-72
pve-firmware: 1.1-10
libpve-common-perl: 4.0-90
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.7.1-1
pve-container: 1.0-62
pve-firewall: not correctly installed
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-1
lxcfs: 2.0.6-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie


t.lamprecht said:
journalctl --since "-3h" -u pveproxy.service
Click to expand...

root@vm:~# journalctl --since "-3h" -u pveproxy.service
-- Logs begin at Fri 2017-02-03 15:47:28 WIB, end at Fri 2017-02-03 17:25:41 WIB. --
Feb 03 15:47:43 vm systemd[1]: Starting PVE API Proxy Server...
Feb 03 15:47:43 vm systemd[1]: Starting PVE API Proxy Server...
Feb 03 15:47:43 vm pveproxy[1449]: Can't locate PVE/AbstractConfig.pm in @INC (you may need to install the PVE::AbstractConfig module) (@INC contains: /etc/perl /usr/lo
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 8, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 8, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 751.
Feb 03 15:47:43 vm pveproxy[1449]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 751.
Feb 03 15:47:43 vm systemd[1]: pveproxy.service: control process exited, code=exited status=2
Feb 03 15:47:43 vm systemd[1]: Failed to start PVE API Proxy Server.
Feb 03 15:47:43 vm systemd[1]: Unit pveproxy.service entered failed state.
Feb 03 15:50:46 vm systemd[1]: Starting PVE API Proxy Server...
Feb 03 15:50:46 vm pveproxy[1540]: Can't locate PVE/AbstractConfig.pm in @INC (you may need to install the PVE::AbstractConfig module) (@INC contains: /etc/perl /usr/lo
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 6, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 8, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 8, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/VZDump.pm line 19, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Backup.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 751.
Feb 03 15:50:46 vm pveproxy[1540]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 751.
Feb 03 15:50:46 vm systemd[1]: pveproxy.service: control process exited, code=exited status=2
Feb 03 15:50:46 vm systemd[1]: Failed to start PVE API Proxy Server.
Feb 03 15:50:46 vm systemd[1]: Unit pveproxy.service entered failed state.
lines 3-45/45 (END)


t.lamprecht said:
cat /etc/apt/sources.list
Click to expand...
root@vm:~# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian jessie main contrib


#deb http://ftp.debian.org/debian jessie main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use

#deb http://download.proxmox.com/debian jessie pve-no-subscription

# security updates
#deb http://security.debian.org jessie/updates main contrib
# security updates
deb http://security.debian.org jessie/updates main contrib

deb http://kambing.ui.ac.id/debian/ jessie main contrib non-free
deb http://kambing.ui.ac.id/debian/ jessie-updates main contrib non-free
deb http://kambing.ui.ac.id/debian-security/ jessie/updates main contrib non-free
root@vm:~#

i comment in #deb http://download.proxmox.com/debian jessie pve-no-subscription because there is some error like this

Reading package lists... Done
W: Duplicate sources.list entry http://download.proxmox.com/debian/ jessie/pve-no-subscription amd64 Packages (/var/lib/apt/lists/download.proxmox.com_debian_dists_jessie_pve-no-subscription_binary-amd64_Packages)
W: You may want to run apt-get update to correct these problems
 
Ok, this can be a failed upgrade error, you miss a new dependency (pve-guest-common). Please run
Code: 
apt update
apt dist-upgrade

Never use `apt-get upgrade`, it does not pulls in new dependencies and thus may result in problems, use either `apt-get dist-upgrade` or if you want a upgrade like behaviour which pulls in new dependencies then use `apt upgrade` (notice apt instead of apt-get). I know this is a little confusing.
 
Last edited:
mfr said:
i comment in #deb http://download.proxmox.com/debian jessie pve-no-subscription because there is some error like this
Click to expand...

Strange, you may have it defined elsewhere already, you could check with:
Code: 
grep -r "pve" /etc/apt/sources.list*

But that's not important right now, its just important that its already defined somewhere.
 
I have the same issues with two PVE hosts. Even after fresh installation of one system it is not reachable via https://...:8006
Version: pve-manager/4.4-12/e71b7a74 (running kernel: 4.4.35-2-pve).
 
t.lamprecht said:
Ok, this can be a failed upgrade error, you miss a new dependency (pve-guest-common). Please run
Code: 
apt update
apt dist-upgrade

Never use `apt-get upgrade`, it does not pulls in new dependencies and thus may result in problems, use either `apt-get dist-upgrade` or if you want a upgrade like behaviour which pulls in new dependencies then use `apt upgrade` (notice apt instead of apt-get). I know this is a little confusing.
Click to expand...

Great !!! its back to normal again .... thanks alot t.lamprecht .. sorry for my bad english.
 
t.lamprecht said:
Ok, this can be a failed upgrade error, you miss a new dependency (pve-guest-common). Please run
Code: 
apt update
apt dist-upgrade

Never use `apt-get upgrade`, it does not pulls in new dependencies and thus may result in problems, use either `apt-get dist-upgrade` or if you want a upgrade like behaviour which pulls in new dependencies then use `apt upgrade` (notice apt instead of apt-get). I know this is a little confusing.
Click to expand...

What is the best way to do a full upgrade and update? I was using
apt-get -y update && apt-get -y upgrade && apt-get -y dist-upgrade

So, that looks like it is wrong on two counts? should it be

apt-get -y update && apt -y upgrade && apt-get -y dist-upgrade
or
apt-get -y update && apt-get -y dist-upgrade && apt -y upgrade
or something else?
Thanks!
 
MikeP said:
What is the best way to do a full upgrade and update? I was using
apt-get -y update && apt-get -y upgrade && apt-get -y dist-upgrade

So, that looks like it is wrong on two counts? should it be

apt-get -y update && apt -y upgrade && apt-get -y dist-upgrade
or
apt-get -y update && apt-get -y dist-upgrade && apt -y upgrade
or something else?
Thanks!
Click to expand...


apt-get update && apt-get dist-upgrade
 
Ashley said:
apt-get update && apt-get dist-upgrade
Click to expand...
t.lamprecht said:
Ok, this can be a failed upgrade error, you miss a new dependency (pve-guest-common). Please run
Code: 
apt update
apt dist-upgrade

Never use `apt-get upgrade`, it does not pulls in new dependencies and thus may result in problems, use either `apt-get dist-upgrade` or if you want a upgrade like behaviour which pulls in new dependencies then use `apt upgrade` (notice apt instead of apt-get). I know this is a little confusing.
Click to expand...
Now, I'm confused.
 
Ashley said:
What are you confused about we both said the same thing.
Click to expand...
It looks different, Ashley wrote, "apt-get dist-upgrade", t.lamprecht states to use "apt dist-upgrade", and what about "apt upgrade" or apt-get upgrade"?
Other docs also say to use apt-get upgrade and apt-get dist-upgrade...
 
MikeP said:
It looks different, Ashley wrote, "apt-get dist-upgrade", t.lamprecht states to use "apt dist-upgrade", and what about "apt upgrade" or apt-get upgrade"?
Other docs also say to use apt-get upgrade and apt-get dist-upgrade...
Click to expand...
Hi Mike,
apt is the newer tool - do mostly the same like apt-get, but also more. You can also search with apt (before apt-cache search is needed).

Udo
 
  • Like
Reactions: MikeP
You must log in or register to reply here.
Top Bottom