Closed Bug 455418 Opened 17 years ago Closed 17 years ago

"Unable to complete request" error when trying to retrieve crash data

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: marcia, Unassigned)

References

Details

I saw this error starting yesterday mid afternoon and have not been able to retrieve any of my reports. Just got it a few minutes ago after trying to access http://crash-stats.mozilla.com/report/index/a8e4afd7-8375-11dd-95a0-001cc45a2c28.
i'm also waiting for my reports to be processed properly: bp-2ec12b00-826f-11dd-859c-001a4bd43ed6 bp-77560d54-826f-11dd-9e66-001321b13766 bp-1711e273-8311-11dd-8b20-001cc4e2bf68 bp-a497b2a8-836d-11dd-8225-001321b13766 bp-f431d1e1-836d-11dd-8ca9-0013211cbf8a leaving those reports open and trying to load in individual tabs for several hours (5+) results in a message: "Unable to Complete Request You can go to the home page or try again." with home page -> http://crash-stats.mozilla.com/ and try again -> http://crash-stats.mozilla.com/report/index/your_crash_id i asked Ted about this issue on IRC but there was no real answer ;)
OS: Mac OS X → All
Hardware: PC → All
morgamic, lars: any clue what's happening here?
well, it's an error from the new PHP code. Not being versed in that code, I don't know what conditions will cause that message. However, I can attest that I cannot get job reports either. It seems to just sit there, though, I've not gotten that specific error reported.
aravind reported that the monitor program had crashed sometime yesterday (cause under investigation). All the aforementioned crash reports are now available. I submitted a new crash and was able to get the report within 3 minutes.
I am seeing this again today - http://crash-stats.mozilla.com/report/index/a5e54d8f-84fb-11dd-bace-001a4bd43e5c is one crash, but any of my previous crashes that I click on return the same message.
This has got to be more than just a crash of monitor. I cannot bring up crashes that worked fine a couple days ago. Monitor isn't involved in the web app or bringing up existing crash reports...
Raising severity of this since we are not able to get any reports.
Severity: normal → critical
This isn't happening for me at the moment. But, I just checked in code to provide Etag, Expires, and Last-Modified headers so that hopefully the netscalers will start to cache relatively non-changing pages and give the database a breather. Not sure what else may be causing this beyond that. http://code.google.com/p/socorro/source/detail?r=516 This will need an update to production.
Additionally, all of the pending reports in comment 1 load up for me, processed, in a few seconds.
they showed up after waiting for ca. two days. new examples of my about:crashes: Report ID Date Submitted bp-98b02135-852d-11dd-912a-001321b13766 9/18/2008 4:57 AM bp-abe93c23-852a-11dd-9608-001a4bd43e5c 9/18/2008 4:36 AM from my point of view i presume there's a (kinda huge) lag of processing the reports. did the amount of incoming reports grow? is the quotient of incoming vs. processed reports the same over the last x days?
the reports i mentioned in comment 12 are now available. so there's a delay of max. 44 hours.
I can see the same with a crash id I got and have to look into: bp-c434af45-87f5-11dd-82db-001cc45a2c28 I always get the "Unable to Complete Request" error message.
I think the "unable to complete request" message was just added when a crash report page "times out" after being viewed for a certain amount of time. Les could probably comment further here. AFAICT, all it indicates is that either 1) this report doesn't exist, or 2) your report is taking an exceptionally long time to be processed.
Ted, could it also be possible that this come up when the report is not added to the processing list yet? In any way we should display a more helpful page like it was before. Now anyone can think that something is wrong with the crash report.
One thing which could confirm my idea is, that after 3 hours I get the expected report processing page now.
still see this problem? resolved with fixing the load issues?
Will resolve this WFM for now and reopen if I see it again.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Nowadays it's damn hot. I get the crash report within some seconds. I can verify that there is no timeout anymore.
Status: RESOLVED → VERIFIED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.