[💥]: Still Server Crashing

[Voxy72]

Was this crash report before?

• No, it was not.

Version modpack used

0.7.19

Environment

Server

Side Crashed

Server

New Worlds

Yes

Please provide a link to your latest.log, if relevant

https://github.com/user-attachments/files/18552145/crash-2025-01-26_18.47.37-server.txt

Steps to Reproduce

Last Thread (#762)
Still having no luck with starting server on linux Debian
I can try to debug by myself as much as i can but i am not very good with java
any help would be great
2 Of new Crash Reports They are i think different then last time (not as important it doesn't close the server it keeps running and using ram and cpu )
(https://github.com/user-attachments/files/18552144/crash-2025-01-26_18.58.07-server.txt)
(https://github.com/user-attachments/files/18552145/crash-2025-01-26_18.47.37-server.txt)
PS... Thanks in Advance

Additional Information

No response

[Xikaro]

Have you tried installing from scratch?

[Voxy72]

I have tried to install on my laptop(with debian) and it worked. But nothing for the server that i am having trouble. I will investigate soon.What is with the server and the OS. So if the bug is because it is in VM(ProxMox) or CraftyControler.I will report back.
PS... Just so you know on windows it runs fine,also it would be great to add start.sh for the linux users.
Thanks a lot
Start.sh
java -jar minecraft_server.jar -Xms1024M -Xmx 6144M nogui

[Supermarcel10]

I remember I had a few issues with the server running on Linux. For me, I use Ubuntu, and the MC server runs in docker. That said, the server did initially work for me out of the box, but had minor issues.

I see a few issues here. Some of them are minor, whereas others are problematic - and most likely the cause of this.

Memory Allocation Issue

You mentioned that you run java -jar minecraft_server.jar -Xms1024M -Xmx 6144M nogui, however from the crashlogs it seems the Xms is being set to 718MiB and Xmx is being set to 3748 MiB. I have encountered this issue before. This is because minecraft_server.jar is actually a wrapper, not the direct executable of the forge server itself.

Running the wrapper once will pull in the desired forge version, after which it can be discarded (if you wish not to use it). Not really sure what the wrapper does exactly, not really a fan of it, but it seems something with logs. For me it has caused more harm than any help at all - causing memory leaks.

If you want to bypass the wrapper, you can run the forge executable directly using something like:

java -Xms128M -Xmx 6144M @/libraries/net/minecraftforge/forge/1.20.1-47.2.6/unix_args.txt
                                                              ^
                                                              |
                                                        FORGE VERSION MAY BE DIFFERENT HERE

That said, it does not seem to be a memory error, else you would get the state "out of memory: true", which is not present on the log. Instead, it seems like mixin/mod conflicts - which is unusual to see.

World Locked

In your logs it seems like the world file is locked, preventing the server from starting up. This sometimes happens when the world is not correctly flushed to disk (the session lock is released when the instance gracefully shuts down) or currently in use by another instance. For e.g. a sudden crash, incorrect shutdown, or another instance already running is the primary cause.

Caution

Before you do anything, back up your world! Worst case scenario, the world will become bricked.

1. Shutdown the server; gracefully if possible, kill the instance otherwise.
2. Search if there are any other instances running on the server. (Use top, ps aux | grep java or anything you prefer). If you find any instances of the server running somewhere, repeat step 1 for them.
3. Once all instances are shutdown, destroy the session lock file using:

rm /home/mc/Desktop/TerraFirmaGreg-Modern-0.7.19-serverpack/world/session.lock

Start your server up as normal, and it should now work as intended.