Page MenuHomePhabricator

Is LocalisationUpdate running every day
Closed, InvalidPublic

Description

Author: Gerard.meijssen

Description:
We have a complaint that the LocalisationUpdate update process is not running daily.. Has the cronjob been setup.. the documentation does not say so.. Are there updates in the files ?

please check this out and let us know
Thanks,

Gerard

Version: unspecified
Severity: enhancement

Details

Reference
bz21260

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:53 PM
bzimport added a project: Deployments.
bzimport set Reference to bz21260.
bzimport added a subscriber: Unknown Object (MLST).

This is a very poor report. It does not contain *any* specifics, and should be maked as FUD/INVALID. Please provide *where* the documentation does not say there is a cron job, please provide details on "a complaint". If this information isn't provided in a timely fashion, this issue should be closed.

According to the documentation, the cron job /is/ set up and runs every 24 hours. The master update script runs on hume at 2 AM GMT, and the individual Apaches pull these updates at 3 AM GMT.

http://wikitech.wikimedia.org/view/LocalisationUpdate#Where_it_runs

Closing as INVALID; any problems with LU should be filed as separate bugs outlining the actual problem, not your theory of what the cause may be.

Gerard.meijssen wrote:

A few lines below it it says: "

Batch frequency

  • not yet set up; planned daily?

Happy to learn that it actually runs .. What is the value of this comment ... This is where I expected to find that it ran.

(In reply to comment #3)

A few lines below it it says: "

Batch frequency

  • not yet set up; planned daily?

Happy to learn that it actually runs .. What is the value of this comment ...
This is where I expected to find that it ran.

If in one place it says "planned daily?" and another place lists the *times* at which it runs, I think it's very likely the latter is correct and someone simply forgot to update/remove the former. Someone can check this, of course, but it makes very little sense for someone to say they've set up two cronjobs mentioning the times while they really didn't do it.