SIGSEGV error, server crashes minutes after - happens frequently

Hi!
Recently I have had problems with my server. It suddenly crashes, and I don’t really know the reason for it. The server can run for an hour and crash, or it can run for 6 hours and crash - which is weird. Whenever it happens, it just throws a lot of stacktrack code and a SIGSEGV error at the end of it.

I have installed mono, and it’s the most recent version. I have tried to disable multiple resources without any changes, will try to disable everything eventually but it sucks to do that on a server that has a lot of players on it. I do have the same script running on a test server, and there it’s fine as there’s not many players playing - therefore I believe it’s a resource issue. Or the SIGSEGV error pops up as soon as I shut down the test server too, but it doesn’t crash it self (atleast havent so far).

Here’s all the shit that’s being printed out once it happens:
https://pastebin.com/TLRWeCyT

Anyone knows what can cause it? Using the ESX framework.

What server artifacts version are you using?
Also what OS is the server running on?

I have tried the latest artifact and the one from 18th of April, same problem with both.
Running linux with ubuntu 16.04 distro.

I get this as well when running multiple servers at once on linux with the same user account. Though that shouldn’t crash the server just 6 hours after starting it.

Have you tried to turn off your test server for the time being, and just running 1 server (your main one that keeps crashing) at a time?

Also, I know it sucks, but if the above doesn’t help, try removing all plugins, and get your players online for a couple of hours, I guess you could even enable scripthook temporarily so your players have something else to do on your server for one day just to test this, and see if it still crashes.

1 Like

I’m running my test and main server on two separate linux servers.
I’m currently disabling resources now and testing, and have tried to disable those resources that I have edited recently but they didn’t make any difference, so weird that it happens to older resources that worked well earlier.

it is indeed strange that this is happening. Only testing will probably show if it is resource related or actually a server configuration issue or fxserver/mono issue.