Closed
Bug 761607
Opened 12 years ago
Closed 12 years ago
May 2012 Report Reminder Emails never sent out
Categories
(Mozilla Reps Graveyard :: reps.mozilla.org, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kinger, Assigned: giorgos)
Details
I have not received the May 2012 Report Reminder Email.
Assignee | ||
Updated•12 years ago
|
Group: mozilla-reps-admins
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → giorgos
Status: NEW → ASSIGNED
Comment 1•12 years ago
|
||
same here!
Comment 2•12 years ago
|
||
Hey same here, I also did not get the May 2012 Report Reminder Email.
Comment 3•12 years ago
|
||
same here, i did not receive the report reminder of May2012
Assignee | ||
Comment 4•12 years ago
|
||
Jason, Could you please check the output of ./manage.py send_first_report_notification on production? The first day of each month, but that didn't work on June. Thanks!
Assignee: giorgos → jcrowe
Comment 5•12 years ago
|
||
Removed cron redirect for the run on the 8th to hopefully get debug information. Giorgos over IRC says he may build a test or --noop for these commands as we cannot run them to test due to sending multiple reminders and such. No action can be taken till either we get some information from cron or the testing commands.
Assignee: jcrowe → server-ops
Component: reps.mozilla.org → Server Operations: Web Operations
Product: Mozilla Reps → mozilla.org
QA Contact: reps-mozilla-org → cshields
Version: unspecified → other
Updated•12 years ago
|
Whiteboard: [06/08 check cronmail]
Assignee | ||
Comment 6•12 years ago
|
||
I filed bug 762408 about implementing --noop flag for the commands. It won't land before tomorrow though so we'll check cron's output first.
Updated•12 years ago
|
Assignee: server-ops → jcrowe
Comment 7•12 years ago
|
||
Giorgos, Did this work last evening? I did not get any cron error emails so I have nothing to go on really. If it did not work we will need to investigate more in-depth troubleshooting methods.
Comment 8•12 years ago
|
||
Giorgos, I lied to you, turns out my filter was not configured correctly. Here is the output from last nights cron run: manage.py send_second_report_notification /data/engagement/src/reps.mozilla.org/remo/vendor/lib/python/celery/loaders/default.py:53: NotConfigured: No celeryconfig.py module found! Please make sure it exists and is available to Python. NotConfigured) Traceback (most recent call last): File "/data/engagement/src/reps.mozilla.org/remo/manage.py", line 27, in <module> manage.main() File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/funfactory/funfactory/manage.py", line 139, in main execute_manager(current_settings) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/core/management/__init__.py", line 438, in execute_manager utility.execute() File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/core/management/__init__.py", line 379, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/core/management/base.py", line 191, in run_from_argv self.execute(*args, **options.__dict__) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/core/management/base.py", line 220, in execute output = self.handle(*args, **options) File "/data/engagement/src/reps.mozilla.org/remo/remo/reports/management/commands/send_second_report_notification.py", line 36, in handle send_remo_mail(reps_without_report, subject, self.EMAIL_TEMPLATE, data) File "/data/engagement/src/reps.mozilla.org/remo/vendor/lib/python/celery/task/base.py", line 248, in __call__ return self.run(*args, **kwargs) File "/data/engagement/src/reps.mozilla.org/remo/vendor/lib/python/celery/decorators.py", line 52, in run return fun(*args, **kwargs) File "/data/engagement/src/reps.mozilla.org/remo/remo/reports/tasks.py", line 20, in send_remo_mail message = render_to_string(email_template, ctx_data) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/template/loader.py", line 181, in render_to_string t = get_template(template_name) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/template/loader.py", line 157, in get_template template, origin = find_template(template_name) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/template/loader.py", line 134, in find_template source, display_name = loader(name, dirs) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/template/loader.py", line 42, in __call__ return self.load_template(template_name, template_dirs) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/jingo/jingo/__init__.py", line 178, in load_template template = env.get_template(template_name) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/jingo/jingo/__init__.py", line 28, in get_template load_helpers() File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/jingo/jingo/__init__.py", line 123, in load_helpers import_module('%s.helpers' % app) File "/data/engagement/src/reps.mozilla.org/remo/vendor/src/django/django/utils/importlib.py", line 35, in import_module __import__(name) File "/data/engagement/src/reps.mozilla.org/remo/remo/base/helpers.py", line 13, in <module> from Crypto.Cipher import AES ImportError: No module named Crypto.Cipher
Assignee | ||
Comment 9•12 years ago
|
||
Jason, I believe that's related to bug 748688. Can you please install pycrypto to the celery servers as well? Thanks for looking into this!
Comment 10•12 years ago
|
||
Giorgos, I installed this on the admin node (as that is where this cron job runs and is failing). Can I run this command manually to see if it is working now?
Assignee | ||
Comment 11•12 years ago
|
||
Sure, you can try running ./manage.py send_second_report_notification
Comment 12•12 years ago
|
||
Giorgos, It ran this time without errors (well with normal errors): manage.py send_second_report_notification /data/engagement/src/reps.mozilla.org/remo/vendor/lib/python/celery/loaders/default.py:53: NotConfigured: No celeryconfig.py module found! Please make sure it exists and is available to Python. NotConfigured) Can you confirm that something happened from this (mail was sent?). Regards
Comment 13•12 years ago
|
||
I have just received a mail: [Reminder] Please file your Mozilla Reps monthly report for May Seems like its working now.
Assignee | ||
Comment 14•12 years ago
|
||
Jason, it works again! ;) Thanks!
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 15•12 years ago
|
||
I received the email on Friday.
Comment 16•12 years ago
|
||
I did receive too, its definitely working.
Comment 17•12 years ago
|
||
I have not yet received it
Assignee | ||
Comment 18•12 years ago
|
||
Can you please check your SPAM folder? The email was sent, meaning that the command was executed successfully.
Assignee | ||
Comment 19•12 years ago
|
||
Not in spam folder. Re-opening to track bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 20•12 years ago
|
||
Giorgos, No idea what you want me to do here. If I understand correctly from comment 18 everything worked correctly from the server side. If this is the case I will need to know what you need form me in terms of work. Regards
Assignee | ||
Comment 21•12 years ago
|
||
Jason, I'll re-assign the bug to me until I find out how we can track and solve the problem. Sorry for the confusion. Thanks!
Assignee: jcrowe → giorgos
Component: Server Operations: Web Operations → reps.mozilla.org
Product: mozilla.org → Mozilla Reps
QA Contact: cshields
Version: other → unspecified
Assignee | ||
Updated•12 years ago
|
Whiteboard: [06/08 check cronmail]
Assignee | ||
Comment 22•12 years ago
|
||
Seems to work OK for a few months now. Closing
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 23•11 years ago
|
||
Verifying since no new reports for a few months.
Status: RESOLVED → VERIFIED
Updated•4 years ago
|
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•