Closed Bug 592725 Opened 14 years ago Closed 14 years ago

Update django-cache-machine on support.mozilla.com (production)

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jsocol, Assigned: fox2mike)

Details

For some reason, it looks like our virtualenv on production is not using the latest django-cache-machine. There's a really easy fix:

cd /data/virtualenvs/kitsune/src/django-cache-machine/
git pull origin master
find . -name "*.pyc" -exec rm -f {} \;

Then restart celery and touch the wsgi/kitsune.wsgi file (or restart apache, whichever you guys usually do). That should bring everything up to date and save us a ton of server errors.
Assignee: server-ops → jeremy.orem+bugs
We're seeing a very high rate of errors from this. Upping priority.
Severity: major → critical
Assignee: jeremy.orem+bugs → server-ops
Assignee: server-ops → shyam
Done.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Thanks, Shyam!
Status: RESOLVED → VERIFIED
Woo, I look forward to fewer stack traces!
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.