Closed Bug 649015 Opened 13 years ago Closed 13 years ago

stage, prod Add lcrouch, lorchard AT mozilla DOT com to various MDN admin emails

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ozten, Assigned: jabba)

Details

Attachments

(1 file)

The admin emails are out of date for various MDN cron / servers.

For stage and production, please remove 
* aking
* fwenzel

Please add or confirm the following are in the admin list:
* lcrouch
* lorchard

All users above are username@mozilla.com.
Removed aking@ from cron-mdn@m.c. fwenzel was removed in a previous ticket. I don't see any other mozilla.com lists for MDN. Kicking this over to desktop-support to verify if there are any mailman (or other) lists that might need updated.
Assignee: server-ops → desktop-support
Component: Server Operations → Server Operations: Desktop Issues
There's a dev-mdn@lists.mozilla.org list - wherever and however that is managed.
lcrouch and lorchard were already added to cron-mdn@mozilla.com
Assignee: desktop-support → shui
Did you need them added to dev-mdn@lists.mozilla.org aswell?
did you want a news group aswell?
Assignee: shui → desktop-support
Lcrouch and lorchard have been added to admin for dev-mdn.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Attached file Still receiving emails
I'm still receiving exception emails. Source attached.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I'm still receiving app stack trace emails such as
"[Django] Error (EXTERNAL IP): /en-US/"
Likewise. One of the MDN instances still seems to have Austin and me as ADMINS. Please replace that too. From the paths etc, it looks like it might be the production instance of MDN.
(In reply to comment #9)
> Likewise. One of the MDN instances still seems to have Austin and me as ADMINS.
> Please replace that too. From the paths etc, it looks like it might be the
> production instance of MDN.

At least
sm-devmostage02:/data/www/django/developer.mozilla.org/mdn/settings_local.py
and
sm-devmostage02:/data/www/django/kuma-stage.mozilla.org/kuma/settings_local.py

Need to remove Fred and Austin from ADMINS

Probably from production servers' settings_local.py also.
The 2 files Luke pointed out are fixed on mradm02, and with auto-updates back on it should be live in 10 minutes or less. Due to a timing issue between mradm02 and sm-devmostage02 (working on it), the 5-minute updates could actually take 10 minutes to propagate.
I have also fixed settings_local.py in this file:

mradm02:/data/dekiwiki_python/src/developer.mozilla.org/mdn/settings_local.py

It will go out with the next prod push... unless we'd like to do that sooner? I believe this bug is otherwise completed.
Following people have been removed,
* aking
* fwenzel

Following people have been added.
* lcrouch
* lorchard

Moving over to service ops.
Assignee: desktop-support → server-ops
Component: Server Operations: Desktop Issues → Server Operations
Anything more to do here? Change is integrated and ready to go, will be made live next push (everything but ADMINS for prod mdn is done).
I went ahead and mode just this change to the sync_dir for the mdn app, so that it would get pushed out to the webheads now. That change will of course be overwritten during, the next push, but jakem made the change in the src dir, too, so that won't be an issue.
Assignee: server-ops → jdow
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
I'm receiving this cronmail:
Subject: Cron <root@mradm02> /data/devmostage/stage_update > /dev/null

Body: http://pastebin.mozilla.org/1217623
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
As well as
Subject: Cron <apache@mradm02> cd /data/devmostage/src/kuma-stage.mozilla.org/kuma; python26 manage.py cron mdc_pages > /dev/null

Body:
Traceback (most recent call last):
  File "manage.py", line 51, in <module>
    execute_manager(settings)
  File "/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/vendor/src/django/django/core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/vendor/src/django/django/core/management/__init__.py", line 379, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/vendor/src/django/django/core/management/base.py", line 191, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/vendor/src/django/django/core/management/base.py", line 220, in execute
    output = self.handle(*args, **options)
  File "/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/vendor/src/django-cronjobs/cronjobs/management/commands/cron.py", line 38, in handle
    registered[script](*args)
  File "/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/apps/docs/cron.py", line 68, in mdc_pages
    json.dump(pages, open(outputfile, 'w'))
IOError: [Errno 13] Permission denied: '/data/dekiwiki-stage/src/kuma-stage.mozilla.org/kuma/lib/mdc_pages/popular.json'
Looks like you were still in the cron-mdn@mozilla.com list. Sorry we missed that. Fixed now.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: