Jump to content

Server Crashing, not sure why. Crash logs inside. [Debian v9.5.0]


Recommended Posts

We're currently working on a server using Debian v9.5.0 Minimal

Our server has recently been crashing quite a lot (5 times within a week) and we are unsure why. We recently switched server-provider so we're thinking it might have to do with that, although the only thing that really did change was us going from Debian v9 to v9.5.

Dump files: https://upload.mtasa.com/u/371729673/dumps_inside.zip_

Link to post

This is the only stack trace line available: 

deathmatch.so!CLuaArguments::ReadFromJSONArray [CLuaArguments.cpp : 795 + 0x8]

Since the rest is libc (part of Debian), it could be Debian related, like a Debian bug, or more likely - you use a custom libc package or build? So check that, and/or get the latest default libc version.

It means MTA server crashes on this line, which is JSON related. Do you use JSON (intensively) on in your scripts? If yes, did you recently change those scripts? (you could have added something faulty, as in heavily unoptimized or recursive, that could lead to allocation or memory problem).

If not, then an unsupported libc version in Debian could cause this (that it would fail there in JSON, by chance).

On top of all, i would advise you simply update from Debian 9.5 to Debian 10.6, and fresh install to bypass any libc package concerns.

 

Besides all that, you could try to downgrade MTA server to this build https://nightly.mtasa.com/multitheftauto_linux_x64-1.5.7-rc-20659.tar.gz as it's 1 revision before we updated JSON-C dependency in MTA. This would let you test and rule out for us that it's not MTA's fault, to see if it stops crashing. But we would definately recommend updating to 1.5.8 again if there are no positive results.

Link to post
3 hours ago, Dutchman101 said:

This is the only stack trace line available: 


deathmatch.so!CLuaArguments::ReadFromJSONArray [CLuaArguments.cpp : 795 + 0x8]

Since the rest is libc (part of Debian), it could be Debian related, like a Debian bug, or more likely - you use a custom libc package or build? So check that, and/or get the latest default libc version.

It means MTA server crashes on this line, which is JSON related. Do you use JSON (intensively) on in your scripts? If yes, did you recently change those scripts? (you could have added something faulty, as in heavily unoptimized or recursive, that could lead to allocation or memory problem).

If not, then an unsupported libc version in Debian could cause this (that it would fail there in JSON, by chance).

On top of all, i would advise you simply update from Debian 9.5 to Debian 10.6, and fresh install to bypass any libc package concerns.

 

Besides all that, you could try to downgrade MTA server to this build https://nightly.mtasa.com/multitheftauto_linux_x64-1.5.7-rc-20659.tar.gz as it's 1 revision before we updated JSON-C dependency in MTA. This would let you test and rule out for us that it's not MTA's fault, to see if it stops crashing. But we would definately recommend updating to 1.5.8 again if there are no positive results.

Thank you for the reply!

We have played around with what you said, we disabled all our JSON usage, we upgraded from Debian 9.5 to Debian 10.6, we made sure to make a fresh install of the libc package however the crashs persist. We have tried using our same scripts on our old host and everything worked flawless, therefore we concluded that this is neither the fault of MTA, nor of us, but rather of the new host.

Again, thank you for helping, we're gonna talk to our new provider and then, if they can't fix it, probably move back to our old host. This thread can be closed.

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...