Closed Bug 438832 Opened 16 years ago Closed 16 years ago

Have AMO maintenance scripts run on preview

Categories

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

All
Other
task
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wenzel, Assigned: reed)

References

()

Details

A few times now, Stephen had trouble verifying bugs on preview.AMO because the database was out of sync due to maintenance tasks not being run like they are in production.

Can we either trigger them as a cron job just like on prod, or maybe add them to the svn up script, whatever is more convenient?

Also, not all of them may be needed. The ones I am specfically asking about are "maintenance.php reviews" and "... ratings".

Thanks.
Blocks: 436810
Assignee: server-ops → reed
I just cloned the maintenance cron to run the same things on preview that run on production AMO.

Reopen if this is a problem.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Sorry, I need to reopen: The review count seems to be off, leading me to believe the "reviews" and "ratings" cron jobs are not being run. Can you double-check please if they are running?

Also, when preview is auto-svn-upped, does that include the bin folder outside the docroot? If not could you make that happen? If the maintenance scripts are not current that could also be a reason for them miscounting.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #2)
> Sorry, I need to reopen: The review count seems to be off, leading me to
> believe the "reviews" and "ratings" cron jobs are not being run. Can you
> double-check please if they are running?

The cron (for both production and staging) was running on a RHEL4 server. Since the mysql5 changeover, it looks like the maintenance scripts have been unable to run. I've moved the cronjob to a RHEL5 server, and it seems to be working fine now.
Status: REOPENED → RESOLVED
Closed: 16 years ago16 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.