Proxmox VE 3.2 released!

shim_ · Mar 18, 2014

Re: Cluster dies

7 hours after upgrade on all my proxmox servers:

Code:

[Sa Feb  8 03:25:07 2014] OOM selected worst BC 0 (overdraft 917462):[Sa Feb  8 03:25:07 2014] RAM: 3637771 / inf [0] SWAP: 339399 / inf [0] KMEM: 102768640 / inf [0] DCSZ: 52612536 / inf [0] OOMG: 3950121 / inf [0] Dirty 65 Wback 0 Dche 47042 Prnd 0
[Sa Feb  8 03:25:07 2014] Out of memory: OOM killed process 721222 (corosync) score 0 vm:13672324kB, rss:13510684kB, swap:0kB

cesarpk · Mar 19, 2014

Re: VM crashing during backup

dietmar said:
Backup works here. But I suggest that you simply test yourself, and if you find a bug, report it (Note: users also reports bugs for 3.1, 3.0, 2.3, 2,2, ...). We are usually quite fast in fixing bugs as soon as we have a reproducible test case.

Hi Dietmar

Only for know it:
1- what is the config of your "exports" file for NFS shared?
2- What you are using as an NFS server?
3- kernel scheduler is deadline or cfq?

Best regards
Cesar

dietmar · Mar 19, 2014

Re: VM crashing during backup

cesarpk said:
1- what is the config of your "exports" file for NFS shared?

nothing special (rw,sync,no_subtree_check,no_root_squash)

cesarpk said:
2- What you are using as an NFS server?

nfs-kernel-server on debian wheezy

cesarpk said:
3- kernel scheduler is deadline or cfq?

deadline

cesarpk · Mar 19, 2014

Re: VM crashing during backup

dietmar said:
nothing special (rw,sync,no_subtree_check,no_root_squash)
nfs-kernel-server on debian wheezy
deadline

Thanks Dietmar for your prompt response, I have the same configuration for nfs, but about the bug in "deadline", is the bug corrected in PVE 3.2 or 3.1?

Best regards
Cesar

dietmar · Mar 19, 2014

Re: VM crashing during backup

cesarpk said:
but about the bug in "deadline", is the bug corrected in PVE 3.2 or 3.1?

what bug?

cesarpk · Mar 20, 2014

Re: VM crashing during backup

dietmar said:
what bug?

Excuse me please, the bug is in cfq

Will have I troubles in my PVEs 2.3 if I change "cfq" a "deadline"?
Please think that these PVE Nodes have 1 NIC of 1 Gb/s for use with
1- The PVE Cluster network Communication,
2- VMs network Communication, and
3- Backups online (in the 1/2 night when the VMs have little activity)

Best regards
Cesar

chriszz · Mar 23, 2014

Dear Team,

I just updated one of my nodes to see whether everything is going all right. What I found is the following:

Everything works well - reboots and is up again with new software just after a few minutes - but when I check with pveversion -v, I get the following result:

- proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve)
- pve-manager: 3.2-1 (running version: 3.2-1/1933730b)
- pve-kernel-2.6.32-27-pve: 2.6.32-121
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.5-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.5-1
- pve-cluster: 3.0-12
- qemu-server: 3.1-15
- pve-firmware: 1.1-2
- libpve-common-perl: 3.0-14
- libpve-access-control: 3.0-11
- libpve-storage-perl: 3.0-19
- pve-libspice-server1: 0.12.4-3
- vncterm: 1.1-6
- vzctl: 4.0-1pve4
- vzprocps: 2.0.11-2
- vzquota: 3.1-2
- pve-qemu-kvm: 1.7-4
- ksm-control-daemon: 1.1-1
- glusterfs-client: 3.4.2-1

Everything all right - but it seems that I have two PVE-KERNELS? Why does that happen - and how can I get rid of the second kernel?

thanks and best regards
Christian

dietmar · Mar 23, 2014

chriszz said:
Everything all right - but it seems that I have two PVE-KERNELS? Why does that happen - and how can I get rid of the second kernel?

We do not remove older kernels automatically (so that you can still boot into them if something fails on update).
But you can easily remove them with dpkg:

# dpkg -r pve-kernel-2.6.32-26-pve

informant · Mar 24, 2014

Hi and thanks for this nice update. It works fine.

Do you add tutorials für vlan-switch in wiki?

best reagards

oermolaev · Mar 27, 2014

Proxmox VE 3.2 ISO Installer (from 10 March 2014 Version: 3.2-1933730b-2 MD5SUM for the ISO is c4ab21d04ac03e06be5377fd2429a6aa) don't work. That is, the installed OS is not booting. Proxmox VE 3.1 ISO Installer - it's OK

m.ardito · Mar 27, 2014

