Last modified: 2014-05-10 06:59:37 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 T51944, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49944 - vagrant up: SSH command responded with a non-zero exit status
vagrant up: SSH command responded with a non-zero exit status
Status: RESOLVED INVALID
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
PC Windows 8
: Normal normal
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-21 07:28 UTC by Robert Vogel
Modified: 2014-05-10 06:59 UTC (History)
6 users (show)

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


Attachments
Full log of "vagrant up" execution (64.90 KB, application/octet-stream)
2013-06-21 07:28 UTC, Robert Vogel
Details

Description Robert Vogel 2013-06-21 07:28:49 UTC
Created attachment 12600 [details]
Full log of "vagrant up" execution

I tried to set up a WikiData development environment using Vagrant. At first everything seemed to be okay. The "precise64" VM was downloaded and the automated setup with "puppet" started. But then after Apache, MySQL and PHP were installed the following error occurred:

---------------------------------------------------------------
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && puppet apply --verbose --debug --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' base.pp --detailed-exitcodes || [ $? -eq 2 ]
---------------------------------------------------------------

There were two errors reported in the script output before it stopped:

---------------------------------------------------------------
[1;35merr: /Stage[main]/Wikidata::Client/Exec[populateSitesTable2]/returns: change from notrun to 0 failed: MW_INSTALL_PATH=/srv/client /usr/bin/php /srv/extensions/Wikibase/lib/maintenance/populateSitesTable.php returned 1 instead of one of [0] at /tmp/vagrant-puppet/modules-0/wikidata/manifests/init.pp:179[0m

[1;35merr: /Stage[main]/Wikidata::Client/Exec[client_update]/returns: change from notrun to 0 failed: /usr/bin/php /srv/client/maintenance/update.php --quick --conf '/srv/orig-client/LocalSettings.php' returned 1 instead of one of [0] at /tmp/vagrant-puppet/modules-0/wikidata/manifests/init.pp:143[0m
---------------------------------------------------------------

Afterwards some "warnings" about "Skipping because of failed dependencies" showed up. See attached log file for details.

I'm using VirtualBox 4.2.12 and Vagrant 1.2.2.
Comment 1 Ori Livneh 2013-06-21 17:35:15 UTC
(In reply to comment #0)
> I tried to set up a WikiData development environment using Vagrant.

Robert, can you specify which Vagrant configuration you are using? Is it https://github.com/SilkeMeyer/wikidata-vagrant ?
Comment 2 Robert Vogel 2013-06-23 14:54:45 UTC
(In reply to comment #1)
> Robert, can you specify which Vagrant configuration you are using? Is it
> https://github.com/SilkeMeyer/wikidata-vagrant ?

Yes, I can confirm the repo. I followed the instructions in README.md. Last attempt/clone was on 2013-06-21
Comment 3 Andre Klapper 2013-09-11 22:45:34 UTC
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]
Comment 4 Bryan Davis 2014-05-10 06:59:37 UTC
MediaWiki-Vagrant currently don't have a Wikidata::Client puppet class, so this is unreproducible.

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


Navigation
Links