Lost databases

Adil Shahzad

unread,

Jun 30, 2019, 3:49:38 AM6/30/19

to Vagrant

Hi everyone!

I recently upgraded my VAGRANT to 2.2.5 version and I've the attached boxes. I was running scotchbox 3.0 and decided to add the latest box 3.5, as soon as I added 3.5 I lost my DB's and can't find them. I can see my previous scotch and I've the screen shot attached. I'm not sure how to revert back to that version and may be if i can get my db's back? Any help will be much appreciated.

Kind regards,

Adil

vagrant-boxes.png

Alvaro Miranda Aguilera

unread,

Jun 30, 2019, 10:49:13 AM6/30/19

to vagra...@googlegroups.com

hello

Are 2 separate things here.

Templates and running VMs.

Templates or vagrant boxes is from where a running VM will be created.

vagrant box list

will show vagrant boxes or templates.

A total separate thing is running VMs.

vagrant global-status

this will display the running VMs and the directory from where it got started.

If you upgrade a base box, and you want to upgrade the running VM, please be aware that the process involve manually running the commands.

vagrant destroy

vagrant up

If you haven't run vagrant destroy, then the running VM should be listed in the output of

vagrant global-status

from there you could do

vagrant ssh <id>

and connect to the VM.

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/afe7aa62-0730-4add-8b37-305b72acd436%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

Adil Shahzad

unread,

Jul 1, 2019, 4:01:06 AM7/1/19

to Vagrant

Hi & Thanks Alvaro, when I run the vagrant box list

I can see below boxes

$ vagrant box list

laravel/homestead (virtualbox, 0.2.7)

laravel/homestead (virtualbox, 0.3.0)

laravel/homestead (virtualbox, 0.4.2)

scotch/box (virtualbox, 3.0)

scotch/box (virtualbox, 3.5)

$ vagrant global-status

id name provider state directory

------------------------------------------------------------------------

0376f86 default virtualbox running F:/october-demo

As you can see above the server id 0376f86 is the same server which is scotch/box (virtualbox, 3.5) and I'm not sure how to switch to scotch/box (virtualbox, 3.0)

My vagrant up out is as follow

$ vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Checking if box 'scotch/box' version '3.5' is up to date...

==> default: Clearing any previously set forwarded ports...

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

default: Adapter 1: nat

default: Adapter 2: hostonly

==> default: Forwarding ports...

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM...

==> default: Waiting for machine to boot. This may take a few minutes...

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

default: Warning: Connection reset. Retrying...

default: Warning: Connection aborted. Retrying...

==> default: Machine booted and ready!

==> default: Checking for guest additions in VM...

default: The guest additions on this VM do not match the installed version of

default: VirtualBox! In most cases this is fine, but in rare cases it can

default: prevent things such as shared folders from working properly. If you see

default: shared folder errors, please make sure the guest additions within the

default: virtual machine match the version of VirtualBox you have installed on

default: your host and reload your VM.

default:

default: Guest Additions Version: 5.1.21

default: VirtualBox Version: 5.2

==> default: Setting hostname...

==> default: Configuring and enabling network interfaces...

==> default: Mounting shared folders...

default: /var/www => F:/october-demo

==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`

==> default: flag to force provisioning. Provisioners marked to run always will still run.

Let me know if it makes any sense and you can help further.

Kind regards,

Adil

To unsubscribe from this group and stop receiving emails from it, send an email to vagra...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/afe7aa62-0730-4add-8b37-305b72acd436%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Alvaro

Alvaro Miranda Aguilera

unread,

Jul 1, 2019, 12:56:00 PM7/1/19

to vagra...@googlegroups.com

Hello.

If vagrant global-status doesn't show a running box with 3.0 I am not sure if you have any other VM running.

You could check in VirtualBox GUI to confirm.

To ensure a new VM is created using a particular version, you can update Vagrantfile to have

  config.vm.box = "scotch/box"
  config.vm.box_version = "3.0"

and a new VM will be created with that version of the box.

vagrant doesn't create or destroy boxes on his own, you create boxes when you run vagrant up, you destroy boxes doing vagrant destroy

a running version, ie 3.0 it won't get upgraded to 3.5 without the instance being deleted and created again.

Hope you can find more information on what happened here.

Good luck.

Alvaro

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/e90db7b0-b5bb-48c1-a382-9881d6d5f0be%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

Adil Shahzad

unread,

Jul 2, 2019, 1:51:26 AM7/2/19

to Vagrant

Hi,

Thank you once again, I don't have any other VM running and I also tried to update the vagrant file by specifying the version for each box but when I ssh I can't see my old databases. Below is my vagrant file, you can see I indicated to run ver 3.0

# -*- mode: ruby -*-
# vi: set ft=ruby :


Vagrant.configure("2") do |config|


    
    config.vm.box = "scotch/box"
    config.vm.box_version = "3.0"


    config.vm.network "private_network", ip: "192.168.33.10"
    config.vm.hostname = "scotchbox"


    # config.vm.synced_folder ".", "/var/www", :mount_options => ["dmode=777", "fmode=666"]
    # config.vm.synced_folder ".", "/var/www", nfs: true, :mount_options => ['nolock,vers=3,udp,noatime,actimeo=1']


    # Optional NFS. Make sure to remove other synced_folder line too
    config.vm.synced_folder ".", "/var/www", :nfs => { :mount_options => ["dmode=777","fmode=666"] }

and here is the log after vagrant up and it shows version 3.5 :(

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'scotch/box' version '3.5' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...

==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 5.1.21
    default: VirtualBox Version: 5.2
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /var/www => F:/october-demo
==> default: Machine already provisioned. Run `vagrant provision` or use the `-- provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.

If I try to run Vagarnt Provision I'm getting the below

$ vagrant provision
==> default: Running provisioner: shell...
    default: Running: inline script
    default: Creating directory for site1.local...
    default: Creating vhost config for site1.local...
    default: cp:
    default: cannot stat '/etc/apache2/sites-available/scotchbox.local.conf'
    default: : No such file or directory
    default: Updating vhost config for site1.local...
    default: sed: can't read /etc/apache2/sites-available/site1.local.conf: No such file or directory
    default: sed: can't read /etc/apache2/sites-available/site1.local.conf: No such file or directory
    default: Enabling site1.local. Will probably tell you to restart Apache...
    default: ERROR: Site site1.local does not exist!
    default: So let's restart apache...

Sorry for all the headache.

Kind regards,

Adil

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/e90db7b0-b5bb-48c1-a382-9881d6d5f0be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Alvaro

Reply all

Reply to author

Forward