Hi there! i dont know if this is the correct server for this but im getting a crash on Fedora 42 using Pterodactyl using any egg i try with the same crash. It crashes with the error code 134 which looks like a memory issue but its got 32GB ram. Here is the Log file, There is also a stack trace at the end of the log file.
#Rust Pterodactyl Crash on startup using carbon
acoustic peak
torpid chasm
Hi there! i dont know if this is the correct server for this but im getting a cr...
Have you tried starting server without plugins and harmony mods?
acoustic peak
The server is currently a completly fresh install with just carbon.
torpid chasm
Interesting
acoustic peak
altho i just notied that there is some extentions left over from trying another egg.
im running it again after deleting the entire server files.
here is the log for that.
torpid chasm
Does this fatal error occur even if you start the server without carbon?
Your logs look completely normal, until it throws that threads related error
torpid chasm
You could try rebooting OS, if you have access to
Or file support ticket, if you are in that kind of relationship with your hosting provider
It is definitely not memory related error
Could be anything
acoustic peak
Someone i know is taking a look at it. Apparently Systemctl is limiting the recoaces that the docker container can pull even tho i raised the Resource map limits to bassically max. but that doesnt seem to be affecting the Docker container.
rough jacinth