Results 1 to 37 of 37

Thread: Best strategy to handle strange JVM errors inside VPS

  1. #1
    Join Date
    Aug 2011
    Posts
    21

    Default Best strategy to handle strange JVM errors inside VPS

    I am playing arround with PROXMOX /openvz to migrate a couple of VMware instances. Most applications are Java based, which can easy be migrate to OpenVZ. For each customer/project an own VPS.

    Now I try to to migrate Alfresco an Open Source Document Mangement System. The actual problem - the JVM which serves the Tomcat Container dies after an hour. Tested with 3 different VMs - SUN JDK two different versions and OpenJDK - same behaviour. Search in the Alfresco forum there is no hint according this problem. Seems to be an JVM/OpenVZ problem. An other VPS with Open-Xchanage (Java based Groupware) works fine.

    Enviroment:
    pve-manager: 1.8-23 (pve-manager/1.8/6533)
    running kernel: 2.6.32-6-pve
    proxmox-ve-2.6.32: 1.8-42
    pve-kernel-2.6.32-6-pve: 2.6.32-42
    qemu-server: 1.1-31
    pve-firmware: 1.0-13
    libpve-storage-perl: 1.0-19
    vncterm: 0.9-2
    vzctl: 3.0.28-1pve5
    vzdump: 1.2-15
    vzprocps: 2.0.11-2
    vzquota: 3.0.11-1
    pve-qemu-kvm: 0.15.0-1
    ksm-control-daemon: 1.0-6

    VPS settings
    105.jpg

    Question: It is allowed to use VZ templates from OpenVZ - or is there a restriction to use only VZ templates provides by PROXMOX ( tested, etc.).

    Any idea to handle such problems?

    With best reagards
    Peter

    JVM dump
    PHP Code:
    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    #  Internal Error (synchronizer.cpp:1401), pid=672, tid=6302576
    #  guarantee(mid->header()->is_neutral()) failed: invariant
    #
    # JRE version: 6.0_22-b22
    # Java VM: OpenJDK Client VM (20.0-b11 mixed mode, sharing linux-x86 )
    # Derivative: IcedTea6 1.10.2
    # Distribution: Ubuntu 11.04, package 6b22-1.10.2-0ubuntu1~11.04.1
    # If you would like to submit a bug report, please include
    # instructions how to reproduce the bug and visit:
    #   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
    #

    ---------------  T H R E A D  ---------------

    Current thread (0x08873800):  VMThread [stack0x00582000,0x00603000] [id=675
    Attached Images Attached Images

  2. #2
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  3. #3
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Quote Originally Posted by pezi View Post

    Question: It is allowed to use VZ templates from OpenVZ - or is there a restriction to use only VZ templates provides by PROXMOX ( tested, etc.).
    you can use whatever template you want but the Debian 6 template are very preferred here and can also be created with dab)
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  4. #4
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Thanks for the quick response - Yes, there are failcounts
    privvmpages 26283 562327 655360 667860 14
    There are some hints to this "problem" -I will try solve this problem with this hints. I will post my results

  5. #5
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    The java vm does have problems inside a openVZ container with the calculation of available memory. this issues is known and discussed several time when you run Zimbra on OpenVZ - just search for this.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  6. #6
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    My newest results - the problem with the fail counts for the property privvmpages was fixed by increasing the memory! But this step doesn't fix the main problem: The page fault of the VM.
    I played arround with the GC parameter of the VM, I created a debian template (instead of Ubuntu) with Alfresco - no chance - the JVM dies after a while.

    As a last test I moved the this template to the test node of the cluster - surprise, there is no problem with the JVM, Alfresco runs since two days!

    Master node:
    model name : Intel(R) Core(TM) i3-2100T CPU @ 2.50GHz
    cpu MHz : 2499.544
    16 GB Ram

    Second node:
    vendor_id : AuthenticAMD
    model name : AMD Athlon(tm)64 X2 Dual Core Processor 4200+
    4 GB Ram

    Both nodes are has beend updated to Proxmox 1.9. Very strange problem! There is an other VZ template on the master node with an open source java stack - Open Xchange since three week. No problems.

  7. #7
    Join Date
    Feb 2010
    Posts
    16

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I am having a similar problem. I just updated two Proxmox installs from 1.8 to 1.9. Now various Java VEs are having strange problems similar to those you report above. One install is our custom Java webapp and it just seems to freeze after awhile. No errors, no high cpu, no nothing. Just quits working. We had a Hudson build server (a Java app) that just won't run after the 1.9 upgrade. It starts fine with no errors but then same thing, just seems to freeze. Every once in awhile it will segfault as well.

    Do you have any additional thoughts on what is going on here?

  8. #8
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I gave up to get Alfreso running on the master node - using Proxmox 1.8 at the start ot this thread, now Proxmox 1.9 latest version including PVE test.

    I tried various JVM paramters - but on the master node Alfreso dies after period. Most JVM Dump messages were internal memory management related.

    On the other hand - on the old test PC (test node) the JVM (Alfresco) runs. I think this is a problem related to a timing problem: Just in time compiler (JVM - different results for different CPUs) in combination with new hardware (Intel(R) Core(TM) i3-2100T CPU) and OpenVZ

  9. #9
    Join Date
    Feb 2010
    Posts
    16

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Ughh... this is incredibly frustrating. Java apps seem to be running fine but then just stop responding.

    I guess I'll try rolling back to 1.8

  10. #10
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    11,785

    Default Re: Best strategy to handle strange JVM errors inside VPS

    The new kernel forces cpu limits as set in the vm configuration. So maybe it helps if you asssign more cpu power.

  11. #11
    Join Date
    Jul 2009
    Location
    Valčncia
    Posts
    52

    Default Re: Best strategy to handle strange JVM errors inside VPS

    We've got exactly the same problem: after upgrading from 1.8 to 1.9 all ours virtual machines with applications using JVM (jboss, tomcat, nuxeo) stop to work.

    We did those upgrade (proxmox 1.8 to 1.9):

    Kernel 2.6.18 -> kernel 2.6.32-6
    Kernel 2.6.24 -> kernel 2.6.32-6
    Kernel 2.6.32-4 -> kernel 2.6.32-6

    The virtual machines (with JVM) working fine before the upgrade, and after upgrading to 2.6.32-6, they stop to work (the jvm crashing or stopping to respond).
    After rebooting the hosts on their initial kernels (2.6.18, 2.6.24, 2.6.32-4), everything works fine again.
    As well, we've migrated a virtual machine with this trouble in 2.6.32-6 to a cluster still under proxmox 1.8 with kernel 2.6.32-4 and it works fine.

  12. #12
    Join Date
    Feb 2010
    Posts
    16

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Good to know we have a real bug here. Dietmar, I assume you mean to bump up the 'CPUs' option on the VE web config. I will try this but then I will need to downgrade to 1.8 (or boot into the old kernel) as I need these machines operational asap

  13. #13
    Join Date
    Sep 2011
    Posts
    7

    Default Re: Best strategy to handle strange JVM errors inside VPS

    +1 for me.

    I use Zimbra in a Lucid OpenVZ container (configuration based on ve-vswap-1024m.conf-sample in /etc/vz/conf so most parameters but PHYSPAGES, SWAPPAGES, KMEMSIZE and LOCKEDPAGES are on unlimited), all failcnt are on 0 but after "some time" (5 minutes, 6 hours, 15 hours), Zimbra stops responding with no error message at all (checked all the logs in /var/log, on the host and in the container - also in /opt/zimbra/log here). SSH connexion are still possible when this occurs, JVM/Zimbra simply stop answering. Only way to get it back is to reboot the container.

    Yesterday evening it goes worse: the whole host was unanswering (ping ok, but no https, no ssh, and no access to any container), after a reboot of the host I cannot find anything in the logs neither ("grep -Ri error /var/log" displays nothing interesting, cron jobs have run past the point where all services were unavailable but were unable to communicate with outside world)

    I'll try downgrading the kernel to 2.6.32-4 and see if it helps.

    Host: Core i5 i2400, 16GB RAM

    lspci:
    lspci
    00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
    00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
    00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
    00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
    00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
    00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
    00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05)
    00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
    01:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 10)
    03:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)

    pveversion -v:
    running kernel: 2.6.32-6-pve
    proxmox-ve-2.6.32: 1.9-43
    pve-kernel-2.6.32-4-pve: 2.6.32-33
    pve-kernel-2.6.32-6-pve: 2.6.32-43
    qemu-server: 1.1-32
    pve-firmware: 1.0-13
    libpve-storage-perl: 1.0-19
    vncterm: 0.9-2
    vzctl: 3.0.28-1pve5
    vzdump: 1.2-15
    vzprocps: 2.0.11-2
    vzquota: 3.0.11-1dso1
    pve-qemu-kvm: 0.15.0-1
    ksm-control-daemon: 1.0-6

  14. #14
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I made a kernel downgrade to
    pve-kernel-2.6.32-4-pve: 2.6.32-33

    Alfresco runs now since 6 hours without crash. . I will monitor this app tov verify that the old kernel fix the Jav/OpenVZ problem!

  15. #15
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Hi!

    Switching to the prior kernel, "fixes" the JVM crash problem!

    During my tests with Alfresco we discovered 3 types of JVM/application missbehaviour.
    - JVM crash - problem Nr. 1
    - JVM runs with 100% CPU, but the appilcation can handle HTTP request
    - JVM seems to be still alive - but the application doesn't response

    You wrote
    http://forum.proxmox.com/threads/702...0248#post40248
    not really, the 2.6.32-4 is based on Squeeze, the 2.6.32-6 is based on RHEL61.
    So I belive to find the exact problem will be difficult.

    Can we do anything for you to fix this problem. Testing, etc.?

    with best
    regards
    Peter

  16. #16
    Join Date
    Apr 2005
    Location
    Austria
    Posts
    11,785

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Quote Originally Posted by pezi View Post
    Can we do anything for you to fix this problem. Testing, etc.?
    It would be great if you find an easy why to reproduce that bug. You can also report the bug on the openvz forum - maybe someone there has an idea.

  17. #17
    Join Date
    Apr 2011
    Posts
    34

    Default

    Can I confirm that this is an issue solely with the new kernel ? Is the rest of the 1.9 update safe for use with jvm ?

  18. #18
    Join Date
    Feb 2010
    Posts
    16

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I downgraded two machines to 1.8 (had some other errors trying to boot into original kernel) and everything is working again.

    I think this will be a difficult bug to track down. To reproduce it you could probably do what I did when trying to rebuild my build server. I just created a new Debian VE, installed Java, downloaded Jenkins (or Hudson) and ran it with 'java -jar jenkins.war'

  19. #19
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I wil try to find a test case for a easy reproducible JVM fail.

    Quote Originally Posted by dietmar View Post
    It would be great if you find an easy why to reproduce that bug. You can also report the bug on the openvz forum - maybe someone there has an idea.
    For posting on the openvz forum. Which relationship exists between the pve kernel and the offical openvz-kernel
    http://download.openvz.org/kernel/br....6.32/current/
    pve kernel = openvz-kernel +some modifications e.g. newer driver?

  20. #20
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    the latest 2.6.32-6 kernel is based on the stable OpenVZ branch (RHEL6) but with some small modifications, and a bunch of newer drivers for NIC´s and raid controllers.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  21. #21
    Join Date
    Sep 2011
    Posts
    7

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Confirmed for me too.
    Zimbra runs flawlessly and rock solid for 60 hours with only the kernel downgraded to 2.6.32-4; all the rest is still Proxmox 1.9.

    pve-manager: 1.9-24 (pve-manager/1.9/6542)
    running kernel: 2.6.32-4-pve
    proxmox-ve-2.6.32: 1.9-43
    pve-kernel-2.6.32-4-pve: 2.6.32-33
    pve-kernel-2.6.32-6-pve: 2.6.32-43
    qemu-server: 1.1-32
    pve-firmware: 1.0-13
    libpve-storage-perl: 1.0-19
    vncterm: 0.9-2
    vzctl: 3.0.28-1pve5
    vzdump: 1.2-15
    vzprocps: 2.0.11-2
    vzquota: 3.0.11-1dso1
    pve-qemu-kvm: 0.15.0-1
    ksm-control-daemon: 1.0-6

  22. #22
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I created topic according this problems on the OpenVz forum http://forum.openvz.org/index.php?t=...0025#msg_43571
    ....with no response...

    But it seems there is perhaps a fix for this problem. Promox 1.9 latest version (update).
    I assigned each OpenVZ container with a Java WebApp 2 CPUs. Now apps like Alfresco and Liferay are running without crash or hanging. With only 1 CPU Liferay dies after an hour. (1)
    I will monitor the Container for the next days, if this a perhaps a real fix, or the dead of the JVM is only delayed.

    Our aim to migrate from VMware to PROXMAX will be delayed this problem is really solved.

    (1) Test Scenario -
    i) Create a Debain Container (Proxmox Template) - 2GB RAM and only 1 CPU
    ii) apt-get install openjdk-6-jre
    iii) Download Liferay Portal Community Edition with TOMCAT from http://www.liferay.com/de/downloads/liferay-portal/available-releases
    iv) unzip liferay-portal-tomcat-6.0.6-20110225.zip to /opt
    v) start app: /opt/liferay-portal-6.0.6/tomcat-6.0.29/bin/startup.sh
    vi) access portal http://container-ip:8080
    ... wait for an hour - system will crash
    search for the JVM dump like: /opt/liferay-portal-6.0.6/tomcat-6.0.29/bin/hs_err_pid7650.log

  23. #23
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    just tried, got immediately a failcount on privvmpages which is out-of-memory.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  24. #24
    Join Date
    Jul 2009
    Location
    Valčncia
    Posts
    52

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Hello,

    I've tried the Pezi's workaround, and I confirm, its works for us as well. To answer to Tom, in ours cases, we've always got 0 failcount.

    1. we start the container with only 1 CPU, the JVM dies.
    PHP Code:
    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    #  Internal Error (objectMonitor.cpp:1559), pid=1996, tid=140506417796864
    #  guarantee(_recursions == 0) failed: invariant
    #
    # JRE version: 6.0_26-b03
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
    # An error report file with more information is saved as:
    # /root/hs_err_pid1996.log
    #
    # If you would like to submit a bug report, please visit:
    #   http://java.sun.com/webapps/bugreport/crash.jsp
    #
    Aborted 
    and
    PHP Code:
           uid  resource                     held              maxheld              barrier                limit              failcnt
                kmemsize                 18055460             23142400  9223372036854775807  9223372036854775807                    0
                privvmpages                 60263               563969              1048576              1061076                    0
                physpages                   88778               407884                    0  9223372036854775807                    0
                vmguarpages                     0                    0              1048576  9223372036854775807                    0
                oomguarpages                14097               329674              1048576  9223372036854775807                    0 
    Now, I stop the container, change the number of cpu to 2 (or more), start it and the JVM works flawless.

  25. #25
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Quote Originally Posted by iti-asi View Post
    Hello,

    I've tried the Pezi's workaround, and I confirm, its works for us as well. ..
    did I miss something? what is the workaround?
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  26. #26
    Join Date
    Jul 2009
    Location
    Valčncia
    Posts
    52

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Quote Originally Posted by tom View Post
    did I miss something? what is the workaround?
    Just give 2 or more CPUs to the containers. Not really an ideal solution, but until the problem is solved, it works.

  27. #27
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Ok - the memory is to small. During my short tests there was no failcount on privvmpages.
    Please change the memory to a higher value e.g. 3GB mem/3B swap - tested now.
    No failcount on privvmpages. But the JVM crash or hangs after one hour.

    On the other hand - the failcount on privvmpages problem should only lead to an out of memory related error - no crash. Is this correct?

  28. #28
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    if you got out of memory the kernel kill processes (OOM killer). the upcoming 2.0 beta (available very soon) will support vswap, would be interesting how this works here and if it solved some issues with container memory handling with java.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  29. #29
    Join Date
    Sep 2011
    Posts
    7

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Tom, the problem described here is not related to failcount, it's something other.
    Please see my first post above.

    Using a vswap enabled configuration (based on samples in /etc/vz/conf), I achieve to get vswap and no failcount at all (of course, as most is set as unlimited), but with kernel 2.6.32-6 JVM simply stop responding (after various periods of time), with kernel 2.6.32-4 everything works rock solid. In my case, no message is available at all, nowhere, nor on the host, nor in the container, it simply stops answering.

    Some have JVM/apps stop responding (my case - all processes are still there but nothing works), others have JVM/apps crash.

    If you take pezi's use case and either set high enough ram/swap or my config based on vswap, you'll see the problem.
    All failcount stays at 0, but JVM dies or stop responding.

    2 solutions exist for this right now:
    - rollback kernel to 2.6.32-4 (tested this, Zimbra still runs flawlessly after 6 days)
    - set 2 cpu in the container (not tested my self)

  30. #30
    Join Date
    Aug 2011
    Posts
    21

    Default Re: Best strategy to handle strange JVM errors inside VPS

    It seems that other non Java apps have the same or similar problem.
    http://forum.proxmox.com/threads/713...llocate-262144

  31. #31
    Join Date
    Sep 2011
    Posts
    7

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Do we have any progress with this bug? A use case has been defined; do you need another one (I can describe Zimbra installation that would raise the problem, but it's a little bit more complicated than pezi's use case)?

  32. #32
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    anyone tested on 2.0 beta? (uses vswap)

    as there exists a workaround for 1.9 I think we should concentrate on vswap on 2.0.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  33. #33
    Join Date
    Sep 2011
    Posts
    7

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I haven't tested the 2.0 (no spare machine) nor the second workaround (2 CPU per VM with Java), only the downgrade of kernel (not a real workaround though). I already use a vswap enabled config with 1.8 and 1.9 but the problem with JVM also exists with this configuration and kernel -6. Will this be different with 2.0?

  34. #34
    Join Date
    Aug 2006
    Posts
    9,743

    Default Re: Best strategy to handle strange JVM errors inside VPS

    yes, only 2.0 uses vswap.

    for 1.9 with 2.6.32-6, just add full cpu power (number depends on your hardware) as it is with 2.6.32-4 (and 2.6.32-5). again, the old kernel always assigned all available cpu´s to the container, only 2.6.18 respected the cpu setting.
    Best regards,
    Tom

    Do you have already a Commercial Support Subscription? - If not, Buy now

  35. #35
    Join Date
    Jul 2009
    Location
    Valčncia
    Posts
    52

    Default Re: Best strategy to handle strange JVM errors inside VPS

    Tom,

    As you've asked, I've done some quick tests.

    I've done an vzdump (proxmox 1.8) and vzrestore on proxmox 2.0 of some VMs (with and without JVM).
    The host have 8 cores (2x Intel Xeon) and 16Gb of memory. There is only one VM running on the host at the same time.

    Proxmox 2.0 has been installed on a clean debian squeeze instalation (not from proxmox cdrom).
    PHP Code:
    root@blade400:~# uname -a
    Linux blade400 2.6.32-6-pve #1 SMP Mon Sep 26 10:35:47 CEST 2011 x86_64 GNU/Linux
    root@blade400:~# pveversion -v
    pve-manager2.0-(pve-manager/2.0/de5d8ab1)
    running kernel2.6.32-6-pve
    proxmox
    -ve-2.6.322.0-46
    pve
    -kernel-2.6.32-6-pve2.6.32-46
    lvm2
    2.02.86-1pve1
    clvm
    2.02.86-1pve1
    corosync
    -pve1.4.1-1
    openais
    -pve1.1.4-1
    libqb
    0.5.1-1
    redhat
    -cluster-pve3.1.7-1
    pve
    -cluster1.0-9
    qemu
    -server2.0-2
    pve
    -firmware1.0-13
    libpve
    -common-perl1.0-6
    libpve
    -access-control1.0-1
    libpve
    -storage-perl2.0-4
    vncterm
    1.0-2
    vzctl
    3.0.29-3pve2
    vzdump
    1.2.6-1
    vzprocps
    2.0.11-2
    vzquota
    3.0.12-3
    pve
    -qemu-kvm0.15.0-1
    ksm
    -control-daemon1.1-
    I'm able to run without trouble the VMs without JVM (zabbix, mysql server, or drupal for example), but not the VMs with JVM.
    As long I stay with 1 CPU, the JVM crash o freeze, even with 8Gb ram and 8Gb of swap or 16Gb of ram. If I'm adding a 2d CPU it works.

  36. #36
    Join Date
    Nov 2011
    Posts
    24

    Default Re: Best strategy to handle strange JVM errors inside VPS

    I am seeing the same thing. With 2.0 all kinds of weird things happen with JVM/Tomcat stuff. When I add a second CPU to the instance it works fine.


    pve-manager: 2.0-38 (pve-manager/2.0/af81df02)
    running kernel: 2.6.32-7-pve
    proxmox-ve-2.6.32: 2.0-60
    pve-kernel-2.6.32-6-pve: 2.6.32-55
    pve-kernel-2.6.32-7-pve: 2.6.32-60
    lvm2: 2.02.88-2pve1
    clvm: 2.02.88-2pve1
    corosync-pve: 1.4.1-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-1
    pve-cluster: 1.0-23
    qemu-server: 2.0-25
    pve-firmware: 1.0-15
    libpve-common-perl: 1.0-17
    libpve-access-control: 1.0-17
    libpve-storage-perl: 2.0-12
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve1
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.0-5
    ksm-control-daemon: 1.1-1
    root@proxmox2:~# uname -a
    Linux proxmox2 2.6.32-7-pve #1 SMP Thu Feb 16 09:00:32 CET 2012 x86_64 GNU/Linux
    root@proxmox2:~#

  37. #37
    Join Date
    Feb 2009
    Posts
    249

    Smile Re: Best strategy to handle strange JVM errors inside VPS

    I can confirm this issue.. I wish I had found this post earlier as I have been spending quite a bit of time with my application Vendor to solve this problem.

    I have a debian 6 container with Sun Java 6 and Crashplan ProE server. After upgrading Proxmox from version 1.8 to 1.9 I encountered some update issues with Java which after fixing them Crashplan ProE did not work. No errors were found in the application logs but I noticed that the application was not listening on the required ports.

    After increasing the number of CPU's from 1 to 2 the app was able to run with no problems!! Thank you Pezi for the workaround!!

    Hopefully this problem will be fixed in the next kernel update! Thanks everyone for your posts!

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •