Issue after upgrade Proxmox 4.3 -> 4.4

Y

yellow-cake

New Member
Feb 17, 2016
15
0
1
32
Hello,

Since I did update a node of my PROXMOX cluster, I have some issues. Indeed after :

apt-get update

apt-get upgrade

I reboot my server but he don't reboot correctly. In fact when I look my cluster, this node is unavailable.

do you have an idea ?
 
Hi,

you have to use
apt-get dist-upgrade
 
please always upgrade with
Code: 
apt-get update
apt-get dist-upgrade

did you get any error messages on upgrade?
does the node boot?
can you login via ssh?
 
Sorry i used apt-get dist-upgrade, this is an error of write in my first post. I followed the documentation http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_4.x_to_latest_4.2 .

I don't remember some errors after theses 2 commands.

I can login via ssh.

I can boot only if I use config-4.4.35-1-pve (by default this is config-4.4.35-2-pve). I modify this during the grub (With the E key)

edit : if i don't change "config-4.4.35-2-pve" i stay blocked on ramdisk test ..
 
boot into 4.4.35-1 and run
"apt-get install -f"
"dpkg --configure -a"
"update-initramfs -u -k 4.4.35-2-pve"
 
Thank for your return.

I tried your suggest: (i tried to update initramfs despite that the previous 2 commands have not worked)

root@node:~# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-manager (4.4-5) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@node:~# uname -a
Linux node 4.4.35-1-pve #1 SMP Thu Dec 22 14:58:39 CET 2016 x86_64 GNU/Linux
root@node:~# dpkg --configure -a
Setting up pve-manager (4.4-5) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pve-manager
root@node:~# update-initramfs -u -k 4.4.35-2-pve
update-initramfs: Generating /boot/initrd.img-4.4.35-2-pve

This is a common issue in this update?

Thank you.


Edit : When I try to use some commands like pveversion -v or pvecm status, i had this :


root@node:~# pvecm status
Global symbol "%str" requires explicit package name at /usr/share/perl5/XML/Twig.pm line 4585.
syntax error at /usr/share/perl5/XML/Twig.pm line 4585, at EOF
Missing right curly or square bracket at /usr/share/perl5/XML/Twig.pm line 4585, at end of line
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus/Binding/Introspector.pm line 57.
BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus/Binding/Introspector.pm line 57.
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus/RemoteObject.pm line 58.
BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus/RemoteObject.pm line 58.
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus/RemoteService.pm line 55.
BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus/RemoteService.pm line 55.
Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus.pm line 97.
BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.20/Net/DBus.pm line 97.
Compilation failed in require at /usr/share/perl5/PVE/Tools.pm line 25.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Tools.pm line 25.
Compilation failed in require at /usr/share/perl5/PVE/INotify.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/INotify.pm line 16.
Compilation failed in require at /usr/bin/pvecm line 6.
BEGIN failed--compilation aborted at /usr/bin/pvecm line 6.
 
Last edited:
that sounds like a corrupted file - the mentioned line should contain $str , not %str (note that '$' and '%' are just one bit different!). you can try reinstalling the offending package, but there might be a lot more broken than just that single file.. (note that this has nothing to do with PVE whatsoever - it's a file provided by Debian which has not been updated since 2014..)
 
Ok, I see.

I think i'll remove this node and reinstall it from scratch in order to re-add it in my cluster.

Thank's for your help !
 
You must log in or register to reply here.
Top Bottom
Back