What kind of specs does a server need to run DH?
I’ve got a server with 8 virtual cores and 25 gigs of RAM. Still every time I try to run DH on it, it eventually crashes. Either how do I fix this or how far do I need to upgrade? It’s a Vanilla+ server
18 Replies
Does it crash from oom or another reason? Can you send logs?
/logsstored
You should send your
latest.log file to provide additional useful information.
Logs are usually located in the .minecraft/logs directory.
On Windows: %appdata%\.minecraft\logs
On Linux: ~/.minecraft/logs
On Mac: ~/Library/Application Support/minecraft/logs
Please upload the file to mclo.gs instead of sending the raw file. This makes reading the contents of the file a lot easier and improves the chances of you getting the help needed.
After uploading the file, click on Save and send the link.i would really like a log that has the crash and is uploaded to mclo.gs
there are some errors there, but it doesnt look like they crashed the server
do you have a crash report maybe?
From the server?
yeah one or two
Are you using a web panel and/or running the server under Docker?
I dont know. I'm running a server owned by Witherhosting
Right, so you have a web based admin panel to control the server?
Are you in control of the launch args for it? Specifically
-Xmx?
Try removing xmx and using -XX:MaxRAMPercentage=95.0 instead.
This will leave 5% of the available memory free for other Java things. Xmx sets the max heap size, and you cannot use all of your available memory for heap - the server will end up using too much memory and getting killed by the admin panel
@Puhpine This should be in the FAQwill this put a hard limit or somethin? ( cuase my server also crash periodiccally oom )
No, it just sets the max heap size to 95% of available memory, instead of 100% like most people do
the thing is, it far crosses my xmx value most of the time
That's what I'm saying. Xmx is not the max memory size for the entire Java process. It's for the heap only. So if you set the max heap size to 10 gigs, the total memory used is likely to be closer to 11 or even 12 gigs
Which is why you cannot set Xmx to the actual max available memory, because you'll be lying to Java and telling it ca allocate more memory than it actually is able to
And when it tries, it gets killed
The example argument I gave with 95% is just a starting point. Adjusting it might be necessary
i am running xmx two gb lower then avalable
i think this would give gimilar results
Yup
Ok ty
Sure. How should I word it? I can't think of how to word the Q since it's so generic