Last modified: 2014-09-23 15:40:23 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T72311, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70311 - [Regression] foreachwiki should not run on labswiki (wikitech.wm.o)
[Regression] foreachwiki should not run on labswiki (wikitech.wm.o)
Status: NEW
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
wmf-deployment
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: code-update-regression
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-02 23:19 UTC by Krinkle
Modified: 2014-09-23 15:40 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2014-09-02 23:19:10 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.
...
...
Comment 1 Bryan Davis 2014-09-02 23:34:34 UTC
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.
Comment 2 Sam Reed (reedy) 2014-09-03 01:38:10 UTC
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
Comment 3 Greg Grossmeier 2014-09-22 21:52:10 UTC
Reducing severity per Reedy.
Comment 4 Antoine "hashar" Musso (WMF) 2014-09-23 14:15:59 UTC
> 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 :)
Comment 5 Sam Reed (reedy) 2014-09-23 15:40:23 UTC
(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...

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links