Maintenance servers are where we run scheduled and ad-hoc command-line scripts relating to MediaWiki.
As of September 2021, the servers are:
- mwmaint1002, current active maintenance server in eqiad.
- mwmaint2002, this one is passive, to be used if we switch activity to codfw (switchover).
Run a maintenance script on a wiki
When running a long-running maintenance script, consider using screen.
To run a maintenance script, log into the active maintenance server:
Use the mwscript command-line utility:
mwscript scriptname.php --wiki dbname
The above command will run the script scriptname.php located in the
/maintenance directory of the specified wiki's php directory.
You can also use a path relative to the MediaWiki installation, for example to run a script from an extension rather than core. It is recommended that in this case you first change a MediaWiki directory to allow for tab completion:
, change to the directory for the version of MediaWiki that you want to run the maintenance script from (for example php-1.27.0-wmf.23)
$ cd /srv/mediawiki/php-1.xx-someversion/ $ mwscript extensions/MyExtension/maintenance/scriptname.php --wiki dbname
IIt will run the version of the maintenance script in
. If you want to run the version under
/home/wikipedia/common /usr/local/apache/common-local/, or you're on a box without /home mounted, you need to change to /usr/local/apache/common-local/multiversion and run ./MWScript.php instead.
$ mwscript eval.php enwiki > print $wgDBname; enwiki > print $wgVersion; 1.18wmf1 > exit $
If you need to pass parameters to your maintenance script, you can add them to the end. You may also want to explicitly declare the database parameter to avoid confusion:
mwscript scriptname.php --wiki=enwiki --days=1
In this case, the 'wiki' parameter is handled by mwscript and the 'days' parameter is handled by scriptname.php. The "wiki" must be in wikiversions.cdb so the maintenance script machinery can figure out what MediaWiki version it is running.
Many maintenance scripts are used to run heavy database queries; remember to check the replication lag and other possible byproducts.