Debian Server - Fatal error (SIGSEGV)

[Descorath]

Hi,

Started testing out FTB during xmas and installed it on a fresh server.
After the latest FTB update we have had some seemingly random crashes.

The server is running Debian, with Intel E8500 and 4gb of memory so it can handle the load without problems.

After the second occurance of the problem I updated java to the newest version (was running Debian default (java 6))

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fb05e3301a5, pid=4687, tid=140395390998272
#
# JRE version: 7.0_10-b18
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x50f1a5] instanceKlass:op_follow_contents(ParCompactionManager*, oopDesc*)+0x2c5
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before startin$
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
http://pastebin.com/Hcm6F0XC
Pastebin of the last two crashes. One from before I updated Java, the other after.
Hope someone can shed light on what this might be the cause of the crashes.

 

[Descorath]

Hmm. Installed it from a repo, but I will get on rolling back the java version.
Though it still doesnt fix what made the server crash in the first place.

 

[Descorath]

Removed the newest version, but still got the crashes:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fcfcd9c0ed0, pid=9377, tid=140528045004544
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
# Derivative: IcedTea6 1.8.13
# Distribution: Debian GNU/Linux 6.0.4 (squeeze), package 6b18-1.8.13-0+squeeze2
# Problematic frame:
# V [libjvm.so+0x4cced0]
#
# An error report file with more information is saved as:
# /data/Mindcrack/hs_err_pid9377.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
Any idea what i might be ?

 

[Dekar]

Running debian squeeze myself with 7.10 and it is working well.

Which pack are you trying to run?
Try installing a vanilla server and see if it will run that first? If that crashes then something with java is not working correctly. If it works, then it is something to do with a mod/forge, etc.

 

[Descorath]

Running Mindcrack.. And its a totaly fresh install of debian, but Im going to try vanilla and let it run a few days to see if the error pops up (it crashes now like every 12th hour.)

 

[Descorath]

Ran standard Minecraft without problems for 24 hours, though it wasnt much activity on it.
Downloaded and installed a fresh install of Minecrack server and had it running for aprox 1 hour before I got the same error message:
This was with a new world file just to make sure it wasnt anything with that.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007facd424107b, pid=13722, tid=140378935514880
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
# Derivative: IcedTea6 1.8.13
# Distribution: Debian GNU/Linux 6.0.4 (squeeze), package 6b18-1.8.13-0+squeeze2
# Problematic frame:
# V [libjvm.so+0x39a07b]
#
# An error report file with more information is saved as:
# /data/Minecraft_server/hs_err_pid13722.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
#
Any ideas ?

 

[glasspelican]

thats a seg fault
one of the mods is trying to access memory that its not allowed to

could you post what command you are starting the server with

 

[Descorath]

java -Xms512M -Xmx1G -jar mindcrack.jar

the standard one.

 

[glasspelican]

perhaps its not handeling the upper memory bound correctly

-Xincgc -Xmx2G

 

[Descorath]

seemed to last longer before the error occurred, but that might just have been because of reduced activity.
Will the full error log help ?

 

[glasspelican]

If in doubt post log