is anything that you can share in a zip file to try to repro? I have OSX/Linux/Windows host
On Wed, Mar 25, 2015 at 10:21 PM, Marcus Brunsten <[email protected]> wrote: > Thanks, > I tried what you said, > But, now it seems i cannot connect to my machine before i package it: > brunis@pingu:~/vagrant$ vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Checking if box 'chef/debian-7.6' is up to date... > ==> default: Fixed port collision for 22 => 2222. Now on port 2200. > ==> 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: 3000 => 1234 (adapter 1) > default: 5432 => 8888 (adapter 1) > default: 22 => 2200 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2200 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > ==> default: Configuring and enabling network interfaces... > ==> default: Rsyncing folder: /home/brunis/vagrant/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the > `--provision` > ==> default: to force provisioning. Provisioners marked to run always will > still run. > > SSH to vagrant and ran what you suggested > > me@host:~/vagrant$ vagrant halt > ==> default: Attempting graceful shutdown of VM... > default: Guest communication could not be established! This is usually > because > default: SSH is not running, the authentication information was changed, > default: or some other networking issue. Vagrant will force halt, if > default: capable. > ==> default: Forcing shutdown of VM... > me@host:~/vagrant$ vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Checking if box 'chef/debian-7.6' is up to date... > ==> default: Clearing any previously set forwarded ports... > ==> default: Fixed port collision for 22 => 2222. Now on port 2200. > ==> 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: 3000 => 1234 (adapter 1) > default: 5432 => 8888 (adapter 1) > default: 22 => 2200 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2200 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Authentication failure. Retrying... > default: Warning: Authentication failure. Retrying.. > > Den onsdag 25 mars 2015 kl. 10:02:33 UTC+1 skrev Alvaro Miranda Aguilera: >> >> Hello, >> >> The IP looks good, so I will suggest ensure the public ssh key is there >> >> This is what I use to setup a Vagrant box: >> >> "useradd vagrant", >> >> "cp /etc/sudoers /etc/sudoers.orig", >> >> "sed -i -e 's/Defaults\\s*requiretty$/#Defaults\trequiretty/' >> /etc/sudoers", >> >> "sed -i -e '/# %wheel\tALL=(ALL)\tNOPASSWD: ALL/a >> %vagrant\tALL=(ALL)\tNOPASSWD: ALL' /etc/sudoers", >> >> "mkdir ~vagrant/.ssh", >> >> "chmod 700 ~vagrant/.ssh", >> >> "echo 'ssh-rsa >> >> AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== >> vagrant insecure public key' > ~vagrant/.ssh/authorized_keys", >> >> "chmod 600 ~vagrant/.ssh/authorized_keys", >> >> "chown -R vagrant: ~vagrant/.ssh", >> >> "cp /etc/ssh/sshd_config /etc/ssh/sshd_config.ori", >> >> "sed -i -e '/#UseDNS yes/a UseDNS no' /etc/ssh/sshd_config", >> >> "for nic in /etc/sysconfig/network-scripts/ifcfg-*; do sed -i >> /HWADDR/d $nic; sed -i /UUID/d $nic || true ; done", >> >> "rm /etc/udev/rules.d/??-persistent-net.rules || true" >> >> >> Remote "" and "", and see what you can reuse. >> >> Hope this helps. >> >> Alvaro. >> >> On Wed, Mar 25, 2015 at 9:32 PM, Marcus Brunsten >> <[email protected]> wrote: >> > The file /etc/udev/rules.d/70-persistent-net.rule did not exist. the >> > directory /etc/udev/rules.d/70-persistent-net.rules/ existed however, >> > should >> > i remove this? It is empty. >> > >> > Output of ifconfig -a >> > root@packer-debian-7:/etc/udev/rules.d# ifconfig -a >> > eth0 Link encap:Ethernet HWaddr 08:00:27:45:b0:85 >> > inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 >> > inet6 addr: fe80::a00:27ff:fe45:b085/64 Scope:Link >> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> > RX packets:1062 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:672 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:1000 >> > RX bytes:106692 (104.1 KiB) TX bytes:80168 (78.2 KiB) >> > >> > eth1 Link encap:Ethernet HWaddr 08:00:27:d0:29:cb >> > inet addr:192.168.56.30 Bcast:192.168.56.255 >> > Mask:255.255.255.0 >> > inet6 addr: fe80::a00:27ff:fed0:29cb/64 Scope:Link >> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:1000 >> > RX bytes:0 (0.0 B) TX bytes:1086 (1.0 KiB) >> > >> > lo Link encap:Local Loopback >> > inet addr:127.0.0.1 Mask:255.0.0.0 >> > inet6 addr: ::1/128 Scope:Host >> > UP LOOPBACK RUNNING MTU:16436 Metric:1 >> > RX packets:38 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:0 >> > RX bytes:21265 (20.7 KiB) TX bytes:21265 (20.7 KiB) >> > >> > >> > Den tisdag 24 mars 2015 kl. 21:39:39 UTC+1 skrev Alvaro Miranda >> > Aguilera: >> >> >> >> On Wed, Mar 25, 2015 at 4:46 AM, Marcus Brunsten >> >> <[email protected]> wrote: >> >> > default: Warning: Authentication failure. Retrying... >> >> >> >> Hello, >> >> >> >> Can you try to connect over the gui and share an ifconfig -a >> >> >> >> before packaging the box, check if >> >> /etc/udev/rules.d/70-persistent-net.rule file exists, if does, delete >> >> it. >> >> >> >> Thanks >> >> Alvaro >> > >> > -- >> > 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 [email protected]. >> > For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
