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

VERIFIED FIXED

Status

Infrastructure & Operations
WebOps: Other
--
critical
VERIFIED FIXED
8 years ago
5 years ago

People

(Reporter: jsocol, Assigned: fox2mike)

Tracking

Details

(Reporter)

Description

8 years ago
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.

Updated

8 years ago
Assignee: server-ops → jeremy.orem+bugs
(Reporter)

Comment 1

8 years ago
We're seeing a very high rate of errors from this. Upping priority.
Severity: major → critical

Updated

8 years ago
Assignee: jeremy.orem+bugs → server-ops
(Assignee)

Updated

8 years ago
Assignee: server-ops → shyam
(Assignee)

Comment 2

8 years ago
Done.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Comment 3

8 years ago
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
You need to log in before you can comment on or make changes to this bug.