Pages : 1
#1 Le 26/03/2017, à 22:27
- __fabrice
Vagrant et NFS. Mount time out
Bonjour,
Je viens de faire une VM avec Puphpet, en essayant NFS . Mais lors de l'activation de NFS, cela s'arrete net :
/etc/exports :
# VAGRANT-BEGIN: 1000 8b4f1639-acee-4953-aba2-38e423981e8b
"/var/www/vm" 192.168.56.102(rw,sync,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3412471446)
#"/var/www/vm" 192.168.56.102(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3412471446)
# VAGRANT-END: 1000 8b4f1639-acee-4953-aba2-38e423981e8b
Mais Vagrant le modifie :
# VAGRANT-BEGIN: 1000 8b4f1639-acee-4953-aba2-38e423981e8b
"/var/www/vm" 192.168.56.102(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=3412471446)
# VAGRANT-END: 1000 8b4f1639-acee-4953-aba2-38e423981e8b
Une partie du config.yaml :
synced_folder:
vflsf_dz1yb40c5aje:
owner: www-data
group: www-data
source: /var/www/vm
target: /var/www
sync_type: nfs
smb:
smb_host: ''
smb_username: ''
smb_password: ''
mount_options:
dir_mode: '0775'
file_mode: '0664'
rsync:
args:
- '--verbose'
- '--archive'
- '-z'
exclude:
- .vagrant/
- .git/
auto: 'true'
L'erreur :
DEBUG guest: Found cap: mount_nfs_folder in linux
INFO guest: Execute capability: mount_nfs_folder [#<Vagrant::Machine: vm.spectre.id (VagrantPlugins::ProviderVirtualBox::Provider)>, "192.168.56.1", {"vflsf_dz1yb40c5aje"=>{:id=>"vflsf_dz1yb40c5aje", :type=>:nfs, :guestpath=>"/mnt/vagrant-vflsf_dz1yb40c5aje", :hostpath=>"/var/www/vm", :disabled=>false, :__vagrantfile=>true, :map_uid=>1000, :map_gid=>1000, :nfs_udp=>true, :nfs_version=>3, :uuid=>"3412471446", :linux__nfs_options=>["rw", "no_subtree_check", "all_squash", "anonuid=1000", "anongid=1000", "fsid=3412471446"]}}] (ubuntu)
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: mkdir -p /mnt/vagrant-vflsf_dz1yb40c5aje (sudo=true)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Exit status: 0
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: mount -o vers=3,udp 192.168.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje (sudo=true)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Sending SSH keep-alive...
DEBUG ssh: Sending SSH keep-alive...
...
DEBUG ssh: Exit status: 32
INFO retryable: Retryable exception raised: #<Vagrant::Errors::NFSMountFailed: 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.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje
Stdout from the command:
Stderr from the command:
mount.nfs: Connection timed out
>
DEBUG ssh: Re-using SSH connection.
INFO ssh: Execute: mount -o vers=3,udp 192.168.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje (sudo=true)
DEBUG ssh: stderr: 41e57d38-b4f7-4e46-9c38-13873d338b86-vagrant-ssh
DEBUG ssh: Sending SSH keep-alive...
...
...
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:225:in `action_raw'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:200:in `block in action'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:567:in `lock'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:186:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/machine.rb:186:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
INFO interface: error: 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.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje
Stdout from the command:
Stderr from the command:
mount.nfs: Connection timed out
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.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje
Stdout from the command:
Stderr from the command:
mount.nfs: Connection timed out
INFO interface: Machine: error-exit ["Vagrant::Errors::NFSMountFailed", "The following SSH command responded with a non-zero exit status.\nVagrant assumes that this means the command failed!\n\nmount -o vers=3,udp 192.168.56.1:/var/www/vm /mnt/vagrant-vflsf_dz1yb40c5aje\n\nStdout from the command:\n\n\n\nStderr from the command:\n\nmount.nfs: Connection timed out\n"]
L'adresse IP est 192.168.56.102 alors que je vois dans le debug : 192.168.56.1
Une idée ?
Fabrice
Dernière modification par __fabrice (Le 26/03/2017, à 22:29)
Hors ligne
#2 Le 28/03/2017, à 06:27
- __fabrice
Re : Vagrant et NFS. Mount time out
Hello,
Personne ne sait, ou n'a eu ce problème ?
Merci
Fabrice
Hors ligne
Pages : 1