steam_api.so issue
upl1nk-v01d opened this issue · 4 comments
From today I'm encountering an error with dedicated COD4x server on linux.
When I launch my server without steam_api.so, the server immediately crashes, otherwise it works with steam_api.so.
The reason I'm removing steam_api.so is because with my client I cannot connect to my dedicated server, the error message: "Steam is not running. Please start your Steam client and login". I had described this issue on #332. And steam_api.so is the issue again.
This wasn't the problem about 6 months till today. I absolutely do not know what happened because there was no problem with linux server without steam_api.so. I used null routing to stop server from automatic updating. So the server wasn't updated in this time period. Please see my log below:
CoD4 X - linux-i386 build 1104 Aug 1 2021
--- Crypto Initializing ---
Testing sha1 hash function - positive.
Testing sha256 hash function - positive.
Testing tiger hash function - positive.
--- Crypto Initialization Complete ---
IP: 127.0.0.1
IP: 192.168.1.102
IP: 192.168.122.1
IP6: ::1
IP6: fe80::6d2b:56be:b3ff:4a28%wlan0
Opening IP6 socket: [::]:28960 UDP
Opening IP6 socket: [::]:28960 TCP
Opening IP socket: 0.0.0.0:28960 UDP
Opening IP socket: 0.0.0.0:28960 TCP
CoD4X Auto Update
Current version: 1.8
Current subversion: 20.1
Current build: 1104
New subversion 20.1
Downloading file: "steam_api.so"
]free(): double free detected in tcache 2
This program has crashed with signal: Aborted
The current Gameversion is: CoD4 X - linux-i386 type 'e' build 1104 Aug 1 2021
File is ./cod4x18_dedrun Hash is: 43493a8d0c2c4c14975894dd9fa76bc59f6343eed6dc473b22642a691535f718
---------- Backtrace ----------
17: ./cod4x18_dedrun(Sys_PrintBacktrace+0x31) [0x809d97b]
16: ./cod4x18_dedrun(Sys_DumpCrash+0x92) [0x809da56]
15: ./cod4x18_dedrun(Sys_SigHandler+0x24) [0x809dacc]
14: linux-gate.so.1(__kernel_sigreturn+0) [0xf7ed7080]
13: linux-gate.so.1(__kernel_vsyscall+0x9) [0xf7ed7069]
12: /lib/i386-linux-gnu/libc.so.6(gsignal+0xc2) [0xf7a53382]
11: /lib/i386-linux-gnu/libc.so.6(abort+0xf0) [0xf7a3d2b6]
10: /lib/i386-linux-gnu/libc.so.6(+0x70d2c) [0xf7a94d2c]
9: /lib/i386-linux-gnu/libc.so.6(+0x77aed) [0xf7a9baed]
8: /lib/i386-linux-gnu/libc.so.6(+0x79459) [0xf7a9d459]
7: ./cod4x18_dedrun() [0x80a005c]
6: ./cod4x18_dedrun(FileDownloadFreeRequest+0x12) [0x80a3ca1]
5: ./cod4x18_dedrun(Sec_Update+0x548) [0x81060c1]
4: ./cod4x18_dedrun(Com_Init+0x314) [0x80df167]
3: ./cod4x18_dedrun(Sys_Main+0x51) [0x80a5c41]
2: ./cod4x18_dedrun(main+0xf9) [0x809d65d]
1: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xf7a3eb41]
0: ./cod4x18_dedrun() [0x809c06a]
-- Registers ---
edi 0x0
esi 0x8
ebp 0xffb962dc
esp 0xffb962c0
eax 0x0
ebx 0x2
ecx 0xffb962dc
edx 0x0
eip 0xf7ed7069
-------- Backtrace Completed --------
Received signal: Aborted, exiting...
Server received signal: Aborted
Shutting down server...
Allright! I solved this again by null routing cod4update.cod4x.me to different network protocol not to an ip address.
Please close this issue. :)
Could you perhaps share a snippet of how you did it? Currently experiencing similar problems when running cod4x in docker (arm84/v8 box86)
I'm currently on work.
I will post my instructions tomorrow.
- delete steam_api.so from your cod4x game dir.
- to avoid downloading cod4x updates, including steam_api.so, run in your linux terminal following cmd:
sudo route add 188.165.57.239 dev eth0 - append route cmd to your /etc/rc.local file for pernament execution.