asherkin
[Linux/SM 1.12] Accelerator faild to upload crash dump
Download latest version in https://github.com/asherkin/accelerator/actions and test
Accelerator (2.6.0-manual): SRCDS Crash Handler
Ubuntu 22.04.5 LTS
Test result In linux -SM v1.11 Stable Builds: fine -SM v1.12 Stable Builds: Sorry, presubmit is required
In windows -SM v1.11 Stable Builds: fine -SM v1.12 Stable Builds: fine
[CRASH] Accelerator uploaded crash dump: Sorry, presubmit is required - you may need to upgrade accelerator or adjust your config
It appears to be related to the SM version. I have to roll back 1.12 to 1.11, crash report can upload.
sm version
SourceMod Version Information:
SourceMod Version: 1.12.0.7202
SourcePawn Engine: 1.12.0.7202, jit-x86 (build 1.12.0.7202)
SourcePawn API: v1 = 5, v2 = 16
Compiled on: May 20 2025 18:24:53
Built from: https://github.com/alliedmodders/sourcemod/commit/1b8a87ca
Build ID: 7202:1b8a87ca
http://www.sourcemod.net/
related #24
cc @Kenzzer (when you have time) - this seems to prevent all crash uploads on >SM1.11 for linux 😬
Given the thorough investigation by OP this seems like an issue with webternet (i.e sourcemod issue)
Given the thorough investigation by OP this seems like an issue with webternet (i.e sourcemod issue)
How? None of that code in SM has changed in several years
just received this error. Ubuntu Server 24.04.2, TF2 32-bit, SM 1.13.0.7245, MM 1.12.0-dev+1219. have not tried to downgrade as I need features from newer SM versions.
Response module list doesn't match sent list (33 < 84)
Uploaded crash dump: Sorry, presubmit is required - you may need to upgrade accelerator or adjust your config
Where do we stand on this right now?
Response module list doesn't match sent list (33 < 87)
Uploaded crash dump: Sorry, presubmit is required - you may need to upgrade accelerator or adjust your config
SourceMod Version Information:
SourceMod Version: 1.13.0.7245
SourcePawn Engine: 1.13.0.7245, jit-x86 (build 1.13.0.7245)
SourcePawn API: v1 = 5, v2 = 16
Compiled on: Jun 21 2025 13:16:15
Built from: https://github.com/alliedmodders/sourcemod/commit/4afbf9d5
Build ID: 7245:4afbf9d5
http://www.sourcemod.net/
Metamod:Source Version Information
Metamod:Source version 2.0.0-dev+1353
Plugin interface version: 17:14
SourceHook version: 5:5
Loaded As: Valve Server Plugin
Compiled on: May 28 2025 18:31:08
Built from: https://github.com/alliedmodders/metamod-source/commit/76f36a8
Build ID: 1353:76f36a8
http://www.metamodsource.net/
This might behave differently now, I found a couple of mismatches between how Throttle was formatting presubmit responses when there were errors and how Accelerator was expecting them. If the same error is still happening, a pcap of the HTTP traffic would be very useful.
Update on this, issue is fixed in 38f7e5d6f23330e35df7f7bcde63134382bbbc33. However Throttle continues to refuse symbols upload, this doesn't prevent crash dumps from being uploaded and processed though. Symbol upload fail is unrelated OP's issue, so I'll be closing this and opening a separate issue.
Update on this, issue is fixed in 38f7e5d. However Throttle continues to refuse symbols upload, this doesn't prevent crash dumps from being uploaded and processed though. Symbol upload fail is unrelated OP's issue, so I'll be closing this and opening a separate issue.
The #24 problem is back again https://github.com/asherkin/accelerator/issues/34#issuecomment-3369342760
Accelerator upload thread started.
free(): invalid pointer
Aborted (core dumped)
This seems like an inconciliable issue, linking statically standard c++ will allow accelerator to load for l4d2 but this in turn will cause the crash with symbol upload to re-appear.
As a temporary fix I recommend that you simply delete bin/libstdc++.so.6 and bin/libgcc_s.so.1 from your server files, and let your system load its standard lib.
A more permanent fix would probably involve compiling the extension & breakpad against C++11, but I've no idea how much of breakpad would have to be edited in order to compile on C++11, especially that they've recently moved to C++20.
Edit: As things stand, I won't revert the recent changes it seems much simpler to inform l4d2 server owners to delete those libs from their servers. Unfortunately I also lack the time to investigate this more thoroughly, so this will be the solution (hopefully) for now.