java dies unexpectedly on cents

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Mathias Verbert
    New Member
    • Dec 2011
    • 1

    java dies unexpectedly on cents

    when running java -Xmx200m server everything works fine and the virtual server runs. but after a few minutes it just decides to quit, no error nothing. i tried with nohup, screen, combination of both, none seemed to work. i found out about strace but this makes me no smarter at all. its a huge file but i'll paste the last part.

    Code:
    18:35:27.963821 mmap2(NULL, 163952, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xffffffffb7493000
    18:35:27.963869 mmap2(0xb74ba000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26) = 0xffffffffb74ba000
    18:35:28.001070 close(3)                = 0
    18:35:28.001196 mprotect(0xb74ba000, 4096, PROT_READ) = 0
    18:35:28.001234 mprotect(0xb74bc000, 4988928, PROT_READ|PROT_WRITE) = 0
    18:35:28.433123 mprotect(0xb74bc000, 4988928, PROT_READ|PROT_EXEC) = 0
    18:35:29.492764 munmap(0xb7f3f000, 54917) = 0
    18:35:29.703327 mmap2(NULL, 331776, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xffffffffb7442000
    18:35:29.713994 mprotect(0xb7442000, 4096, PROT_NONE) = 0
    18:35:29.714047 clone(child_stack=0xb74924b4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xb7492bd8, tls=0xb7492bd8, child_tidptr=0xbfa834ac) = 32236
    18:35:29.714112 futex(0xb7492bd8, FUTEX_WAIT, 32236, NULL) = -1 EINTR (Interrupted system call)
    18:40:01.812233 --- SIGTERM (Terminated) @ 0 (0) ---
    18:40:01.812294 futex(0xb79a49a0, FUTEX_WAKE_PRIVATE, 1) = 1
    18:40:01.812344 rt_sigreturn(0xb7492bd8) = -1 EINTR (Interrupted system call)
    18:40:01.812395 futex(0xb7492bd8, FUTEX_WAIT, 32236, NULL <unfinished ... exit status 143>
  • matthiasgasser
    New Member
    • Apr 2012
    • 1

    #2
    I asume you are inside an OpenVZ like container (VPS)... In my case it looks like some VPS providers are periodically SIGTERM-inating processes called "java"
    You can easily proof this by renaming a simple program to "java" and wait for the termination, or just rename the java executable itself and it will persist...

    Thats a very bad thing of those VPS providers as it is not communicated at all (advertised ;) )

    HTH

    Comment

    Working...