Upgrade path for 3.2-4 system?

cdsJerry · Mar 24, 2017

We're a tiny business (three people) using Proxmox 3.2-4 to run three VMs on an 8 core machine. I haven't been on the forums for a long time as everything was stable and our tiny company is barely surviving. To say money is tight would be an understatement.

Firefox just dropped support for Java so I no longer have a way to log into the console in Proxmox when a VM doesn't start correctly. I haven't been in the Proxmox forum for a long time. I know my system is out of date but I couldn't afford the new license fees. I don't even know what those fees are now.

So since Java isn't working I'm trying to figure out my best solution and how to get there. I'm a bit of a propeller-head but not nearly on the level as most of you guys.

Current version 3.2-4 8 X Intel Xeon CPU X3440 @ 2.53 GHz (1 socket) 24GB RAM Installed from distro, Linux 2.6.32-29

isg_itadmin · Mar 24, 2017

you would probably want to upgrade to 3.4 first to get to a level where higher upgrades are possible.
https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_3.x_to_latest_3.4

Then you would upgrade to the 4.0 series
https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0

Since you only have 3 VM's, it may be just a useful and expedient to backup each vm, export it to external storage and then rebuild your machine using a fresh install of 4.4. You would then restore your machines from backup and start again with a fresh system.

https://pve.proxmox.com/wiki/Backup_-_Restore_-_Live_Migration
http://cyberpersons.com/2016/09/13/backup-transfer-proxmox-vm-another-proxmox-node/

cdsJerry · Mar 24, 2017

Oh man! I think I just went from the frying pan into the fire. On the update tab there were a bunch of packages listed that needed updated. Like a fool I told it to update. Now I can't access the GUI at all. This is bad.

udo · Mar 24, 2017

cdsJerry said:
Oh man! I think I just went from the frying pan into the fire. On the update tab there were a bunch of packages listed that needed updated. Like a fool I told it to update. Now I can't access the GUI at all. This is bad.

Hi,
have you tried the simple trick? Clear Browser cache?

Which version is running now? "pveversion -v"

Udo

isg_itadmin · Mar 24, 2017

There is some additional information in the first post here:
https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_3.x_to_latest_3.4

Regarding if you make the mistake of using the GUI instead of the CLI. That information may be of help but use with caution.

You may also want to see about doing cli backups of your running VM's incase you need to rebuild.

cdsJerry · Mar 24, 2017

udo said:
Hi,
have you tried the simple trick? Clear Browser cache?

Which version is running now? "pveversion -v"

Udo

I did clear the cache and even tried two other machines. No joy. I have access via Putty but otherwise none.
I hate to admit it, but I don't know how to do container backups with the cli as I'm so dependant on the GUI. I have several VMs on the machine that I'm not using that I created for testing etc. I'm not even sure what numbers the three VMs I need are. I'm in deep poo poo here.

I thought about restarting the server to see what happens but at some point I need to stop digging myself deeper.

proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-29-pve)
pve-manager: not correctly installed (running version: 3.4-16/40ccc11c)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: not correctly installed
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: not correctly installed
pve-cluster: not correctly installed
qemu-server: not correctly installed
pve-firmware: not correctly installed
libpve-common-perl: not correctly installed
libpve-access-control: not correctly installed
libpve-storage-perl: not correctly installed
pve-libspice-server1: 0.12.4-3
vncterm: not correctly installed
vzctl: not correctly installed
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: not correctly installed
ksm-control-daemon: 1.1-1
glusterfs-client: not correctly installed

udo · Mar 24, 2017

cdsJerry said:
I did clear the cache and even tried two other machines. No joy. I have access via Putty but otherwise none.
I hate to admit it, but I don't know how to do container backups with the cli as I'm so dependant on the GUI. I have several VMs on the machine that I'm not using that I created for testing etc. I'm not even sure what numbers the three VMs I need are. I'm in deep poo poo here.

I thought about restarting the server to see what happens but at some point I need to stop digging myself deeper.

proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-29-pve)
pve-manager: not correctly installed (running version: 3.4-16/40ccc11c)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: not correctly installed
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: not correctly installed
pve-cluster: not correctly installed
qemu-server: not correctly installed
pve-firmware: not correctly installed
libpve-common-perl: not correctly installed
libpve-access-control: not correctly installed
libpve-storage-perl: not correctly installed
pve-libspice-server1: 0.12.4-3
vncterm: not correctly installed
vzctl: not correctly installed
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: not correctly installed
ksm-control-daemon: 1.1-1
glusterfs-client: not correctly installed

Hi,
do following on the sonsole and post the output:

Code:

