You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering a fatal crash in a Minecraft server running within the itzg/docker-minecraft-server Docker image. The crash occurs with a SIGBUS (0x7) error in the Java Runtime Environment (OpenJDK 21.0.7), specifically in the VM Periodic Task Thread during the PerfLongVariant::sample() function. Notably, there are no errors or warnings in the Minecraft server logs immediately preceding the crash, but creating a hs_err_pid1.log file in the data directory. The server terminated unexpectedly after approximately 5-6 hours of uptime.
...
[23:41:11] [Server thread/INFO]: Disconnecting todaracmustpay (/156.146.63.209:30737): You are not white-listed on this server!
[23:41:11] [Server thread/INFO]: todaracmustpay (/156.146.63.209:30737) lost connection: You are not white-listed on this server!
[23:41:11] [Server thread/WARN]: handleDisconnection() called twice
[00:50:13] [Server thread/WARN]: handleDisconnection() called twice
No service logs after this until the crash at Fri May 16 01:17:38 2025 with the crash generating an hs_err_pid1.log file -> attachment hs_err_pid1.log
Uh oh!
There was an error while loading. Please reload this page.
Describe the problem
I'm encountering a fatal crash in a Minecraft server running within the
itzg/docker-minecraft-server
Docker image. The crash occurs with aSIGBUS (0x7)
error in the Java Runtime Environment (OpenJDK 21.0.7), specifically in theVM Periodic Task Thread
during thePerfLongVariant::sample()
function. Notably, there are no errors or warnings in the Minecraft server logs immediately preceding the crash, but creating ahs_err_pid1.log
file in the data directory. The server terminated unexpectedly after approximately 5-6 hours of uptime.This happens very few days.
Container definition
Container logs
No service logs after this until the crash at Fri May 16 01:17:38 2025 with the crash generating an
hs_err_pid1.log
file -> attachment hs_err_pid1.logManual restart the next day:
The text was updated successfully, but these errors were encountered: