Accelerator - Crash Reporting That Doesn't Suck
Accelerator replaces the default SRCDS crash handler with one that is a lot more reliable and uploads the crash reports to a community-accessible processing backend.
This is useful since Valve's processing system discards crash reports from modded servers - and they still receive a representative sample of crash reports for actual game issues. The processing backend (Throttle - https://crash.limetech.org/) analyses crash reports to extract useful information, and in the case of common issues affecting many servers where manual analysis has been done, tags them with helpful notices with information on resolving the cause of the crash. Previous versions of Accelerator have been in use on hundreds of servers since 2010 (as of this thread's creation, Throttle has processed over 30,000 crash reports in the last 90 days), this is a re-release as a lot has changed since then. If you're running any earlier version (including the previous extension alpha build), please upgrade to 2.4.3+. Installation
Configuration Edit addons/sourcemod/configs/core.cfg to add the following key: Code:
"MinidumpAccount" "<insert your steamid here>" So your core.cfg will end up looking like (with your own steamid): Code:
"Core" The full set of available options with their default values and documentation are below, you should only put ones you intend to change into core.cfg: Code:
"Core" Once running on your servers, whenever they crash they will write a crash dump into sourcemod/data/dumps/. Next time the server starts it will upload any pending crash dumps in that directory to Throttle (https://crash.limetech.org/), you can login to that site using Steam OpenID authentication to view any processed crash reports owned by you. Accelerator logs all upload activity to sourcemod/logs/accelerator.log, from there you can see all uploaded crash IDs and error messages if any fail to upload. The crash dump uploader is threaded so will not impose any startup delay on your servers. Crash dumps plus metadata are generally less than 500kb combined. There may be additional uploads occasionally if your server has symbols available that Throttle does not have yet. Security Crash dumps can contain sensitive information such as RCon / Database credentials, as they are produced by saving key parts of SRCDS' memory space. As standard, crash reports uploaded to Throttle will contain at least the following information:
As of version 2.4.x, Accelerator can now partially preprocess crash reports locally before upload, and process modules loaded into SRCDS' memory for symbol files (this is a hard restriction in the code, it won't touch any other files). The latter, if enabled, will cause files to be processed locally and uploaded to Throttle. See the MinidumpSymbolUpload and MinidumpBinaryUpload options above for more information. Throttle maintains strict security controls, only the owner of the crash (the SteamID specified in core.cfg), people the owner selects to share their reports with on the website, and a select set of SourceMod Core team members can access full crash reports. Everyone else can only see the crashing thread's call stack and any assigned notices, so please do link Throttle crash reports directly if you're seeking help rather than just copying the stack trace / taking a screenshot. That said, please do not post in this thread looking for help diagnosing a crash. Create your own thread in the Source Servers section where you'll get much better help and will not fill up this thread with transient trash. Supported Games At a basic level Accelerator should work with all games on both Linux and Windows. Games with enhanced support will additionally get console output included in crash reports. Windows (and CS:GO) crash reports are generally useless if they do not directly crash due to SourceMod, this is because Valve continue to refuse to provide stripped symbol files (like Microsoft provide for Windows). Download Source Code Build Status https://travis-ci.org/asherkin/accel...?branch=master https://ci.appveyor.com/api/projects...aster?svg=true |
Re: Accelerator - Crash Reporting That Doesn't Suck
Nice release! Updated my servers, Accelerator has always been a great help for me. Keep up the good work!
|
Re: Accelerator - Crash Reporting That Doesn't Suck
sounds nice! can't wait to try this great job master!
|
Re: Accelerator - Crash Reporting That Doesn't Suck
What about backend sorucecode? For example start this service in private network.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Nice update, but I cant understand.
When server crash, nothing happen ! I mean, I dont have any logs on the website ! I just have to install extension and add my steam in core file ? log sm : Failed to upload crash dump: The requested URL returned error: 400 (22) |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
I've never been able to replicate the issue and it appears to be an OS-level problem, I would need access to your host to look into it. |
Re: Accelerator - Crash Reporting That Doesn't Suck
Is it possible to revert a375772 commit?
Serveral servers of my friend was damaged by this commit. He realy enjoyed Accelerator because it saved him a lot of times! He is using "thing, that cannot be spoken" not on his own, but because all of his local competitors use it and without it his online will suffer. The amount of CSS players is dramatically decreasing and by now, the amount of players using "thing, that cannot be spoken" and not using it is almost the same. |
Re: Accelerator - Crash Reporting That Doesn't Suck
No, by far most of Throttle's processing capacity was being used by no-steam servers.
While that capacity is seriously constrained, I wish to make it available to legitimate servers. |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
1. Legit 2. Legit ES crash 3. no-steam 4. no-steam ES crash (Almost all servers, that uses ES is a WCS servers, and they are crashing every 1-2 hours) |
Re: Accelerator - Crash Reporting That Doesn't Suck
@Asherkin,
So, what Can I do to fix that : [CRASH] Accelerator failed to upload crash dump: The requested URL returned error: 400 (22) ?? |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
Supporting "no-steam" is a no go. Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
is there a way to log what map the server was on when it crashed, it would really help in rooting out bad maps
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Sure, is there anything else you would find useful?
(I have a long list, but it makes sense to prioritize - and some of it is just not possible without SM changes.) |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
Crash log can tell you the time when server crash, then just check your "log" files, and see at the same time which map was used. About my error Asherkin, What can I do to fix that ? [CRASH] Accelerator failed to upload crash dump: The requested URL returned error: 400 (22) |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
Quote:
Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Its possible to copy logs in a txt file maybe on ftp ?
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Throttle now shows you how many other people are getting similar crashes, this should help to identify actual bugs (especially post-update) vs wierdo issues.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
hello i try to compile but i get:
Code:
git clone https://github.com/asherkin/accelerator.git accelerator Quote:
Code:
ambuild Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Accelerator is using AMBuild1, not AMBuild2 - see the TravisCI (.travis.yml) or AppVeyor (appveyor.yml) configs for what dependencies you need and commands you need to run.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Thanks!
|
Re: Accelerator - Crash Reporting That Doesn't Suck
So I just learned how to find windows signatures and how to decipher windows stack traces.
Does this extension cause any noticeable overhead while it's being run on the server or none? Thanks! |
Re: Accelerator - Crash Reporting That Doesn't Suck
Effectively none, it only does work on a crash and when the server first starts (which is all offloaded to a thread in current versions).
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
You can find timestamped log messages in the SourceMod error log.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
My server crashes evertyime map changes during the game not like on start, accelerator says dump was created with ID ( number) but when i look at dumps folder its empty
|
Re: Accelerator - Crash Reporting That Doesn't Suck
They are deleted after upload, enter the ID you were given into the web page.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Just saw this in a random crash report:
"The server that this crash is from has been modified to allow pirated game clients to join." Why aren't you just outright discarding and refusing to process these crashes? Don't we reject no-steam servers? Even if you must fully process them to determine it is a cracked server, I still don't see any harm in just discarding the processed data and saying "no-steam servers are not supported by this application". I could be talking out of my ass so I don't know. |
Re: Accelerator - Crash Reporting That Doesn't Suck
Subsequent reports from the same server are discarded for the next 90 days.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
asherkin can you gather a list of map that are causing the server.so!CCSPhysicsPushEntities::EnsureValid PushWhileRiding(CBaseEntity*, CBaseEntity*) + 0x8b crash?
the least we can do is remove the maps from the rotation to prevent the servers from crashing every so often... |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
Code:
[ze_farmhouse_v9_fix] => 5 |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
I've spent some time today working with ImACow, who was having the same problem as you with empty crash dumps - we tracked it down to the grsecurity patch set being included in his kernel by his hosting provider. He's going to post some details for other OVH customers on how to switch to a standard kernel. Since you refused to go into details on your kernel modifications, I'm guessing you're in a similar position. Breakpad takes measures to work with the newer restrictions included in the mainline kernel, but grsecurity is too opinionated to be supported. I'm going to see what I can do to improve Breakpad's failure logging so everyone at least gets more information in these cases. |
Re: Accelerator - Crash Reporting That Doesn't Suck
Quote:
About the extension, the problem is, im using the same kernel since 2 years. I just changed my dedicated server, and now, not working anymore. So, I dont think so its from the kernel Edit : So, im guessing, some library are missing (maybe) Edit : maybe some settings on the latest dedicated servers ovh are fucked ? |
Re: Accelerator - Crash Reporting That Doesn't Suck
It's the kernel - if you provide your kernel config I can probably help you.
|
Re: Accelerator - Crash Reporting That Doesn't Suck
Will be updating Accelerator but this is terrible news. Minigame and zombie servers are screwed :(
What about WIndows servers (also ovh) |
Re: Accelerator - Crash Reporting That Doesn't Suck
|
Re: Accelerator - Crash Reporting That Doesn't Suck
"crash" engine commands create a dump which is uploaded to throttle. Can't you ignore theese report?
I'm using it to restart my server because "_restart" command will somehow shutdown. |
All times are GMT -4. The time now is 10:21. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.