#problem with minecraft server

62 messages ยท Page 1 of 1 (latest)

main knot
keen skiffBOT
#

โŒ› This post has been reserved for your question.

Hey @main knot! Please use /close or the Close Post button above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 720 minutes of inactivity.

TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.

shut furnace
#

Hmm, it segfaults when trying to build a message for a ClassCastException.

raven gale
#

and it seems to be caused by netty

#

j io.netty.buffer.AdaptivePoolingAllocator$Magazine.newBuffer()Lio/netty/buffer/AdaptivePoolingAllocator$AdaptiveByteBuf;+29

#

Can you try without -DLeaf.enableFMA -DLeaf.disable-vanilla-profiler -DLeaf.enable-io-uring?

#

Also a heap size of 60GB? wow

#

Is there any agent injected somewhere?

main knot
raven gale
#

No it's fine that shouldn't be the problem

#

Do you know what that is? it.ytnoos.lpx.lib.com.github.retrooper.packetevents

main knot
raven gale
#

yeah it might be related to that

main knot
raven gale
#

idk what you changed but it would be possible

main knot
raven gale
#

Especially without IO Uring

main knot
#

i tested it before

raven gale
#

recycler.get() returns something that is not an AdaptiveByteBuf for some reason

#

actually not entirely sure

old sun
#

I just want to add that the crashes occur at different uptimes, sometimes after a few hours, sometimes even immediately after turning on, and almost every time we get a different error. I'm sending here more logs that I managed to collect.

raven gale
#

You are using the JDK "OpenJDK Runtime Environment Temurin-21.0.10+7 (21.0.10+7)"

#

you could try updating to 21.10.11

old sun
#

Do you think it's definitely not because we had 60gb heap?

#

On the previous server we had 48GB and there were no such problems. Our hosting provider also says that if it was a physical problem with RAM, the entire system would crash, not just Java.

raven gale
old sun
#

Okay, so far we have 40 minutes of uptime and there is no crash after changing the heap to 30GB. If it crashes again, I will do some memory tests, maybe it will show something.

raven gale
#

And it seems like the crash logs you provided are all segmentation fauls (except one SIGILL) from different location

#

so a memory failure sounds like a plausible option

#

and SIGILL means there's an illegal machine instruction which doesn't easily happen without a memory failure

#

Theoretically you could also try to download one of the coredumps and try to analyze them

old sun
#

yea it crashed again

raven gale
#

The logs mention

Core dump will be written. Default location: /home/container/core.1

#

But these files will probably be big

#

I think they contain the entire memory

old sun
#

yes, but it's nowhere in the pterodactyl panel

raven gale
#

Since it seems to be using some containerization, the file is probably removed once the program stops

#

If you can do that, try to check for memory failures or similar

old sun
#

Do you think coredump would actually help with this? If so, I can try to change something in the pterodactyl so that it doesn't delete itself

#

for now i will try running memory tests

raven gale
#

Maybe maybe not. I think it would be possible to read some things but core dumps are annoying to analyze

#

They basically allow "reviving" the JVM into a state where it cannot run any code but you can inspect some things

raven gale
# old sun

btw I think the last two log files there are exactly the same (but that doesn't make a difference)

#

The error occured in regular (JITed) Java code, native code and even in GC code

old sun
#

I ran memory test and the whole dedicate turned off, so it looks to me like it's a physical RAM problem.

keen skiffBOT
#

๐Ÿ’ค Post marked as dormant

This post has been inactive for over 720 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.

old sun
#

Hello, it turned out that the RAM was actually physically damaged, so I have another question, apart from these crashes, what would be the appropriate heap size for a Minecraft server with +- 200 players or is it better to have closer to 30 or 40GB?

raven gale
#

I don't know much about Minecraft servers

old sun
#

I'm rather concerned about the Java itself whether the heap size has any greater significance

raven gale
#

but there are some general tricks about heap sizing

#

A bigger heap size will typically make it easier for the JVM

#

but ofc you don't have infinite memory available

old sun
#

I have 110 GB of RAM available, but I want to assign a reasonable amount of RAM to the heap, max 45 GB, so that the GC doesn't have problems.