[poel]

@Asherkin,

So, what Can I do to fix that : [CRASH] Accelerator failed to upload crash dump: The requested URL returned error: 400 (22)

??

[DarkDeviL]

Originally Posted by ejk499 If the problem is in capacity, then maybe it would be better to just prioritize reports processing?

You were presented with the AlliedModders Rules when you signed up today. Did you read them at all?

Supporting "no-steam" is a no go.

Originally Posted by ejk499 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)

If you won't run a legitimate server, then I suggest you leave this forum alone.

[PresidentEvil]

is there a way to log what map the server was on when it crashed, it would really help in rooting out bad maps

[asherkin]

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.)

[poel]

Originally Posted by PresidentEvil is there a way to log what map the server was on when it crashed, it would really help in rooting out bad maps

Well, its ez.

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)

[PresidentEvil]

Originally Posted by poel Well, its ez. 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)

no I rather have accerator note the map in the crash log, making it easy to view on crash.limetech.org instead of opening up ftp and digging through large ass log files..

[8guawong]

Originally Posted by PresidentEvil no I rather have accerator note the map in the crash log, making it easy to view on crash.limetech.org instead of opening up ftp and digging through large ass log files..

i agree with presidentevil this feature would be awesome! (hopefully this post won't be deleted )

[asherkin]

Originally Posted by PresidentEvil is there a way to log what map the server was on when it crashed, it would really help in rooting out bad maps

This is now in 2.2.1, you wont find it displayed on Throttle yet, but if you append "/metadata" to the URL you can see the raw data and it's at the top.

Originally Posted by 8guawong i agree with presidentevil this feature would be awesome! (hopefully this post won't be deleted )

No, it's just spammy. I already said I would add it, further evangelizing is just pointless and taking up space.

Originally Posted by poel About my error Asherkin, What can I do to fix that ?

I've already answered you, the problem is in Breakpad and there is nothing I can do about it since I can't reproduce it, and never have been able to - I only know of 3 people it affects, which is tiny and implies an obscure OS misconfiguration.

[poel]

Its possible to copy logs in a txt file maybe on ftp ?

[asherkin]

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.