oermolaev said:
Proxmox VE 3.2 ISO Installer (from 10 March 2014 Version: 3.2-1933730b-2 MD5SUM for the ISO is c4ab21d04ac03e06be5377fd2429a6aa) don't work. That is, the installed OS is not booting. Proxmox VE 3.1 ISO Installer - it's OK

probably that is on your system. maybe some particular hardware or so, but generally if you can describe the hardware, a solution can be found. I have tried exactly that ISO and I was able to install it. Could it be a bad download? My iso has 567279616 bytes and md5sum -b is "c4ab21d04ac03e06be5377fd2429a6aa"

Marco

oermolaev · Mar 28, 2014

I too have iso: size 567279616, md5sum c4ab21d04ac03e06be5377fd2429a6aa */dev/sr1.
I used emulator CD Zalman ZM-VE300.
lshw included

m.ardito · Mar 28, 2014

m.ardito said:
generally if you can describe the hardware, a solution can be found.

ie: if someone else has or has tested with your hardware, or knows if it should work, could help you

Marco

Alectronic · Apr 2, 2014

oermolaev said:
Proxmox VE 3.2 ISO Installer (from 10 March 2014 Version: 3.2-1933730b-2 MD5SUM for the ISO is c4ab21d04ac03e06be5377fd2429a6aa) don't work. That is, the installed OS is not booting. Proxmox VE 3.1 ISO Installer - it's OK

I am having a similar issue. I am trying to run this on a new Mac Mini 6.1 but when I get to the boot screen with the proxmox and hit return to boot it just give me a black screen. any ideas?

oermolaev · Apr 2, 2014

Alectronic said:
...any ideas?...

Do you tried Proxmox VE 3.1 ISO Installer?

m.ardito · Apr 2, 2014

Alectronic said:
any ideas?

ISO should work, but some hardware may cause issues. You could try also installing debian wheezy, and then pve on it.

See the wiki for specific instructions: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy

Marco

KP7 · Apr 4, 2014

Hello,
We have to node cluster ver. 3.1. (with registered subscription)
Node1: 2CPU socket
Node2: 1CPU socket
One node updated to latest 3.2 without problem (Node2), but on Node1 apt-get update shows:
Hit http://ftp.pl.debian.org wheezy Release.gpg
Hit http://ftp.pl.debian.org wheezy Release
Hit http://ftp.pl.debian.org wheezy/main amd64 Packages
Hit http://ftp.pl.debian.org wheezy/contrib amd64 Packages
Hit http://ftp.pl.debian.org wheezy/main i386 Packages
Hit http://ftp.pl.debian.org wheezy/contrib i386 Packages
Hit http://ftp.pl.debian.org wheezy/contrib Translation-en
Hit http://ftp.pl.debian.org wheezy/main Translation-en
Hit http://security.debian.org wheezy/updates Release.gpg
Hit https://enterprise.proxmox.com wheezy Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit https://enterprise.proxmox.com wheezy Release
Hit https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://security.debian.org wheezy/updates/main i386 Packages
Hit http://security.debian.org wheezy/updates/contrib i386 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/Release Unable to find expected entry 'pve-enterprise/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

# pveversion -v
proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.2-1 (running version: 3.2-1/1933730b)
pve-kernel-2.6.32-27-pve: 2.6.32-121
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.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

Same iso was used for both nodes. Any ideas? Is it safe to dist-upgrade?

Regards
KP7

dietmar · Apr 7, 2014

KP7 said:
Same iso was used for both nodes. Any ideas? Is it safe to dist-upgrade?

pls contact https://shop.maurer-it.com/contact.php and tell your subscription key there.

tom · Apr 8, 2014

KP7 said:
...

W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/Release Unable to find expected entry 'pve-enterprise/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

...

Proxmox VE is 64-bit only (amd64), so there are no i386 packages.

seems you did some custom settings on your box, querying i386 packages which are do not exist.

mo_ · Apr 11, 2014

Ive actually seen that happen too once on a fresh and vanilla proxmox 3.2 install (from iso, no debian->proxmox). Heres what I put on the wiki about it:

NOTE: Due to a bug in debian/apt(?) it may be required to alter the above sources.list entry to say the following, if apt-get complains about not being able to find /binary-i386: "Unable to find expected entry 'pve/binary-i386/Packages'" (despite it being a 64bit install!)

deb [arch=amd64] http://download.proxmox.com/debian wheezy pve

Adding this [arch=amd64] bit should work the same for the repository you're trying to use.

Proxmox VE 3.2 released!

New Member

Well-Known Member

Proxmox Staff Member

Well-Known Member

Proxmox Staff Member

Well-Known Member

New Member

Proxmox Staff Member

Renowned Member

Active Member

Active Member

Active Member

Attachments

Active Member

Alectronic

Guest

Active Member

Active Member

Member

Proxmox Staff Member

Proxmox Staff Member

Active Member