Hi David, Thank you for your prompt response. So I "up" the vagrant again in a non proxy internet connection and end up with this [1]. It has less errors than the earlier one. and when I do "vagrant ssh" i got the following,
amila@amila-X550LD:~/Installs/ryaVagrant$ vagrant ssh Welcome to Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-87-generic x86_64) * Documentation: https://help.ubuntu.com/ System information as of Tue Jun 14 17:03:04 UTC 2016 System load: 0.96 Processes: 110 Usage of /: 3.5% of 39.34GB Users logged in: 0 Memory usage: 3% IP address for eth0: 10.0.2.15 Swap usage: 0% Graph this data and manage this system at: https://landscape.canonical.com/ Get cloud support with Ubuntu Advantage Cloud Guest: http://www.ubuntu.com/business/services/cloud 0 packages can be updated. 0 updates are security updates. vagrant@rya-example-box:~$ And after that I can run those two commands (ping google.com and wget http://google.com/) without any error. Is it ok? if it is I like to know how to proceed further. Thank you! [1] https://gist.github.com/AmilaWijayarathna/8a2a20e6a4a1b9b5449bad83f459762b On Tue, Jun 14, 2016 at 11:10 PM, David Lotts <[email protected]> wrote: > Wow, well documented attempt! Thanks for the listings. > > So you brought "up" a default vagrant VM. > All the messages from [3] are as I would expect, that is great. > > Then your copied the Rya Vagrantfile, and did a vagrant up, creating the > output in [5]. > It downloaded the vm image from cloudera successfully, so we know your > internet connection on the host is fine. > But then when the guest VM attempts to update it's libraries, we start > seeing all errors, starting with this one: > > ==> default: Failed to fetch > http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease > > So I think something is wrong with your network inside the VM. > Run the command > vagrant ssh > from it's install directory, then see if you can run these without error: > ping google.com > and/or > wget http://google.com/ > => Resolving google.com (google.com)... Connecting to google.com ( > google.com) > > I can't tell if your first VM [3] was able to connect, you might ssh to > it, and then ping and wget to see if it also has network problems. > > If you start the Virtualbox app, you can modify the network setting for > the box and see if you can get it working. Maybe you can set a proxy as > you mentioned. > > david. > > > On Tue, Jun 14, 2016 at 12:36 PM, Amila Wijayarathna < > [email protected]> wrote: > >> Hi david, >> This is my first time, setting up a vagrant file. >> I downloaded the vagrant from [1] and downloaded a virtual box from [2]. >> As this is my first time i didn't know how to do it correctly. So i >> installed the the vagrant and up it other location that there was no any >> Rya vagrant file. so i got this [3]. seems it set up successfully. >> >> After that I copied the vagrant file from [4] and made a Vagrantfile in a >> local location. when i do vagrant up in that location i got this [5]. it >> says something went wrong. >> I don't know this because is my Internet connection, because it has some >> proxy settings. I will look about it. Any idea about this is appreciated. >> >> Thank you! >> >> >> [1] https://www.vagrantup.com/ <https://www.vagrantup.com/> >> [2] https://www.virtualbox.org/wiki/Linux_Downloads >> [3] >> https://gist.github.com/AmilaWijayarathna/52aa5da9a9c6e952967b1db1b01a1701 >> [4] >> https://github.com/DLotts/incubator-rya/blob/RYA-54_vagrant-cleanup-squ/extras/vagrantExample/src/main/vagrant/Vagrantfile >> [5] >> https://gist.github.com/AmilaWijayarathna/9dd9ce075d98524dad9a97eb1d521e99 >> >> On Mon, Jun 13, 2016 at 11:22 PM, Adina Crainiceanu <[email protected]> >> wrote: >> >>> David, I'm travelling until Thursday. I'll try it then if Amila does not >>> do >>> it earlier. >>> >>> Thanks, >>> Adina >>> >>> On Mon, Jun 13, 2016 at 11:47 AM, David Lotts <[email protected]> wrote: >>> >>> > Adina, Amila, and everyone: >>> > >>> > Adina: Thanks for the great feedback! >>> > I think I have resolved everything that you mention, and a few others. >>> > Are you able to run it again? >>> > I updated the readme.md also. >>> > >>> > It's in my Rya github branch "RYA-54_vagrant-cleanup-squ" : >>> > >>> > >>> > >>> https://github.com/DLotts/incubator-rya/blob/RYA-54_vagrant-cleanup-squ/extras/vagrantExample/src/main/vagrant >>> > >>> > Start-over instructions below. >>> > >>> > The pull request is here: >>> https://github.com/apache/incubator-rya/pull/47 >>> > david. >>> > >>> > >>> > On Tue, May 17, 2016 at 10:54 AM, David Lotts <[email protected]> >>> wrote: >>> > Amila, >>> > I have re-worked the Vagrant Example. There were some race conditions >>> and >>> > places where errors become lost or skipped over. >>> > [...old link removed...] >>> > >>> > It uses the same instructions. >>> > You can do the command: >>> > >>> > vagrant destroy >>> > >>> > To remove your last attempt. Then use the new file and the same >>> readme to >>> > start over. >>> > >>> > The new version is made to be re-run and possible fix errors from the >>> last >>> > attempt -- so you could just copy this over your old version and type: >>> > >>> > vagrant provision >>> > >>> > Then follow the readme instructions. >>> > I am interested in your experience with this. >>> > >>> >>> >>> >>> -- >>> Dr. Adina Crainiceanu >>> Associate Professor, Computer Science Department >>> United States Naval Academy >>> 410-293-6822 >>> [email protected] >>> http://www.usna.edu/Users/cs/adina/ >>> >> >> >> >> -- >> >> *Amila Wijayarathna* >> Undergraduate, >> Faculty of Information Technology, >> University of Moratuwa, >> Sri Lanka. >> > > -- *Amila Wijayarathna* Undergraduate, Faculty of Information Technology, University of Moratuwa, Sri Lanka.
