New crash signature custom field created via the web UI caused internal server error

RESOLVED INVALID

Status

mozilla.org Graveyard
Server Operations
RESOLVED INVALID
7 years ago
3 years ago

People

(Reporter: dkl, Assigned: dumitru)

Tracking

Details

(Reporter)

Description

7 years ago
This past Friday we updated the code on production to allow for enabling the
new crash signature custom field. We made the necessary changes to again
allow creation of custom fields via the web UI. I was waiting til last night (sunday EDT) to add the field to try and do it when the load would not be great. Everything seems to go well til for
whatever reason, the server did an Internal Server 500 error. I went back to the custom fields list on BMO and the new field is in fact there but the ISE has me concerned. Can someone with log access see what the error was exactly around the 1:30 AM EDT time range? It may not be a problem anyway but it may be a good idea to see what the error was. 

Time range: Monday June 6 ~1:30AM EDT 

Thanks dkl
(Assignee)

Updated

7 years ago
Assignee: server-ops → dgherman
(Assignee)

Comment 1

7 years ago
David,
I looked at the error logs but I couldn't find anything in that time range out of the regular messages.
I can send you via email the access and error logs for that hour if you'd like to have a look also.
(Reporter)

Comment 2

7 years ago
Thats fine. We will let it go for now and try again on the next field we need created.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.