Closed
Bug 693317
Opened 14 years ago
Closed 14 years ago
Affiliates: cron error
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cmore, Unassigned)
Details
(Whiteboard: [dev] [it])
We are receiving this cron error message:
/bin/sh: /data/engagement-stage/src/affiliates-dev.allizom.org/affiliates-app/manage.py: No such file or directory
| Reporter | ||
Updated•14 years ago
|
Whiteboard: [dev] [it]
| Reporter | ||
Updated•14 years ago
|
Target Milestone: --- → 1.0
Comment 1•14 years ago
|
||
Details: We've been receiving this error for a while, at least a few weeks. It occurs once a day at 12:00 AM.
It's probably related to the cron job that runs at midnight on stage and prod that calls `manage.py update_leaderboard`. I suspect that the path needs to be changed for stage and prod to the appropriate directory.
cshields: Can you confirm whether or not the cron job has the correct path for this command on stage and prod?
Comment 2•14 years ago
|
||
Fixed. engagement-stage / affiliates-dev.allizom.org.
stage does not have -dev in the path.
There was a similar error on prod. Also fixed.
Assignee: nobody → server-ops
Status: NEW → RESOLVED
Closed: 14 years ago
Component: affiliates.mozilla.org → Server Operations: Web Operations
OS: Mac OS X → All
Product: Websites → mozilla.org
QA Contact: affiliates-mozilla-org → cshields
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: 1.0 → ---
Version: unspecified → other
Updated•12 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•