Java crash with Zimbra OpenVZ after upgrade proxmox 1.8 to 1.9

M

mmenaz

Renowned Member
Jun 25, 2009
838
29
93
Northern east Italy
Is the second server where this happens, for the first one I thought was a Zimbra problem, but now I'm sure that is related with Proxmox.
I've Zimbra installed in a OpenVZ container upon debian-5.0-standard_5.0-2_i386
After Proxmox upgrade, Jetty crashes and I've a long, impossible for me to understand, core dump.
I had
Code: 
# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6

and then I upgraded to 1.9
Code: 
proxmox:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

The vm is set to have
HD 100GB
Memory: 3584
Swap: 3584

and it's settings are:
Code: 
# PVE default config for 256MB RAM

ONBOOT="yes"

# Primary parameters
NUMPROC="1024:1024"
NUMTCPSOCK="9223372036854775807:9223372036854775807"
NUMOTHERSOCK="9223372036854775807:9223372036854775807"
VMGUARPAGES="1835008:9223372036854775807"

# Secondary parameters
KMEMSIZE="9223372036854775807:9223372036854775807"
OOMGUARPAGES="1835008:9223372036854775807"
PRIVVMPAGES="1835008:1847508"
TCPSNDBUF="9223372036854775807:9223372036854775807"
TCPRCVBUF="9223372036854775807:9223372036854775807"
OTHERSOCKBUF="9223372036854775807:9223372036854775807"
DGRAMRCVBUF="9223372036854775807:9223372036854775807"

# Auxiliary parameters
NUMFILE="9223372036854775807:9223372036854775807"
NUMFLOCK="9223372036854775807:9223372036854775807"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="9223372036854775807:9223372036854775807"
LOCKEDPAGES="917504:917504"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="9223372036854775807:9223372036854775807"
PHYSPAGES="0:9223372036854775807"

# Disk quota parameters
DISKSPACE="104857600:115343360"
DISKINODES="20000000:22000000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-5.0-standard_5.0-2_i386"
ORIGIN_SAMPLE="pve.auto"
HOSTNAME="lsmtp.trecisrl.it"
NAMESERVER="127.0.0.1"
SEARCHDOMAIN="trecisrl.it"
NETIF="ifname=eth0,bridge=vmbr1,mac=D6:A5:27:6A:85:D2,host_ifname=veth103.0,host_mac=00:18:51:7A:2E:7A"
DESCRIPTION="Zimbra 6.0.5_GA_2213_Debian5_FOSS 32 IP .12 e gw .1"

Any clue? I repeat, worked fine until the proxmox upgrade from 1.8 to 1.9, no Zimbra update or change in settings.
If I can find the solution I'll have to try to "move" the zimbra installation to a kvm machine, sigh.
Thanks a lot
Marco
 
the 26.32-4 kernel does not respect the cpu settings, means your container always uses all cpu cores available. the 2.6.32-6 respect the cpu settings and I assume you assigned only one? Try to increase the CPU to the full number of available cores (depends on your physical CPU) and try again.
 
You must log in or register to reply here.
Top Bottom