Cannot update to 3.3 or 4.0
Hi there,
I'm using YouTrack inside the Yanuki Service Wrapper, which has worked like a charm until now.
System: Suse Linux Enterprise Server 11, fully patched.
Today I tried an upgrade from 3.2.3 to 4.0, which leads to JVM being terminated, after the standalone wrapper is restarted.
wrapper.log
I experienced the same error when trying to upgrade from 3.2.3 to 3.3.
Back then, I skipped the update and reverted to 3.2.3, but 4.0's brand new features are worth upgrading, I think.
Could someone give me a hint where to search for the error or what to do to make 4.0 running as flawlessly as 3.2.x?
Best regards,
ThaGoob
I'm using YouTrack inside the Yanuki Service Wrapper, which has worked like a charm until now.
System: Suse Linux Enterprise Server 11, fully patched.
Today I tried an upgrade from 3.2.3 to 4.0, which leads to JVM being terminated, after the standalone wrapper is restarted.
wrapper.log
INFO | jvm 1 | 2012/07/02 15:32:59 | # A fatal error has been detected by the Java Runtime Environment:
INFO | jvm 1 | 2012/07/02 15:32:59 | #
INFO | jvm 1 | 2012/07/02 15:32:59 | # SIGSEGV (0xb) at pc=0x00007f8b02db478a, pid=8438, tid=140234716694272
INFO | jvm 1 | 2012/07/02 15:32:59 | #
INFO | jvm 1 | 2012/07/02 15:32:59 | # JRE version: 7.0-b147
INFO | jvm 1 | 2012/07/02 15:32:59 | # Java VM: Java HotSpot(TM) 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops)
INFO | jvm 1 | 2012/07/02 15:32:59 | # Problematic frame:
INFO | jvm 1 | 2012/07/02 15:32:59 | # J org.apache.lucene.analysis.ASCIIFoldingFilter.incrementToken()Z
INFO | jvm 1 | 2012/07/02 15:32:59 | #
INFO | jvm 1 | 2012/07/02 15:32:59 | # Core dump written. Default location: /home/youtrack/standalone/bin/core or core.8438 (max size 1 kB). To ensure a full core dump, try "ulimit -c unlimited" before starting Java again
INFO | jvm 1 | 2012/07/02 15:32:59 | #
INFO | jvm 1 | 2012/07/02 15:32:59 | # An error report file with more information is saved as:
INFO | jvm 1 | 2012/07/02 15:32:59 | # /home/youtrack/standalone/bin/hs_err_pid8438.log
INFO | jvm 1 | 2012/07/02 15:32:59 | #
INFO | jvm 1 | 2012/07/02 15:32:59 | # If you would like to submit a bug report, please visit:
INFO | jvm 1 | 2012/07/02 15:32:59 | # http://bugreport.sun.com/bugreport/crash.jsp
INFO | jvm 1 | 2012/07/02 15:32:59 | #
STATUS | wrapper | 2012/07/02 15:32:59 | JVM received a signal UNKNOWN (6).
STATUS | wrapper | 2012/07/02 15:32:59 | JVM process is gone.
ERROR | wrapper | 2012/07/02 15:32:59 | JVM exited unexpectedly.
STATUS | wrapper | 2012/07/02 15:33:26 | TERM trapped. Shutting down.
STATUS | wrapper | 2012/07/02 15:33:26 | <– Wrapper Stopped
STATUS | wrapper | 2012/07/02 15:36:13 | –> Wrapper Started as Daemon
STATUS | wrapper | 2012/07/02 15:36:13 | Java Service Wrapper Community Edition 64-bit 3.5.6
STATUS | wrapper | 2012/07/02 15:36:13 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2012/07/02 15:36:13 | http://wrapper.tanukisoftware.com
I experienced the same error when trying to upgrade from 3.2.3 to 3.3.
Back then, I skipped the update and reverted to 3.2.3, but 4.0's brand new features are worth upgrading, I think.
Could someone give me a hint where to search for the error or what to do to make 4.0 running as flawlessly as 3.2.x?
Best regards,
ThaGoob
Please sign in to leave a comment.