Last modified: 2014-09-23 15:40:23 UTC
$ foreachwiki extensions/GlobalCssJs/removeOldManualUserPages.php --user=*** > ~/globalcssjs.log ... ... The MediaWiki script file "/usr/local/apache/common-local/php-1.24wmf15/extensions/GlobalCssJs/removeOldManualUserPages.php" does not exist. ... ...
Should foreachwiki really skip wikitech (labswiki)? foreachwiki is a wrapper for `foreachwikiindblist all.dblist` and labswiki certainly needs to be in all.dblist for multiversion to work there. We added it to fishbowl.dblist to make CentralAuth and other things happier. Was this particular error caused mostly by wikitech being on a lagged wmf branch? If so that is expected to change in the near future but was needed in the near term so we can avoid breaking the old wikitech deploy while we work through config issues with the new het deploy setup on a separate vhost.
From tin (et al), they can't actually access the wikitech database (currently at least), so in the current state, running scripts against it from tin is pointless. Caught exception DBConnectionError: DB connection error: Can't connect to MySQL server on '208.80.154.18' (4) (208.80.154.18) Is this really major? IIRC it'll just skip the wiki and carry on, so it's not a great inconvience
Reducing severity per Reedy.
> Is this really major? IIRC it'll just skip the wiki and carry on, so it's not a great inconvience foreachwikiindblist does not have set -e, so it will continue on command failure. > From tin (et al), they can't actually access the wikitech database (currently at > least), so in the current state, running scripts against it from tin is pointless. Reedy, that should probably be a bug report :)
(In reply to Antoine "hashar" Musso from comment #4) > > From tin (et al), they can't actually access the wikitech database (currently at > > least), so in the current state, running scripts against it from tin is pointless. > > Reedy, that should probably be a bug report :) It's sort of desired behaviour as things stand...