Server Crash: 13 Segmentation fault (core dumped)

Aloha,
I’ve noticed over some time that our server crash restarts and kicks everyone. I had not seen why before and there may have been different reasons.

I finally caught a line of code that may tell something important this time, but I’m not sure what caused it.

/entrypoint.sh: line 13: 13 Segmentation fault (core dumped) ./BeamMP-Server

We had maybe 5 people in the server. No crazy loads on the server. I believe one person had just logged in moments before.

Here’s more of the previous log:
[08/09/24 19:46:04] [LUA] [Cobalt] On Player Join: 5
[08/09/24 19:46:04] [CHAT] (to everyone) Dirty_media1787 joined the game
[08/09/24 19:46:04] [INFO] Dirty_media1787 is now synced!
[08/09/24 19:46:26] [CHAT] (to everyone) SVT_Texan: 01:04:59.877 Trail: 2 Pit: 2

/entrypoint.sh: line 13: 13 Segmentation fault (core dumped) ./BeamMP-Server
container@pterodactyl~ Server marked as offline…
[Pterodactyl Daemon]: ---------- Detected server process in a crashed state! ----------
[Pterodactyl Daemon]: Exit code: 139
[Pterodactyl Daemon]: Out of memory: false
[Pterodactyl Daemon]: Updating process configuration files…
[Pterodactyl Daemon]: Ensuring file permissions are set correctly, this could take a few seconds…
container@pterodactyl~ Server marked as starting…
[Pterodactyl Daemon]: Pulling Docker container image, this could take a few minutes to complete…

I don’t know if that means much to anyone, but if there are suggestions, I’d love to hear it. It doesn’t happen all that often, but if there’s improvement that can be made, I’d love to try.

Mahalo
-Sam

Sorry for the delay, I’m going to refile this topic into the “server support” section and bring it to the attention of the larger Support team.

Thank you. Appreciate you moving it to where it needed to go.

Aloha by the way. I see we both live on the same volcano.

1 Like

Happy humuhumunukunukuapua’a to you,

Alright, so I’ve been told that this is an ongoing issue that is still under investigation. Some of the more common causes are.

-People connecting to the server with bugged/cracked clients.
-Sustained high player counts
-Plugin issues

Hopefully one of those causes is what is afflicting your server and you can solve it, if not the best course of action may be to have everyone refresh their user folders, BeamMP installs and redo your server to make everything brand new and try again.

Sorry we can’t give you a more direct answer, but the back end team is working on this problem in the hopes that future troubleshooting for this issue is either far easier or not needed at all.

I appreciate that and a happy Haupia day to you.

It seems in our case it’s a connecting to the server issue. I don’t quite know what would be a bugged or cracked client, but I can see what we are using and if there’s something odd there.

Both of these scenarios came on a map that is built at 8k which can have issues loading at times. Maybe that’s our situation, but it’s definitely happened on other maps and servers of ours.

Here was the latest one tonight. The only difference is the “14 Segmentation” instead of “13 Segmentation”. This happened when I was trying to log into the server.

/entrypoint.sh: line 13: 14 Segmentation fault (core dumped) ./BeamMP-Server

I’ll welcome you guys to our servers if there’s any interest to test.