java runtime

B

broascaa

New Member
Oct 9, 2022
5
0
1
Hello guys!
I keep got this error from one of my java servers and idk if it's because of proxmox (i use LXC container) or it's a hardware problem (the memory).
I allocated 64GB and 4GB swap to the LXC and i run docker containers inside of it using ubuntu 22.

Code: 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f04d9330dff, pid=380, tid=466
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.4.1+1 (17.0.4.1+1) (build 17.0.4.1+1)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.4.1+1 (17.0.4.1+1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x6d5dff]  void OopOopIterateDispatch<G1CMOopClosure>::Table::oop_oop_iterate<InstanceKlass, narrowOop>(G1CMOopClosure*, oopDesc*, Klass*)+0xdf
#
# Core dump will be written. Default location: /data/core
#
# An error report file with more information is saved as:
# /data/hs_err_pid380.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
#
 
Also when i take that error everything kind of broke..
node's + VMs and LXCs status is changed to unknown and i can't reboot the server from interface, i have to manually reboot from power button
 
broascaa said:
How can i do that?
Click to expand...
You download a memtest86 image, burn it to a USB stick (for example with rufus) and then boot that stick and let the test run for several hours hammering your RAM checking for false results.
I think either PVE itself or the PVE ISO also should got a copy of memtest86 integrated as alternate boot options.
 
Last edited:
Until i do this test, is there anyway to move a part of content from one LXC Container to another?
 
You must log in or register to reply here.
Top Bottom