Release Information

A

Antonino89

Member
Jul 13, 2017
76
1
6
36
Hi guys,

Does this output means that my proxmox 4.4 version is now correctly upgraded to proxmox 5.0?

root@Server1:/var/lib/vz/template/iso# pveversion
pve-manager/5.0-23/af4267bf (running kernel: 4.4.35-1-pve)

after the upgrade procedure i still see running kernel: 4.4.35-1-pve.

Is that right?

Thanks
 
willy1009 said:
Hi,

Please post pveversion -v output
Click to expand...

Hi... :)

Here we go.

root@Server1:/var/lib/vz/template/iso# pveversion -v
proxmox-ve: 5.0-15 (running kernel: 4.4.35-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.4.35-1-pve: 4.4.35-76
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-8
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

Thanks.
 
You have to reboot to load the 4.10 kernel.
 
wolfgang said:
You have to reboot to load the 4.10 kernel.
Click to expand...

Hi...

Done. Now it should be okay. Right?

root@Server1:~# pveversion -v
proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.4.35-1-pve: 4.4.35-76
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-8
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

Thanks
 
I did the same procedure (in order to upgrade it) on the second server, but i think somethings went wrong...

root@Server2:~# pveversion -v
bash: pveversion: command not found

What does it means? :(
 
Failed to reload-or-restart pve-firewall.service: Unit pve-firewall.service is masked.
dpkg: error processing package pve-firewall (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-firewall
qemu-server
proxmox-ve
pve-manager
pve-ha-manager
pve-container
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@Server2:/etc/apt/sources.list.d# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.4.35-1-pve)
pve-manager: not correctly installed (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.4.35-1-pve: 4.4.35-76
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: not correctly installed
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-8
pve-qemu-kvm: 2.9.0-2
pve-container: not correctly installed
pve-firewall: not correctly installed
pve-ha-manager: not correctly installed
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

Now the pveversion -v command works, but sims there's not proxmox-ve installed, any suggestions?

Thanks
 
try
Code: 
systemctl unmask pve-firewall
apt-get -f install
 
You must log in or register to reply here.
Top Bottom