Bug 14403 - Add reason to uploaded crash reports
: Add reason to uploaded crash reports
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Diagnostics
: unspecified
: PC Windows XP
: P1 normal (vote)
: 7.4.1
Assigned To: Brandon Black
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-29 11:36 UTC by Richard Titmuss
Modified: 2009-10-22 11:23 UTC (History)
2 users (show)

See Also:
Category: Feature


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Titmuss 2009-09-29 11:36:31 UTC
per discussion in campfire:

Richard T.	
so a change i'd like to investigate for 7.4 is added why it crashed to the logs. so we can pull that out more easily (like segfault, timeout, oom, etc)
i'll look at that tomorrow, if it's easy i'll add it.
Brandon B.	
agreed
11:35 AM
Brandon B.	
if you can just make it a short field in the json data that's sent, it's trivial from there with the current system server-side
Comment 1 SVN Bot 2009-09-30 07:47:19 UTC
 == Auto-comment from SVN commit #7811 to the jive repo by richard ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7811 ==

Bug #14403
Add uptime and failure to the uploaded crash logs.
Comment 2 Richard Titmuss 2009-09-30 07:48:07 UTC
Brandon, 7.4.1 should now upload two extra fields with useful info, 'uptime' and 'failure'.
Comment 3 SVN Bot 2009-09-30 08:25:41 UTC
 == Auto-comment from SVN commit #7525 to the network repo by blblack ==
 == https://svn.slimdevices.com/network?view=revision&revision=7525 ==

fixes bug 14403: pass crashlog uptime/reason fields from json to splunk
Comment 4 James Richardson 2009-10-22 11:23:26 UTC
This bug has been marked as fixed in the 7.4.1 release version of SqueezeBox
Server! 

Please see the Release Notes for all the details:
http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from
http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with
your new comments and we'll have another look.