MSH crash on start
sogata-aw opened this issue · 1 comments
Current Behavior (🐛 Bug)
I got this error after launching msh but before that it works.
I tried to delete every files of msh and reinstall it but it's still the same.
Expected Behavior
I expected it to start and fix the issue.
Steps to Reproduce
Just starting the binary file.
MSH Logs
2023/12/04 10:56:30.318 [info ≡ ] checking OS support...
2023/12/04 10:56:30.318 [info ≡ ] loading config...
2023/12/04 10:56:30.318 [info ≡ ] reading config file: "/srv/minecraft/liberty_mods/msh-config.json"
2023/12/04 10:56:30.319 [info ≡ ] msh instance file exists
2023/12/04 10:56:30.319 [info ≡ ] msh instance loaded is healthy
2023/12/04 10:56:30.319 [info ≡≡≡≡] setting log level to: 1
2023/12/04 10:56:30.319 [info ≡≡≡ ] eula.txt exist and is set to true
2023/12/04 10:56:30.550 [info ≡≡≡≡] issuing msh termination
2023/12/04 10:56:30.550 [info ≡≡≡ ] listening for new clients connections on 0.0.0.0:25555 ...
2023/12/04 10:56:30.550 [info ≡≡≡ ] received signal: interrupt
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x296f10] goroutine 1 [running]:
main.main() C:/Users/Giacomo/Desktop/Giacomo/informatica/programmazione/» Go/minecraft-server-hibernation/msh/minecraft-server-hibernation.go:73 +0x300
MSH-Version
2.5.0
MSH-Commit
Operating system
Linux
System architecture?
ARM 64 Bit
Minecraft Version
1.20.1
Minecraft Server Software?
Fabric
Is there an existing issue for this?
- I have searched the existing issues before opening this issue.
- I have provided all relevant details.
I just fixed it, I had an instance already launch of it and it interfere with the one I tried to launch