Not receiving Django traceback emails for 500 Internal Server Errors

RESOLVED INVALID

Status

Websites
webifyme.org
--
critical
RESOLVED INVALID
7 years ago
7 years ago

People

(Reporter: stephend, Unassigned)

Tracking

unspecified

Details

(URL)

(Reporter)

Description

7 years ago
Even though I was added to the ADMINS array for both staging servers for Webify Me (bug 655839), I'm still not getting Django tracebacks emailed to me (see the traceback-triggering URLs in bug 656754), for example.

Updated

7 years ago
Assignee: nobody → jbresnik
(Reporter)

Updated

7 years ago
Blocks: 655839

Comment 2

7 years ago
I don't know if assigning this to brez without Repro steps is helpful.

I see three ways forward:
1) Document how to repro a 500
2) Assign to Ops to debug why emails aren't sent
3) Dev can commit a new broken url that always has an exception to test this

/b0rk3n

def b0rk3n(request):
    doh

http://webifyme-dev/en-US/b0rk3n

@stephen - What do you think is the most promising next step?
Assignee: jbresnik → stephen.donner
(Reporter)

Comment 3

7 years ago
(In reply to comment #2)
> I don't know if assigning this to brez without Repro steps is helpful.

Repro steps are in bug 656754, but here they are again, for clarity:

https://webifyme-dev.allizom.org/quiz/
https://webifyme-dev.allizom.org/features/
https://webifyme-dev.allizom.org/collage/e2c5ffc9c060/

(it appears the whole site is bombing out)
 
> I see three ways forward:
> 1) Document how to repro a 500

Again, we have clear example on dev/staging -- do you mean locally, then?  I agree, this is probably an environment issue.

> 2) Assign to Ops to debug why emails aren't sent

As I mentioned in comment 0, bug 655839 was closed, and should be working, as it is with other projects, just fine (Spark, for example).  Maybe this portends a problem with auto-updates, or something?

> 3) Dev can commit a new broken url that always has an exception to test this

This would help locally, but we already have plenty of examples on https://webifyme-dev.allizom.org -- can we start there?

In thinking about this a little more, though, this is actually a good idea -- would be nice to have a special URL to ensure that tracebacks are always working.

 
> /b0rk3n
> 
> def b0rk3n(request):
>     doh
> 
> http://webifyme-dev/en-US/b0rk3n
> 
> @stephen - What do you think is the most promising next step?

Not sure -- maybe start with Jabba ensuring the ADMINS array is there, still, and auto-updating is on, and not clobbering it?  Don't know if that's code or config change.

As there's nothing further for me to do here, un-assigning and re-assigning to nobody.
Assignee: stephen.donner → nobody

Comment 4

7 years ago
Previously this was an issue with missing 404 template (the 500 error was that the template wasn't available, not an exception in the code itself, i.e. no stack trace) i.e. are we sure this is still a problem?
(Reporter)

Comment 5

7 years ago
(In reply to comment #4)
> Previously this was an issue with missing 404 template (the 500 error was
> that the template wasn't available, not an exception in the code itself,
> i.e. no stack trace) i.e. are we sure this is still a problem?

Yeah, I haven't seen any problems with missing tracebacks.  Webify Me isn't auto-updating, though, as far as I can tell.

Comment 6

7 years ago
Ok I'm gonna close this as invalid then - I'd say open a new ticket if there's issues with auto updating, I (TBG in general) don't have access to it.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.