I had several desktop crashes last evening that never showed up. https://crash-stats.mozilla.com/report/index/bp-fea78660-91a0-4847-ac21-787982111215 and http://crash-stats.mozilla.com/report/index/bp-fd7f2277-d8f1-482b-a98e-f76f22111215 Is there any reason that this happened?
sp-collector06 is having hbase connection troubles, which none of the other collectors are having. Collectors store straight to disk then attempt to push to hbase as a background process, so this crash was collected and is stored on the disk but just hasn't made it into hbase. Since all of the other collectors are fine, I am going to file a bug right now to have IT take collector06 out of service so it can catch up, and we can see what's going on with it.
This report is now available, https://crash-stats.mozilla.com/report/index/bp-fea78660-91a0-4847-ac21-787982111215 However this one is not, https://crash-stats.mozilla.com/report/index/bp-fd7f2277-d8f1-482b-a98e-f76f22111215
(In reply to Matt Brandt [:mbrandt] from comment #2) > This report is now available, > https://crash-stats.mozilla.com/report/index/bp-fea78660-91a0-4847-ac21- > 787982111215 > > However this one is not, > https://crash-stats.mozilla.com/report/index/bp-fd7f2277-d8f1-482b-a98e- > f76f22111215 Sorry was out this morning/afternoon and didn't have a chance to comment on this yesterday - we need followup action from IT here, there are some crashes stuck on the filesystem as a result of the latest outage (related to bug 711565), we have "orphan" crashes on the filesystem. I will followup in that bug (which is blocking this one).
rhelmer: Do we have a followup bug to get those orphan crashes off the filesystem. (In reply to Robert Helmer [:rhelmer] from comment #3) > (In reply to Matt Brandt [:mbrandt] from comment #2) > > This report is now available, > > https://crash-stats.mozilla.com/report/index/bp-fea78660-91a0-4847-ac21- > > 787982111215 > > > > However this one is not, > > https://crash-stats.mozilla.com/report/index/bp-fd7f2277-d8f1-482b-a98e- > > f76f22111215 > > Sorry was out this morning/afternoon and didn't have a chance to comment on > this yesterday - we need followup action from IT here, there are some > crashes stuck on the filesystem as a result of the latest outage (related to > bug 711565), we have "orphan" crashes on the filesystem. > > I will followup in that bug (which is blocking this one).
(In reply to Marcia Knous [:marcia] from comment #4) > rhelmer: Do we have a followup bug to get those orphan crashes off the > filesystem. I was going to use bug 711565 (already blocking) to take care of this, I'll comment there right now.
Component: Socorro → General
Product: Webtools → Socorro
Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20100101 Firefox/14.0 Some of the crash reports are still not found. I crashed Firefox 14 beta 12 using the extensions: https://addons.mozilla.org/en-US/firefox/addon/nightly-tester-tools/ http://ted.mielczarek.org/mozilla/crashme.html These are the crash reports: http://crash-stats.mozilla.com/report/index/bp-0340bdd5-8b02-4579-a05b-364402120711 http://crash-stats.mozilla.com/report/index/bp-dad06d43-38d6-4f91-82b5-823382120711 http://crash-stats.mozilla.com/report/index/bp-d7cb0bda-fd56-4f60-a9f8-865a62120711 http://crash-stats.mozilla.com/report/index/bp-cc7612f0-13bd-4fac-9d92-081ad2120711
Simona B, Socorro is currently experiencing an outage on HBase, our primary crash storage system. IT and Metrics are working on the problem. They report that the system will be restored by 6am PDT. This is a very old bug dated in 2011. I'm going to close it. If problems persist, please file a new bug.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(In reply to Simona B [QA] from comment #6) All of the signatures that you reported in comment 6 return results now except for https://crash-stats.mozilla.com/report/index/bp-dad06d43-38d6-4f91-82b5-82338212071 Bumping to QA verify fixed per the age of the bug. Please file a new bug if the problem persists - thanks.
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.