Closed Bug 375283 Opened 17 years ago Closed 17 years ago

Enable cron job for updating AMO v3 download counts

Categories

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

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: morgamic, Assigned: oremj)

References

Details

We will need to set up a cron job to update download counts for AMO v3 once we know things will be okay during peak load times -- Monday, Tuesday?

The cron job is much like v2 except it has been modified to use the new schema.  The script is in ./bin/maintenance.php, and has weekly and total count options.

See the current v2 cron job, change the path, and that should be it.
Blocks: 375278
Assignee: server-ops → justdave
This can replace the v2 cron job, or do we still need that one for some reason?
I went ahead and replaced the v2 one.  If we need it back, holler.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
v2 one is no longer needed, so this is all we wanted -- did you test the output of the cron job?

Thanks, Dave.
Users are reporting issues -- can you verify output from the command line by running the scheduled cronjobs manually?

I'd also want to double check that garbage collection is working properly and is scheduled -- there should be a cron to clean out all downloads older than 8 days.

If we don't schedule this, the size of the downloads table could get out of control.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: justdave → server-ops
Status: REOPENED → NEW
Assignee: server-ops → aravind
Assignee: aravind → oremj
if (!defined('DB_HOST'))
    define('DB_HOST', 'localhost');

That block is not working.  defined is returning 1 but it's still falling into the if block.
Fixed.
Status: NEW → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
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.