[Bug]: Crashes Server on startup
BadgerSnacks opened this issue · 4 comments
Describe the bug you're experiencing
I added Connectivity 1.21-6.1 and Cupboard 1.21-2.8 to my custom server running a custom modpack I am working on called Dig Burrow Build 2 and it will fail to start up. It has broken my server so badly that even after removing the mod I am now getting a full java runtime crash. Since its not listed on the bottom of the page I am using NeoForge 21.1.84
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x0000782c77c6e06a, pid=1, tid=68
JRE version: OpenJDK Runtime Environment Temurin-21.0.3+9 (21.0.3+9) (build 21.0.3+9-LTS)
Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (21.0.3+9-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
Problematic frame:
[error occurred during error reporting (printing problematic frame), id 0xb, SIGSEGV (0xb) at pc=0x0000782c90e52664]
Core dump will be written. Default location: /home/container/core.1
An error report file with more information is saved as:
/home/container/hs_err_pid1.log
[thread 60 also had an error]
[18.644s][warning][os] Loading hsdis library failed
If you would like to submit a bug report, please visit:
https://github.com/adoptium/adoptium-support/issues
[error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x0000782c9176c898]
latest.log
Reproducability
Use the mod list located in the log file from the pack DIg Burrow Build 2 to host a dedicated server. Install connectivity and cupboard and server will crash.
Mod up to date
- Before submitting this issue I updated to the newest version and reproduced it
Minecraft version
1.21.1
Modloader version
Forge
Logs
https://github.com/user-attachments/files/18104213/latest.log
the mod cannot permanently change any settings nor affect the server in that way, thats simply another error that occured on that server, maybe as side effect of the server instance crashing on load. Has nothing to do with the mod itself though.
the mod cannot permanently change any settings nor affect the server in that way, thats simply another error that occured on that server, maybe as side effect of the server instance crashing on load. Has nothing to do with the mod itself though.
Good to know, I’m very new to all of this and learning as I go. I will run some more attempts to see if I can get things working. Thank you for the reply.