mtasa-blue

mtasa-blue copied to clipboard

Describe the bug

Linux server crashes on startup.

Steps to reproduce

1. Start server
2. After initial welcome message block server crashes.

Version

MTA:SA Server v1.6-r21935-release

Not sure what is the linux version, may request info from hosting provider if needed.

Additional context

crash.zip

Relevant log output

MTA:SA Server v1.6-r21935-release crash report.
2023-08-07 21:47
Caught 25 addresses ...

Backtrace:
#0 - ./core.so(+0x73bad) [0xf7c10bad]
#1 - ./core.so(+0x9d69a) [0xf7c3a69a]
#2 - ./core.so(+0x9dada) [0xf7c3aada]
#3 - linux-gate.so.1(__kernel_rt_sigreturn+0) [0xf7f920a0]
#4 - linux-gate.so.1(__kernel_vsyscall+0x9) [0xf7f92079]
#5 - /lib/i386-linux-gnu/libc.so.6(gsignal+0xc2) [0xf7da4a02]
#6 - /lib/i386-linux-gnu/libc.so.6(abort+0x121) [0xf7da5e91]
#7 - /lib/i386-linux-gnu/libc.so.6(+0x6fe53) [0xf7de6e53]
#8 - /lib/i386-linux-gnu/libc.so.6(+0x109bea) [0xf7e80bea]
#9 - /lib/i386-linux-gnu/libc.so.6(+0x109b9b) [0xf7e80b9b]
#10 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x8d9b58) [0xf6ec2b58]
#11 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x37305a) [0xf695c05a]
#12 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x2dd7db) [0xf68c67db]
#13 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x2e5a4a) [0xf68cea4a]
#14 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x2e76f5) [0xf68d06f5]
#15 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x308e64) [0xf68f1e64]
#16 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x30a01f) [0xf68f301f]
#17 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x1f88e0) [0xf67e18e0]
#18 - /usr/local/gpx/users/nonstopdayz/51.77.237.112-22008/mods/deathmatch/deathmatch.so(+0x131ca2) [0xf671aca2]
#19 - ./core.so(+0x76085) [0xf7c13085]
#20 - ./core.so(+0x79538) [0xf7c16538]
#21 - ./core.so(Run+0x98) [0xf7c31078]
#22 - ./mta-server(main+0x2a6) [0x56643f86]
#23 - /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xf7d8ffa1]
#24 - ./mta-server(_start+0x35) [0x56644635]
--------------------------------------------------------------------------------

Security Policy

• [X] I have read and understood the Security Policy and this issue is not security related.

I checked linux 32 21942 build with default resources on debian 12 x86 and on ubuntu 22.04 x64. I got no crash after startup. Also i got no crash after join on ubuntu (i didn't check this on debian).

Hosting uses: Ubuntu 18.04 LTS OS

Hosting uses: Ubuntu 18.04 LTS OS

for fix handmade solution, try to do systemd-nspawn with debian12 x86 and run your MTA server into it.

Hosting uses: Ubuntu 18.04 LTS OS

for fix handmade solution, try to do systemd-nspawn with debian12 x86 and run your MTA server into it.

Unfortunatelly it is not my hosting, but game-servers host, with containers, and no access to OS

Hosting uses: Ubuntu 18.04 LTS OS

for fix handmade solution, try to do systemd-nspawn with debian12 x86 and run your MTA server into it.

Unfortunatelly it is not my hosting, but game-servers host, with containers, and no access to OS

No way to help, because the version OS which the version of MTA server was built about 20.04

Hey There,

• Try disabling plugins;
• Update or reinstall modules;

If still doesn't work try contacting your host provider.