cat /etc/apt/sources.d/*

apt-get update

apt-get dist-upgrade

to see which VMs has which number:

Code:

qm list
vzlist

Udo

udo · Mar 24, 2017

… and post the output of following:

Code:

df -h

Udo

cdsJerry · Mar 24, 2017

root@live:~# cat /etc/apt/sources.d/*
cat: /etc/apt/sources.d/*: No such file or directory

root@live:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 2.4G 428K 2.4G 1% /run
/dev/mapper/pve-root 95G 2.6G 88G 3% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 4.8G 38M 4.7G 1% /run/shm
/dev/mapper/pve-data 1.9T 1.2T 712G 63% /var/lib/vz
/dev/sdb1 495M 150M 320M 32% /boot
/dev/sda1 1.8T 1.1T 667G 62% /backups
192.168.2.114:/mnt/pools/A/A0/Backups 1.8T 1.1T 816G 56% /mnt/pve/Backups-IOMEGA
192.168.2.126:/mnt/HD/HD_a2/ProxNAS3 2.8T 1.3T 1.5T 45% /mnt/pve/ProxNas3
192.168.2.89:/nfs/ProxmoxStore 2.8T 1.4T 1.4T 52% /mnt/pve/WDnas2
/dev/fuse 30M 20K 30M 1% /etc/pve

cdsJerry · Mar 24, 2017

I have access to the GUI again!!! <whew>

Not sure I have the nerve to try to update again. That was scary.

udo · Mar 24, 2017

cdsJerry said:
root@live:~# cat /etc/apt/sources.d/*
cat: /etc/apt/sources.d/*: No such file or directory

sorry, mean

Code:

cat /etc/apt/sources.list.d/*

Udo

udo · Mar 24, 2017

cdsJerry said:
I have access to the GUI again!!! <whew>

Not sure I have the nerve to try to update again. That was scary.

Hi,
and how looks "pveversion -v" now?

BTW. OpenVZ is not supported with pve4 - so your container must run as lxc-container. AFAIK backup on the old system and restore...

should tested before on an test-system.

udo

cdsJerry · Mar 24, 2017

root@live:~# cat /etc/apt/sources.list.d/*
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

cdsJerry · Mar 24, 2017

root@live:~# pveversion -v
proxmox-ve-2.6.32: 3.4-185 (running kernel: 2.6.32-29-pve)
pve-manager: 3.4-16 (running version: 3.4-16/40ccc11c)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-48-pve: 2.6.32-185
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-20
qemu-server: 3.4-9
pve-firmware: 1.1-6
libpve-common-perl: 3.0-27
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-35
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-28
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@live:~#

udo · Mar 24, 2017

cdsJerry said:
root@live:~# cat /etc/apt/sources.list.d/*
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

Hm,
and "cat /etc/apt/sources.list"? otherwise you don't get any updates, if you don't have pve-no-subscription enabled.

Udo

cdsJerry · Mar 24, 2017

root@live:~# cat /etc/apt/sources.list
deb http://ftp.us.debian.org/debian wheezy main contrib

# PVE no-subscription packages provided by proxmox.com
deb http://download.proxmox.com/debian wheezy pve-no-subscription

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

udo · Mar 24, 2017

ok,
i go sleep

cdsJerry · Mar 24, 2017

I get lost on the various environments. I'm currently running three VMs (two Windows 2008 servers and one Windows 7 Pro machine). I tried to run FreePBX on another VM but was never able to make it work without a lot of jitter so I went back to a physical machine.

You're saying in the updated Proxmox I can't run those as VMs? It's now something called an lxc container? Maybe if my system is working now I should just leave it alone forever. I about had a heart attack when it stopped.

cdsJerry · Mar 24, 2017

udo said:
ok,
i go sleep

THANK YOU!!!!! For staying up long enough to help me.

udo · Mar 25, 2017

cdsJerry said:
I get lost on the various environments. I'm currently running three VMs (two Windows 2008 servers and one Windows 7 Pro machine). I tried to run FreePBX on another VM but was never able to make it work without a lot of jitter so I went back to a physical machine.

Hi,
this are kvm-VM, which can migrate to an new pve-version without trouble (still kvm).
Do you have any Open-VZ container running?? OpenVZ - the container tecnologie war replaced wit lxc.

You're saying in the updated Proxmox I can't run those as VMs? It's now something called an lxc container? Maybe if my system is working now I should just leave it alone forever. I about had a heart attack when it stopped.

To stay on such an old Version is an bad idea - you don't get any security fixes...

Udo

Upgrade path for 3.2-4 system?

Renowned Member

New Member

Renowned Member

Distinguished Member

New Member

Renowned Member

Distinguished Member

Distinguished Member

Renowned Member

Renowned Member

Distinguished Member

Distinguished Member

Renowned Member

Renowned Member

Distinguished Member

Renowned Member

Distinguished Member

Renowned Member

Renowned Member

Distinguished Member