Roy 10,832 / 0 Report Post Posted May 11, 2019 Hi all, I just wanted to address a server crash both our 2Fort and High Tower servers experience when performing 2 - 3 map changes over the span of 3 - 5 days. The server crashes as soon as the map changes and there is no engine error before the crash. Here is the stack trace: Program terminated with signal SIGABRT, Aborted. #0 0xf7f17029 in __kernel_vsyscall () [Current thread is 1 (Thread 0xd7cffb40 (LWP 84))] #0 0xf7f17029 in __kernel_vsyscall () #1 0xf7d5eea9 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf7d60407 in abort () from /lib/i386-linux-gnu/libc.so.6 #3 0xf7d9a37c in ?? () from /lib/i386-linux-gnu/libc.so.6 #4 0xf7e2a6b8 in __fortify_fail () from /lib/i386-linux-gnu/libc.so.6 #5 0xf7e288a8 in __chk_fail () from /lib/i386-linux-gnu/libc.so.6 #6 0xf7e2a5aa in __fdelt_warn () from /lib/i386-linux-gnu/libc.so.6 #7 0xf65ff276 in CBlockingUDPSocket::WaitForMessage(float) () from /home/container/bin/engine_srv.so #8 0xf6724861 in Win32UploadGameStatsBlocking(TGameStatsParameters const&) () from /home/container/bin/engine_srv.so #9 0xf67253f7 in CAsyncUploaderThread::ThreadProc() () from /home/container/bin/engine_srv.so #10 0xf6725aa1 in CAsyncUploaderThread::CallbackThreadProc(void*) () from /home/container/bin/engine_srv.so #11 0xf7eef295 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0xf7e1a05e in clone () from /lib/i386-linux-gnu/libc.so.6 This is a very odd crash considering it's calling Linux functions. The only entries that refer to the Source Engine itself is towards the end of the stack trace (e.g. "CBlockingUDPSocket:WaitForMessage(float)"). I might try to learn more about GDB and how to inspect the core dump file. Specifically, I'm curious about how to retrieve the float parameter's value in the CBlockingUDPSocket:WaitForMessage function. I plan to open the engine_srv.so file in IDA and look for this function to see if I can gain more information on what it exactly does. Thank you! Share this post Link to post