Buffalo

1.4 linux server keeps crashing

Recommended Posts

Hello,

Server is running debian-6.0, MTA 1.4-release-6760, using pre-compiled server files from linux.mtasa.com.

Error on crash:

http://i.gyazo.com/6c572078cf1f88abf687e7119a6b3d98.png (bad_allocation?)

Crash happens after awhile, somewhere in the middle of 20mins to 4 hours.

Gamemode scripts are mostly running client-side. Script is based on peds.

Major server scripts based on custom files downloading, that works very well. E.g. no open file handles reported by performancebrowser. Actually can't see anything abnormal in performancebrowser.

Although, there are some server side peds, like bosses, that must be synced correctly.

Also, this gamemode is 1 year old, with nothing special added (except file downloader), it worked perfect on MTA 1.3.3.

I forgot how to debug crash deeper, since I had last server crashes on this gamemode on early MTA versions. Once someone reminds what to use, I will try to collect more information it dumps.

EDIT: Crash seems pretty random. Worked 9 hours straight without incident.

Edited by Guest

Share this post


Link to post

I have same experience. what I did is to read the dump file. even it was encrypted. finally I found some information just above the hardware description. there is a resource name, which was a dayZ addon for anti-corpse-copy. I guess maybe some variables or data table overflow. so later I write a script to restart that resource every half hour. now the server is never crash

Share this post


Link to post

At least you can read a dump file. I never got one.

BTW nice english.

Edited by Guest

Share this post


Link to post

Thanks.

I'm almost certain the crash is due to the process running out of memory. Can you PM me the script that does the latent sends to the clients?

Share this post


Link to post

Change your triggerLatentClientEvent code so the server only sends one file at a time - This will prevent the server from queuing all the file requests (which uses memory).

Also make sure the server never sends the same file more than once for any client - This will prevent hackers causing memory problems by constantly triggering the 'download' events

Share this post


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.