Re: Problema al levantar Vagrant
Claudio,
NFS:
---
hmontero@HP-HMONTERO:~$ sudo aptitude install nfs-kernel-server
[sudo] password for hmontero:
nfs-kernel-server ya está instalado en la versión solicitada (1:1.3.4-2.1)
nfs-kernel-server ya está instalado en la versión solicitada (1:1.3.4-2.1)
No se instalará, actualizará o eliminará ningún paquete.
0 paquetes actualizados, 0 nuevos instalados, 0 para eliminar y 0 sin
actualizar.
Necesito descargar 0 B de ficheros. Después de desempaquetar se usarán 0 B.
hmontero@HP-HMONTERO:~$ ps -fea | grep nfs
root 669 2 0 jun24 ? 00:00:00 [nfsd4_callbacks]
root 677 2 0 jun24 ? 00:00:00 [nfsd]
root 678 2 0 jun24 ? 00:00:00 [nfsd]
root 679 2 0 jun24 ? 00:00:00 [nfsd]
root 680 2 0 jun24 ? 00:00:00 [nfsd]
root 681 2 0 jun24 ? 00:00:00 [nfsd]
root 682 2 0 jun24 ? 00:00:00 [nfsd]
root 683 2 0 jun24 ? 00:00:00 [nfsd]
root 684 2 0 jun24 ? 00:00:00 [nfsd]
hmontero 1320 21566 0 22:23 pts/2 00:00:00 grep --color=auto nfs
---
Comente la linea: #config.vm.synced_folder ".", "/vagrant", type: "nfs"
---
hmontero@HP-HMONTERO:~/Proyectos/portal-laravel$ vagrant up
Bringing machine 'portal-laravel' up with 'virtualbox' provider...
==> portal-laravel: Checking if box 'educar/portal-laravel' is up to date...
==> portal-laravel: Clearing any previously set forwarded ports...
==> portal-laravel: Clearing any previously set network interfaces...
==> portal-laravel: Preparing network interfaces based on configuration...
portal-laravel: Adapter 1: nat
portal-laravel: Adapter 2: hostonly
==> portal-laravel: Forwarding ports...
portal-laravel: 22 (guest) => 2222 (host) (adapter 1)
==> portal-laravel: Running 'pre-boot' VM customizations...
==> portal-laravel: Booting VM...
==> portal-laravel: Waiting for machine to boot. This may take a few minutes...
portal-laravel: SSH address: 127.0.0.1:2222
portal-laravel: SSH username: vagrant
portal-laravel: SSH auth method: private key
==> portal-laravel: Machine booted and ready!
[portal-laravel] GuestAdditions 5.1.22 running --- OK.
==> portal-laravel: Checking for guest additions in VM...
==> portal-laravel: Configuring and enabling network interfaces...
==> portal-laravel: Mounting shared folders...
portal-laravel: /vagrant => /home/hmontero/Proyectos/portal-laravel
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
: Protocol error
---
Buscando el error instale el plugin:
vagrant plugin install vagrant-vbguest
y en la consola muestra:
---
hmontero@HP-HMONTERO:~/Proyectos/portal-laravel$ vagrant up
Bringing machine 'portal-laravel' up with 'virtualbox' provider...
==> portal-laravel: Checking if box 'educar/portal-laravel' is up to date...
==> portal-laravel: Clearing any previously set forwarded ports...
==> portal-laravel: Clearing any previously set network interfaces...
==> portal-laravel: Preparing network interfaces based on configuration...
portal-laravel: Adapter 1: nat
portal-laravel: Adapter 2: hostonly
==> portal-laravel: Forwarding ports...
portal-laravel: 22 (guest) => 2222 (host) (adapter 1)
==> portal-laravel: Running 'pre-boot' VM customizations...
==> portal-laravel: Booting VM...
==> portal-laravel: Waiting for machine to boot. This may take a few minutes...
portal-laravel: SSH address: 127.0.0.1:2222
portal-laravel: SSH username: vagrant
portal-laravel: SSH auth method: private key
==> portal-laravel: Machine booted and ready!
[portal-laravel] GuestAdditions 5.1.22 running --- OK.
==> portal-laravel: Checking for guest additions in VM...
==> portal-laravel: Configuring and enabling network interfaces...
==> portal-laravel: Mounting shared folders...
portal-laravel: /vagrant => /home/hmontero/Proyectos/portal-laravel
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
Protocol error
---
y mi archivo de /etc/hosts
127.0.0.1 localhost
127.0.1.1 HP-HMONTERO
192.168.10.2 portal-laravel.educ.ar local-backend.educ.ar
backend-laravel.educ.ar
Muchas gracias por la ayuda
2017-06-27 17:56 GMT-03:00 claudio menet <claudiomenet@gmail.com>:
> Hernan,
>
> Veo en la siguiente línea que estás utilizando NFS para montar tu
> carpeta compartida. No se si esto es indispensable en tu caso ya que
> por lo que pude ver en la documentación de Vagrant este monta por
> defecto el directorio /vagrant si necesidad de agregar ninguna
> configuración, eso sin utiliza NFS.
>
> Si no es indispensable utilizar NFS comentaría la siguiente línea de
> código e intentaría arrancar la box.
>
> #config.vm.synced_folder ".", "/vagrant", type: "nfs"
>
> Si es necesario utilizar NFS, revisaría si está instalado y
> funcionando el servicio NFS en mi host. Esto lo podes hacer con:
>
> aptitude search nfs-server
>
> (si no tenes instaldo aptitude podes instalarlo ejecutado como root el
> comando apt-get update y luego apt-get install aptitude)
>
> Luego comprobaría que el demonio NFS esté levantado ejecutando el comando:
>
> ps -fea | grep nfs
>
> Por otro lado:
>
> ¿Tu host tiene IP 192.168.10.1? Supongo que si por lo que muestra el log...
> ¿La IP 192.168.10.2 está disponible en tu lan?
>
> Saludos
>
> 2017-06-27 17:05 GMT-03:00 Hernan Montero <montero.hernan.90@gmail.com>:
>> Hola Claudio, así deje el vagrantfile:
>>
>> -----
>>
>> # Versión de la API de Vagrant
>> VAGRANTFILE_API_VERSION = "2"
>>
>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>
>> # Definir máquina virtual
>> config.vm.define :'portal-laravel'
>>
>> # Configurar caja
>> config.vm.box = "educar/portal-laravel"
>> config.vm.box_url =
>> "http://packages.educ.gov.ar/educar-boxes/portal-laravel/last/portal-laravel.json";
>>
>> # Configurar proveedor
>> config.vm.provider "virtualbox" do |v|
>> v.memory = 1024
>> end
>>
>> # Configurar dirección de IP
>> config.vm.network "private_network", ip: "192.168.10.2"
>>
>> # Configurar carpeta compartida
>> config.vm.synced_folder ".", "/vagrant", type: "nfs"
>>
>> end
>>
>> ------
>>
>> Tambien me di cuenta que me faltaba agregar la extensión de virtual
>> box (Oracle_VM_VirtualBox_Extension_Pack-5.1.22-115126.vbox-extpack) y
>> al agregar la extensión apareció lo siguiente:
>>
>> ---
>> hmontero@HP-HMONTERO:~/Proyectos/portal-laravel$ vagrant up
>> Bringing machine 'portal-laravel' up with 'virtualbox' provider...
>> ==> portal-laravel: Checking if box 'educar/portal-laravel' is up to date...
>> ==> portal-laravel: Clearing any previously set forwarded ports...
>> ==> portal-laravel: Clearing any previously set network interfaces...
>> ==> portal-laravel: Preparing network interfaces based on configuration...
>> portal-laravel: Adapter 1: nat
>> portal-laravel: Adapter 2: hostonly
>> ==> portal-laravel: Forwarding ports...
>> portal-laravel: 22 (guest) => 2222 (host) (adapter 1)
>> ==> portal-laravel: Running 'pre-boot' VM customizations...
>> ==> portal-laravel: Booting VM...
>> ==> portal-laravel: Waiting for machine to boot. This may take a few minutes...
>> portal-laravel: SSH address: 127.0.0.1:2222
>> portal-laravel: SSH username: vagrant
>> portal-laravel: SSH auth method: private key
>> ==> portal-laravel: Machine booted and ready!
>> ==> portal-laravel: Checking for guest additions in VM...
>> portal-laravel: No guest additions were detected on the base box
>> for this VM! Guest
>> portal-laravel: additions are required for forwarded ports, shared
>> folders, host only
>> portal-laravel: networking, and more. If SSH fails on this machine,
>> please install
>> portal-laravel: the guest additions and repackage the box to continue.
>> portal-laravel:
>> portal-laravel: This is not an error message; everything may
>> continue to work properly,
>> portal-laravel: in which case you may ignore this message.
>> ==> portal-laravel: Configuring and enabling network interfaces...
>> ==> portal-laravel: Exporting NFS shared folders...
>> ==> portal-laravel: Preparing to edit /etc/exports. Administrator
>> privileges will be required...
>> ● nfs-server.service - NFS server and services
>> Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled;
>> vendor preset: enabled)
>> Active: active (exited) since Sat 2017-06-24 20:23:22 -03; 2 days ago
>> Process: 667 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited,
>> status=0/SUCCESS)
>> Process: 652 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
>> Main PID: 667 (code=exited, status=0/SUCCESS)
>> Tasks: 0 (limit: 4915)
>> CGroup: /system.slice/nfs-server.service
>> ==> portal-laravel: Mounting NFS shared folders...
>>
>> ---
>>
>> Me resulto raro el siguiente texto:
>> "No guest additions were detected on the base box for this VM! Guest
>> additions are required for forwarded ports, shared folders, host only
>> networking, and more. If SSH fails on this machine, please install the
>> guest additions and repackage the box to continue."
>>
>> Hice una búsqueda del mismo y encontré en este link
>> https://github.com/gfreeau/php7play/issues/1 que me faltaba agregar
>> los siguientes plugins:
>>
>> vagrant plugin install vagrant-vbguest
>>
>> Ahora la consola me dice lo siguiente:
>>
>> ---
>>
>> hmontero@HP-HMONTERO:~/Proyectos/portal-laravel$ vagrant plugin
>> install vagrant-vbguest
>> Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
>> Fetching: micromachine-2.0.0.gem (100%)
>> Fetching: vagrant-vbguest-0.14.2.gem (100%)
>> Installed the plugin 'vagrant-vbguest (0.14.2)'!
>> hmontero@HP-HMONTERO:~/Proyectos/portal-laravel$ vagrant up
>> Bringing machine 'portal-laravel' up with 'virtualbox' provider...
>> ==> portal-laravel: Checking if box 'educar/portal-laravel' is up to date...
>> ==> portal-laravel: Clearing any previously set forwarded ports...
>> ==> portal-laravel: Fixed port collision for 22 => 2222. Now on port 2200.
>> ==> portal-laravel: Clearing any previously set network interfaces...
>> ==> portal-laravel: Preparing network interfaces based on configuration...
>> portal-laravel: Adapter 1: nat
>> portal-laravel: Adapter 2: hostonly
>> ==> portal-laravel: Forwarding ports...
>> portal-laravel: 22 (guest) => 2200 (host) (adapter 1)
>> ==> portal-laravel: Running 'pre-boot' VM customizations...
>> ==> portal-laravel: Booting VM...
>> ==> portal-laravel: Waiting for machine to boot. This may take a few minutes...
>> portal-laravel: SSH address: 127.0.0.1:2200
>> portal-laravel: SSH username: vagrant
>> portal-laravel: SSH auth method: private key
>> ==> portal-laravel: Machine booted and ready!
>> [portal-laravel] No installation found.
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> The following extra packages will be installed:
>> cpp-4.8 gcc-4.8 libasan0 libgcc-4.8-dev linux-compiler-gcc-4.8-x86
>> linux-headers-3.16.0-4-common linux-headers-amd64 linux-kbuild-3.16
>> Suggested packages:
>> gcc-4.8-locales gcc-4.8-multilib gcc-4.8-doc libgcc1-dbg libgomp1-dbg
>> libitm1-dbg libatomic1-dbg libasan0-dbg libtsan0-dbg libquadmath0-dbg
>> Recommended packages:
>> linux-image
>> The following NEW packages will be installed:
>> cpp-4.8 dkms gcc-4.8 libasan0 libgcc-4.8-dev linux-compiler-gcc-4.8-x86
>> linux-headers-3.16.0-4-amd64 linux-headers-3.16.0-4-common
>> linux-headers-amd64 linux-kbuild-3.16
>> 0 upgraded, 10 newly installed, 0 to remove and 97 not upgraded.
>> Need to get 16.7 MB of archives.
>> After this operation, 62.1 MB of additional disk space will be used.
>> Err http://security.debian.org/ jessie/updates/main
>> linux-compiler-gcc-4.8-x86 amd64 3.16.36-1+deb8u1
>> 404 Not Found [IP: 200.17.202.197 80]
>> Err http://security.debian.org/ jessie/updates/main
>> linux-headers-3.16.0-4-common amd64 3.16.36-1+deb8u1
>> 404 Not Found [IP: 200.17.202.197 80]
>> Err http://security.debian.org/ jessie/updates/main
>> linux-headers-3.16.0-4-amd64 amd64 3.16.36-1+deb8u1
>> 404 Not Found [IP: 200.17.202.197 80]
>> Get:1 http://httpredir.debian.org/debian/ jessie/main libasan0 amd64
>> 4.8.4-1 [63.3 kB]
>> Get:2 http://httpredir.debian.org/debian/ jessie/main cpp-4.8 amd64
>> 4.8.4-1 [4,577 kB]
>> Get:3 http://httpredir.debian.org/debian/ jessie/main dkms all
>> 2.2.0.3-2 [70.9 kB]
>> Get:4 http://httpredir.debian.org/debian/ jessie/main libgcc-4.8-dev
>> amd64 4.8.4-1 [1,689 kB]
>> Get:5 http://httpredir.debian.org/debian/ jessie/main gcc-4.8 amd64
>> 4.8.4-1 [4,787 kB]
>> Get:6 http://httpredir.debian.org/debian/ jessie/main
>> linux-kbuild-3.16 amd64 3.16.7-ckt20-1 [174 kB]
>> Get:7 http://httpredir.debian.org/debian/ jessie/main
>> linux-headers-amd64 amd64 3.16+63 [5,050 B]
>> Fetched 11.4 MB in 14s (773 kB/s)
>> E: Failed to fetch
>> http://security.debian.org/pool/updates/main/l/linux/linux-compiler-gcc-4.8-x86_3.16.36-1+deb8u1_amd64.deb
>> 404 Not Found [IP: 200.17.202.197 80]
>>
>> E: Failed to fetch
>> http://security.debian.org/pool/updates/main/l/linux/linux-headers-3.16.0-4-common_3.16.36-1+deb8u1_amd64.deb
>> 404 Not Found [IP: 200.17.202.197 80]
>>
>> E: Failed to fetch
>> http://security.debian.org/pool/updates/main/l/linux/linux-headers-3.16.0-4-amd64_3.16.36-1+deb8u1_amd64.deb
>> 404 Not Found [IP: 200.17.202.197 80]
>>
>> E: Unable to fetch some archives, maybe run apt-get update or try with
>> --fix-missing?
>> Hit http://packages.educ.gov.ar unstable InRelease
>> Hit http://packages.educ.gov.ar unstable InRelease
>> Hit http://packages.educ.gov.ar unstable InRelease
>> Hit http://packages.educ.gov.ar unstable InRelease
>> Hit http://packages.educ.gov.ar unstable/main amd64 Packages
>> Hit http://packages.educ.gov.ar unstable/main amd64 Packages
>> Hit http://packages.educ.gov.ar unstable/main amd64 Packages
>> Hit http://packages.educ.gov.ar unstable/main amd64 Packages
>> Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
>> Get:2 http://security.debian.org jessie/updates/main Sources [209 kB]
>> Ign http://packages.educ.gov.ar unstable/main Translation-en_US
>> Ign http://packages.educ.gov.ar unstable/main Translation-en
>> Ign http://packages.educ.gov.ar unstable/main Translation-en_US
>> Get:3 http://security.debian.org jessie/updates/main amd64 Packages [415 kB]
>> Ign http://packages.educ.gov.ar unstable/main Translation-en
>> Ign http://packages.educ.gov.ar unstable/main Translation-en_US
>> Ign http://packages.educ.gov.ar unstable/main Translation-en
>> Ign http://packages.educ.gov.ar unstable/main Translation-en_US
>> Ign http://packages.educ.gov.ar unstable/main Translation-en
>> Get:4 http://security.debian.org jessie/updates/main Translation-en [218 kB]
>> Ign http://httpredir.debian.org jessie InRelease
>> Get:5 http://httpredir.debian.org jessie Release.gpg [2,373 B]
>> Get:6 http://httpredir.debian.org jessie Release [148 kB]
>> Get:7 http://httpredir.debian.org jessie/main Sources [7,055 kB]
>> Get:8 http://httpredir.debian.org jessie/main amd64 Packages [6,790 kB]
>> Get:9 http://httpredir.debian.org jessie/main Translation-en [4,583 kB]
>> Fetched 19.5 MB in 35s (542 kB/s)
>> Reading package lists...
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> The following extra packages will be installed:
>> cpp-4.8 gcc-4.8 libasan0 libgcc-4.8-dev linux-compiler-gcc-4.8-x86
>> linux-headers-3.16.0-4-common linux-headers-amd64 linux-kbuild-3.16
>> Suggested packages:
>> gcc-4.8-locales gcc-4.8-multilib gcc-4.8-doc libgcc1-dbg libgomp1-dbg
>> libitm1-dbg libatomic1-dbg libasan0-dbg libtsan0-dbg libquadmath0-dbg
>> Recommended packages:
>> linux-image
>> The following NEW packages will be installed:
>> cpp-4.8 dkms gcc-4.8 libasan0 libgcc-4.8-dev linux-compiler-gcc-4.8-x86
>> linux-headers-3.16.0-4-amd64 linux-headers-3.16.0-4-common
>> linux-headers-amd64 linux-kbuild-3.16
>> 0 upgraded, 10 newly installed, 0 to remove and 168 not upgraded.
>> Need to get 5,367 kB/16.7 MB of archives.
>> After this operation, 62.1 MB of additional disk space will be used.
>> Get:1 http://security.debian.org/ jessie/updates/main
>> linux-compiler-gcc-4.8-x86 amd64 3.16.43-2+deb8u2 [359 kB]
>> Get:2 http://security.debian.org/ jessie/updates/main
>> linux-headers-3.16.0-4-common amd64 3.16.43-2+deb8u2 [4,556 kB]
>> Get:3 http://security.debian.org/ jessie/updates/main
>> linux-headers-3.16.0-4-amd64 amd64 3.16.43-2+deb8u2 [451 kB]
>> dpkg-preconfigure: unable to re-open stdin: No such file or directory
>> Fetched 5,367 kB in 8s (602 kB/s)
>> Selecting previously unselected package libasan0:amd64.
>> (Reading database ... 43880 files and directories currently installed.)
>> Preparing to unpack .../libasan0_4.8.4-1_amd64.deb ...
>> Unpacking libasan0:amd64 (4.8.4-1) ...
>> Selecting previously unselected package cpp-4.8.
>> Preparing to unpack .../cpp-4.8_4.8.4-1_amd64.deb ...
>> Unpacking cpp-4.8 (4.8.4-1) ...
>> Selecting previously unselected package dkms.
>> Preparing to unpack .../dkms_2.2.0.3-2_all.deb ...
>> Unpacking dkms (2.2.0.3-2) ...
>> Selecting previously unselected package libgcc-4.8-dev:amd64.
>> Preparing to unpack .../libgcc-4.8-dev_4.8.4-1_amd64.deb ...
>> Unpacking libgcc-4.8-dev:amd64 (4.8.4-1) ...
>> Selecting previously unselected package gcc-4.8.
>> Preparing to unpack .../gcc-4.8_4.8.4-1_amd64.deb ...
>> Unpacking gcc-4.8 (4.8.4-1) ...
>> Selecting previously unselected package linux-compiler-gcc-4.8-x86.
>> Preparing to unpack
>> .../linux-compiler-gcc-4.8-x86_3.16.43-2+deb8u2_amd64.deb ...
>> Unpacking linux-compiler-gcc-4.8-x86 (3.16.43-2+deb8u2) ...
>> Selecting previously unselected package linux-headers-3.16.0-4-common.
>> Preparing to unpack
>> .../linux-headers-3.16.0-4-common_3.16.43-2+deb8u2_amd64.deb ...
>> Unpacking linux-headers-3.16.0-4-common (3.16.43-2+deb8u2) ...
>> Selecting previously unselected package linux-kbuild-3.16.
>> Preparing to unpack .../linux-kbuild-3.16_3.16.7-ckt20-1_amd64.deb ...
>> Unpacking linux-kbuild-3.16 (3.16.7-ckt20-1) ...
>> Selecting previously unselected package linux-headers-3.16.0-4-amd64.
>> Preparing to unpack
>> .../linux-headers-3.16.0-4-amd64_3.16.43-2+deb8u2_amd64.deb ...
>> Unpacking linux-headers-3.16.0-4-amd64 (3.16.43-2+deb8u2) ...
>> Selecting previously unselected package linux-headers-amd64.
>> Preparing to unpack .../linux-headers-amd64_3.16+63_amd64.deb ...
>> Unpacking linux-headers-amd64 (3.16+63) ...
>> Processing triggers for man-db (2.7.0.2-5) ...
>> Setting up libasan0:amd64 (4.8.4-1) ...
>> Setting up cpp-4.8 (4.8.4-1) ...
>> Setting up dkms (2.2.0.3-2) ...
>> Setting up libgcc-4.8-dev:amd64 (4.8.4-1) ...
>> Setting up gcc-4.8 (4.8.4-1) ...
>> Setting up linux-compiler-gcc-4.8-x86 (3.16.43-2+deb8u2) ...
>> Setting up linux-headers-3.16.0-4-common (3.16.43-2+deb8u2) ...
>> Setting up linux-kbuild-3.16 (3.16.7-ckt20-1) ...
>> Setting up linux-headers-3.16.0-4-amd64 (3.16.43-2+deb8u2) ...
>> Examining /etc/kernel/header_postinst.d.
>> run-parts: executing /etc/kernel/header_postinst.d/dkms 3.16.0-4-amd64
>> Setting up linux-headers-amd64 (3.16+63) ...
>> Processing triggers for libc-bin (2.19-18+deb8u2) ...
>> Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the
>> box /tmp/VBoxGuestAdditions.iso
>> mount: /dev/loop0 is write-protected, mounting read-only
>> Installing Virtualbox Guest Additions 5.1.22 - guest version is unknown
>> Verifying archive integrity... All good.
>> Uncompressing VirtualBox 5.1.22 Guest Additions for Linux...........
>> VirtualBox Guest Additions installer
>> Copying additional installer modules ...
>> Installing additional modules ...
>> vboxadd.sh: Starting the VirtualBox Guest Additions.
>> ==> portal-laravel: Checking for guest additions in VM...
>> ==> portal-laravel: Configuring and enabling network interfaces...
>> ==> portal-laravel: Exporting NFS shared folders...
>> ==> portal-laravel: Preparing to edit /etc/exports. Administrator
>> privileges will be required...
>> ● nfs-server.service - NFS server and services
>> Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled;
>> vendor preset: enabled)
>> Active: active (exited) since Sat 2017-06-24 20:23:22 -03; 2 days ago
>> Process: 667 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited,
>> status=0/SUCCESS)
>> Process: 652 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
>> Main PID: 667 (code=exited, status=0/SUCCESS)
>> Tasks: 0 (limit: 4915)
>> CGroup: /system.slice/nfs-server.service
>> ==> portal-laravel: Mounting NFS shared folders...
>> The following SSH command responded with a non-zero exit status.
>> Vagrant assumes that this means the command failed!
>> mount -o vers=3,udp
>> 192.168.10.1:/home/hmontero/Proyectos/portal-laravel /vagrant
>> Stdout from the command:
>> Stderr from the command:
>> mount.nfs: Connection timed out
>>
>> ---
>>
>> Aun sigo sin poder hacerlo funcionar.
>>
>>
>> Muchas Gracias por la ayuda
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 2017-06-27 16:29 GMT-03:00 claudio menet <claudiomenet@gmail.com>:
>>> Hola Hernan,
>>>
>>> Entiendo, mire con mas detenimiento el log que pasas.
>>>
>>> ¿Pensaste en invertir estas líneas en el archivo de VagrantFile?
>>>
>>> Digo reemplazar esto:
>>>
>>> # Configurar carpeta compartida
>>> config.vm.synced_folder ".", "/vagrant", type: "nfs"
>>>
>>> # Configurar dirección de IP
>>> config.vm.network "private_network", ip: "192.168.10.2"
>>>
>>> Por esto:
>>>
>>> # Configurar dirección de IP
>>> config.vm.network "private_network", ip: "192.168.10.2"
>>>
>>> # Configurar carpeta compartida
>>> config.vm.synced_folder ".", "/vagrant", type: "nfs"
>>>
>>> Se me ocurre que puede estar intentando montar el directorio
>>> compartido por NFS antes de asignarle la IP.
>>>
>>> Saludos!
>>>
>>> 2017-06-27 13:41 GMT-03:00 Hernan Montero <montero.hernan.90@gmail.com>:
>>>> Hola Claudio, muchas gracias por la respuesta.
>>>> Hice toda una instalación desde cero y otra prueba que hice fue borrar
>>>> y crear la virtual desde el vagrant.
>>>> También hice búsquedas por los buscadores sobre mi problema, pero las
>>>> soluciones que aparecían no me funcionaron.
>>>> Me un compañero que tiene el mismo problema con las mismas
>>>> configuraciones se inscribió en las ayudas de vagrant, pero aun no le
>>>> contestaron.
>>>>
>>>> Saludos y muchas gracias por la ayuda.
>>>>
>>>> 2017-06-27 13:31 GMT-03:00 claudio menet <claudiomenet@gmail.com>:
>>>>> Hola!
>>>>>
>>>>> ¿Abriste virtual box luego de la actualización de debian?
>>>>>
>>>>> VirtualBox suele necesitar que se ejecute un script luego de que se
>>>>> realizan actualizaciones en el kernel del sistema operativo.
>>>>>
>>>>> Yo abriría manualmente VirtualBox y si me muestra el mensaje de que
>>>>> necesita actualizar seguiría los pasos que indica.
>>>>>
>>>>> Saludos!
>>>>>
>>>>> 2017-06-27 13:09 GMT-03:00 Hernan Montero <montero.hernan.90@gmail.com>:
>>>>>> Hola a todos,
>>>>>> Les comento a todos que eh migrado a Debian Stretch y estoy teniendo
>>>>>> unos problemas con Vagrant.
>>>>>> Sistema operativo: Debian 9.0 (Stretch) AMD64
>>>>>> Vagrant: 1.9.5
>>>>>> Virtual: Virtual Box OS versión 5.1
>>>>>>
>>>>>> El problema que me aparece es que el vagrant no esta levantando el
>>>>>> adaptador de red de la virtual box (vboxnet0).
>>>>>>
>>>>>> Dejo la información que me da la consola:
>>>>>>
>>>>>> hmontero@HP-HMONTERO:~/Proyectos/portal-laravel$ vagrant up
>>>>>> Bringing machine 'portal-laravel' up with 'virtualbox' provider...
>>>>>> ==> portal-laravel: Box 'educar/portal-laravel' could not be found.
>>>>>> Attempting to find and in
>>>>>> stall...
>>>>>> portal-laravel: Box Provider: virtualbox
>>>>>> portal-laravel: Box Version: >= 0
>>>>>> ==> portal-laravel: Loading metadata for box
>>>>>> 'http://packages.educ.gov.ar/educar-boxes/portal
>>>>>> -laravel/last/portal-laravel.json'
>>>>>> portal-laravel: URL:
>>>>>> http://packages.educ.gov.ar/educar-boxes/portal-laravel/last/portal-
>>>>>> laravel.json
>>>>>> ==> portal-laravel: Adding box 'educar/portal-laravel' (v0.3) for
>>>>>> provider: virtualbox
>>>>>> portal-laravel: Downloading:
>>>>>> http://packages.educ.gov.ar/educar-boxes/portal-laravel/vers
>>>>>> iones/0.3/portal-laravel-0.3.box
>>>>>> ==> portal-laravel: Box download is resuming from prior download progress
>>>>>> ==> portal-laravel: Successfully added box 'educar/portal-laravel'
>>>>>> (v0.3) for 'virtualbox'!
>>>>>> ==> portal-laravel: Importing base box 'educar/portal-laravel'...
>>>>>> ==> portal-laravel: Matching MAC address for NAT networking...
>>>>>> ==> portal-laravel: Checking if box 'educar/portal-laravel' is up to date...
>>>>>> ==> portal-laravel: Setting the name of the VM:
>>>>>> portal-laravel_portal-laravel_1498352247358_6
>>>>>> 659
>>>>>> ==> portal-laravel: Clearing any previously set network interfaces...
>>>>>> ==> portal-laravel: Preparing network interfaces based on configuration...
>>>>>> portal-laravel: Adapter 1: nat
>>>>>> portal-laravel: Adapter 2: hostonly
>>>>>> ==> portal-laravel: Forwarding ports...
>>>>>> portal-laravel: 22 (guest) => 2222 (host) (adapter 1)
>>>>>> ==> portal-laravel: Running 'pre-boot' VM customizations...
>>>>>> ==> portal-laravel: Booting VM...
>>>>>> ==> portal-laravel: Waiting for machine to boot. This may take a few minutes...
>>>>>> portal-laravel: SSH address: 127.0.0.1:2222
>>>>>> portal-laravel: SSH username: vagrant
>>>>>> portal-laravel: SSH auth method: private key
>>>>>> ==> portal-laravel: Machine booted and ready!
>>>>>> ==> portal-laravel: Checking for guest additions in VM...
>>>>>> portal-laravel: No guest additions were detected on the base box
>>>>>> for this VM! Guest
>>>>>> portal-laravel: additions are required for forwarded ports, shared
>>>>>> folders, host only
>>>>>> portal-laravel: networking, and more. If SSH fails on this machine,
>>>>>> please install
>>>>>> portal-laravel: the guest additions and repackage the box to continue.
>>>>>> portal-laravel:
>>>>>> portal-laravel: This is not an error message; everything may
>>>>>> continue to work properly,
>>>>>> portal-laravel: in which case you may ignore this message.
>>>>>> ==> portal-laravel: Configuring and enabling network interfaces...
>>>>>> ==> portal-laravel: Exporting NFS shared folders...
>>>>>> ==> portal-laravel: Preparing to edit /etc/exports. Administrator
>>>>>> privileges will be required
>>>>>> ...
>>>>>> [sudo] password for hmontero:
>>>>>> ● nfs-server.service - NFS server and services
>>>>>> Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled;
>>>>>> vendor preset: enabled)
>>>>>> Active: active (exited) since Sat 2017-06-24 20:23:22 -03; 1h 35min ago
>>>>>> Process: 667 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited,
>>>>>> status=0/SUCCESS)
>>>>>> Process: 652 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
>>>>>> Main PID: 667 (code=exited, status=0/SUCCESS)
>>>>>> Tasks: 0 (limit: 4915)
>>>>>> CGroup: /system.slice/nfs-server.service
>>>>>> ==> portal-laravel: Mounting NFS shared folders...
>>>>>> The following SSH command responded with a non-zero exit status.
>>>>>> Vagrant assumes that this means the command failed!
>>>>>> mount -o vers=3,udp
>>>>>> 192.168.10.1:/home/hmontero/Proyectos/portal-laravel /vagrant
>>>>>> Stdout from the command:
>>>>>> Stderr from the command:
>>>>>> mount.nfs: Connection timed out
>>>>>>
>>>>>>
>>>>>> VagrantFile:
>>>>>>
>>>>>> # Versión de la API de Vagrant
>>>>>> VAGRANTFILE_API_VERSION = "2"
>>>>>>
>>>>>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>>>>>
>>>>>> # Definir máquina virtual
>>>>>> config.vm.define :'portal-laravel'
>>>>>>
>>>>>> # Configurar caja
>>>>>> config.vm.box = "educar/portal-laravel"
>>>>>> config.vm.box_url =
>>>>>> "http://packages.educ.gov.ar/educar-boxes/portal-laravel/last/portal-laravel.json";
>>>>>>
>>>>>> # Configurar proveedor
>>>>>> config.vm.provider "virtualbox" do |v|
>>>>>> v.memory = 1024
>>>>>> end
>>>>>>
>>>>>> # Configurar carpeta compartida
>>>>>> config.vm.synced_folder ".", "/vagrant", type: "nfs"
>>>>>>
>>>>>> # Configurar dirección de IP
>>>>>> config.vm.network "private_network", ip: "192.168.10.2"
>>>>>>
>>>>>> end
>>>>>>
>>>>>> Desde ya, muchas gracias
>>>>>> --
>>>>>> Saludos
>>>>>> **Hernan**
>>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Saludos
>>>> **Hernan**
>>
>>
>>
>> --
>> Saludos
>> **Hernan**
--
Saludos
**Hernan**
Reply to: