Jump to content

Help talk:MediaWiki-Vagrant in Cloud VPS

Rendered with Parsoid
From Wikitech
Latest comment: 1 year ago by BryanDavis in topic Update sizes


Thanks for this help page! Worked smoothly:

==> default: Notice: Finished catalog run in 494.92 seconds

I got this, easily resolved by running setup.sh with my user:

Path: /srv/mediawiki-vagrant/Vagrantfile
Line number: 40
Message: RuntimeError: The mediawiki-vagrant plugin hasn't been installed yet. Please run `setup.sh`.

The wiki is working, however I can't ssh into it.

$ vagrant ssh
The provider 'lxc' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.

--Nemo 17:44, 11 September 2015 (UTC)Reply

I don't know what happened, but now it works. :o (I did many MediaWiki configuration changes and run "vagrant provision" a few times, but I don't know how that could matter.) --Nemo 20:07, 12 September 2015 (UTC)Reply
Thanks for . The last time I tried to follow the documentation, I got stuck as I couldn't find the "configure" link any longer. Nemo 12:30, 28 January 2017 (UTC)Reply
For what it's worth, I had this same issue which was resolved when I stopped trying to run vagrant under screen, and instead just ran it directly from shell that I logged in with. maximilianklein (talk) 17:50, 24 March 2019 (UTC)Reply

No usable default provider

After running setup.sh manually and trying to run 'vagrant up' I got this:

$ vagrant up
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.

--brion (talk) 18:51, 3 November 2015 (UTC)Reply

Ok this may be due to not having loaded the profile magic that sets the user properly? After a reboot I got different errors (permissions-related on .vagrant dir), presumably because I ran ./setup.sh as myself. After manually chown -R'ing .vagrant to mwvagrant, it seems to be loading up happier. --brion (talk) 18:56, 3 November 2015 (UTC)Reply

Yeah, this happens when the alias from vagrant to /usr/local/bin/mwvagrant is not set - either because you skip the (now) bolded setup step of logging out and back or you are not in a login shell. Filed T195592 about that. --tgr (talk) 14:48, 25 May 2018 (UTC)Reply


The 5th step "Log out and log back in to pick up profile.d alias..." could use some info on what is going on/needed from the user. I figured out that what is meant is /etc/profile.d but it is unclear if the user has to do anything else or if the rest of the info is just an explanation for why you have to log out once. If the latter is the case then simple sticking a bracket around everything after "log back in" should make this clearer. /Lokal_Profil (talk) 00:47, 12 January 2017 (UTC)Reply

Yes Done, but feel free to tweak the wording if it is still unclear. --BryanDavis (talk) 16:37, 12 January 2017 (UTC)Reply

Got issues

I've been having some issues getting a testing instance set up. All I need is mw-vagrant with the restbase role enabled. First try went the best: initial 'vagrant up' provisioning went fine and I only ran into trouble when vagrant wouldn't shut down to reboot after enabling the restbase role and doing 'vagrant provision'. The vm ended up in some kind of basically hosed state after that and I decided to just nuke the instance and start over.

Since then, I've tried bringing up a few fresh instances and the initial 'vagrant up' fails each time with:

 NFS requires a host-only network to be created.
 Please add a host-only network to the machine (with either DHCP or a
 static IP) for NFS to work.

This is something the puppet config should be handling, right? I want to go through puppet and Do Things Right so I'm resisting the urge to hack around stuff and/or just install MW & RB manually. Mholloway (talk) 15:53, 4 February 2017 (UTC)Reply

Improving content design

Leaving this here as a placeholder phab:T245083. Would like to improve the content design of this page. SRodlund (talk) 00:20, 13 February 2020 (UTC)Reply

Update sizes

The documentation here refers to m1.medium etc. but these names appear to not be used anymore. The screenshots will also need updating. Esanders (talk) 12:29, 14 March 2021 (UTC)Reply

Yeah, I just noticed the same thing. I assume m1.small should now be g3.cores2.ram4.disk20? RoySmith (talk) 14:44, 28 June 2022 (UTC)Reply
  • m1.small -> g3.cores1.ram2.disk20
  • m1.medium -> g3.cores2.ram4.disk20
-- BryanDavis (talk) 15:32, 28 June 2022 (UTC)Reply

Ruby permissions error (and solution)

When trying to call vagrant up I got the error:

/srv/mediawiki-vagrant/lib/mediawiki-vagrant/environment.rb:306:in `initialize': Permission denied @ rb_sysopen - /srv/mediawiki-vagrant/puppet/hieradata/vagrant-managed.yaml (Errno::EACCES)

Doing sudo chown -R mwvagrant /srv/mediawiki-vagrant/puppet/hieradata/ fixed it.

Not sure how to fold this into existing documents, as I'm not sure how common this is but wanted to record this in case anyone ran into the same issue. jdlrobson (talk) 21:31, 27 May 2022 (UTC)Reply