662592 - fix developer-stage9 settings_local.py EMAIL_BACKEND

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Luke Crouch [:groovecoder]]

blocking QA. we need to add the following to developer-stage9:

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'

(See kuma-stage settings_local.py for example)

Comment 1

[Jake Maul [:jakem]]

Completed.

Comment 2

[raymond [:retornam] (inactive)]

Luke I did not the get the email when you flagged the demo so i'm re-opening this bug so you can investigate

Comment 3

[Jake Maul [:jakem]]

Reassigning to Luke, then. :)

Comment 4

[Luke Crouch [:groovecoder]]

(In reply to comment #3)
> Reassigning to Luke, then. :)

Jake, can you check the latest /var/log/httpd/devmo.dekiwiki.mozilla.org/error_log on sm-devmostage02? I don't have access to the logs. (Should I?)

Comment 5

[Jake Maul [:jakem]]

The only error in the current error_log, repeated over and over with a few different client IPs, is this:

[Tue Jun 07 12:40:59 2011] [error] [client 10.2.10.207] Target WSGI script not found or unable to stat: /data/www/django/developer.mozilla.org

Comment 6

[Luke Crouch [:groovecoder]]

(In reply to comment #5)
> The only error in the current error_log, repeated over and over with a few
> different client IPs, is this:
> 
> [Tue Jun 07 12:40:59 2011] [error] [client 10.2.10.207] Target WSGI script not
> found or unable to stat: /data/www/django/developer.mozilla.org

That's from the error log for stage9? not production nor kuma nor the old stage logs?

Comment 7

[Luke Crouch [:groovecoder]]

Also, is there an SMTP server accessible to stage9? it's trying to use django defaults:

https://docs.djangoproject.com/en/1.2/ref/settings/#email-host

Comment 8

[Jake Maul [:jakem]]

Correct. It is from /var/log/httpd/devmo.dekiwiki.mozilla.org/error_log_2011-06-07-19, which is what developer-stage9 logs to (for some odd reason).

Comment 9

[Jake Maul [:jakem]]

Yes, 'localhost' works properly. I was able to send a test message from there to my @mozilla.com account.

Comment 10

[Luke Crouch [:groovecoder]]

(In reply to comment #9)
> Yes, 'localhost' works properly. I was able to send a test message from there
> to my @mozilla.com account.
Hmm ... then I wonder if we need to restart apache to pick up new settings_local.py?

Comment 11

[Jake Maul [:jakem]]

Apache should not need to be restarted- we touch the .wsgi file, and that should generally be all that's needed to get it to reread the config. However, I've restarted it anyway for you.

Comment 12

[Luke Crouch [:groovecoder]]

changed the way FLAG_NOTIFICATIONS work which should fix this, and added search box to profile admin page to make it easier to set the content flagging email for a user.

raymond, make sure there's an email address on the user record, and make sure the 'content flagging email' field is checked on the user profile record. you should be able to set both with the admin interface.