Hi Tharindu, I just fixed this in the latest. Thanks for the catch, looks like the path changed since this script was written.
No need for concern; the vagrant solution is provided only as a convenience to developers (and I think the path was correct in our official releases anyhow), so this script never enters into a real production installation of arches. This was probably caused by some recent changes. Nonetheless, well caught! Thanks! - Rob > On May 12, 2014, at 9:47 PM, Tharindu Rusira <[email protected]> wrote: > > Hi Rob, > I destroyed the existing machine and started a new instance of my vagrant > machine. However the process failed because some of the dependencies were not > found in the system. (Please refer to the error log in the attachments > section) > > As the error log suggests, the problem begins with the following line. > /tmp/vagrant-shell: line 1: cd: /vagrant/archesproject/Install: No such file > or directory > > I checked my archesproject directory and instead of a 'Install' directory, it > has a 'install' directory that contains necessary scripts to setup the > environment. So I changed vagrant_setup.sh accordingly so that it directs to > archesproject/install directory. (I have attached the modified > vagrant_setup.sh file too) > > Now 'vagrant up' is capable of running all the scripts the install the > dependencies and I can access Arches at localhost:8000/Arches/index.htm > > Now that Arches is working, I am a bit concerned why has nobody else > encountered this issue earlier. > > Thank you, > > >> On Thu, May 8, 2014 at 10:33 PM, Rob Gaston <[email protected]> wrote: >> Hi Tharindu, >> >> You probably need to first run 'vagrant destroy' before running 'vagrant >> up'. The log that you sent shows that the vm has already been created and >> provisioned, so I can't see the issue there (and you did not actually get a >> 'fresh vagrant instance'). You should compare your output with the one I >> posted on Gist (showing a successful set up); hopefully that will shed some >> light. >> >> - Rob >> >> >>> On Wednesday, May 7, 2014 9:01:08 PM UTC-7, Tharindu Rusira wrote: >>> Hi Rob, I'm sorry I did not reply sooner. >>> >>> I started a fresh vagrant instance and ran runserver-vagrant.sh script. Now >>> the elasticsearch issues does not appear but the problem with >>> virtualenv/ENV/bin/activate is still there (please see vagrant-up.log). >>> >>> When I access http://localhost:8000/Arches/index.htm, it takes quite a >>> while initializing(see arches-initializing.png). Apparently, a couple of >>> http resources are also missing(return 404). (see runserver-vagrant.log) >>> >>> [07/May/2014 21:51:52] "GET /Arches/Media/js/i18n/en-us.js HTTP/1.1" 404 >>> 1664 >>> [07/May/2014 21:52:04] "GET /Arches/Media/js/i18n/en-us.js HTTP/1.1" 404 >>> 1664 >>> >>> >>> Thank you, >>> >>> >>> >>> >>> >>>> On Thu, May 8, 2014 at 2:05 AM, Rob Gaston <[email protected]> wrote: >>>> Hi Tharindu, >>>> >>>> Any progress here? >>>> >>>> You should be able to ignore that particular elasticsearch error -- I >>>> think that is only showing up because elasticsearch is already running on >>>> your virtual machine. You can make it go away by manually killing >>>> elasticsearch by running the following command: >>>> >>>> sudo killall java >>>> >>>> and then restarting the server: >>>> >>>> ./runserver-vagrant.sh >>>> >>>> Of course, you don't have to do this because all that message is really >>>> telling you is that elasticsearch is already running, so you should be >>>> fine. >>>> >>>> I'm still not certain why your virtual environment would not have been >>>> created -- have you been able to determine anything by looking at the >>>> output? Feel free to send that along and I'd be happy to take a look >>>> myself. >>>> >>>> - Rob >>>> >>>> >>>>> On Monday, May 5, 2014 11:27:53 AM UTC-7, Rob Gaston wrote: >>>>> Hi Tharindu, >>>>> >>>>> Looks like the installation did not complete successfully. If it did, >>>>> you should have had the virtual environment generated >>>>> (./runserver-vagrant.sh: line 10: >>>>> archesproject/virtualenv/ENV/bin/activate: No such file or directory), >>>>> which appears to not have happened. This should have happened following >>>>> the 'vagrant up' command. It's hard to say why this happened without >>>>> seeing the output of that command. I'd recommend looking at the gist I >>>>> posted >>>>> (https://gist.githubusercontent.com/robgaston/10031103/raw/arches_vagrant_setup.log) >>>>> that contains the full output from a successful install and comparing >>>>> with the output you are seeing. >>>>> >>>>> I think the permissions issue is a red herring -- those paths are >>>>> relative to the script (note the lack of a leading slash), which is why >>>>> they are different from the complete path to those files on your virtual >>>>> machine. I strongly doubt the issue is related to pathing; my guess is >>>>> that something went wrong and as a result this script was never executed. >>>>> Best way to tell would be to look at the output from the 'vagrant up' >>>>> command. The virtualenv installation output can be seen in the gist >>>>> referred to previously from ln 13541-13635: >>>>> https://gist.github.com/robgaston/10031103#file-arches_vagrant_setup-log-L13541-L13635 >>>>> >>>>> - Rob >>>>> >>>>> >>>>>> On Friday, May 2, 2014 10:37:21 PM UTC-7, Tharindu Rusira wrote: >>>>>> Hello everyone, >>>>>> >>>>>> I am trying to setup Arches development environment on a vagrant >>>>>> machine. I followed this[1] tutorial but when I run runserver-vagrant.sh >>>>>> script, I get the following error. >>>>>> >>>>>> vagrant@precise32:/vagrant$ ./runserver-vagrant.sh >>>>>> ./runserver-vagrant.sh: line 10: >>>>>> archesproject/virtualenv/ENV/bin/activate: No such file or directory >>>>>> Validating models... >>>>>> >>>>>> 0 errors found >>>>>> May 02, 2014 - 20:49:52 >>>>>> Django version 1.6.4, using settings 'archesproject.settings' >>>>>> Starting development server at http://0.0.0.0:8000/ >>>>>> Quit the server with CONTROL-C. >>>>>> [2014-05-03 01:49:52,235][WARN ][bootstrap ] jvm uses the >>>>>> client vm, make sure to run `java` with the server vm for best >>>>>> performance by adding `-server` to the command line >>>>>> {0.90.3}: Initialization Failed ... >>>>>> - ElasticSearchIllegalStateException[Failed to obtain node lock, is the >>>>>> following location writable?: >>>>>> [/vagrant/archesproject/arches/Search/engines/elasticsearch-0.90.3/data/elasticsearch]] >>>>>> >>>>>> But as I can see, the script itself is modifying permissions in a >>>>>> slightly different path but at the runtime elasticsearch is trying to >>>>>> access a different location. >>>>>> >>>>>> #!/bin/bash >>>>>> >>>>>> # Start ElasticSearch >>>>>> chmod u+x >>>>>> "archesproject/arches/Search/engines/elasticsearch-0.90.3/bin/elasticsearch.in.sh" >>>>>> source >>>>>> "archesproject/arches/Search/engines/elasticsearch-0.90.3/bin/elasticsearch.in.sh" >>>>>> chmod u+x >>>>>> "archesproject/arches/Search/engines/elasticsearch-0.90.3/bin/elasticsearch" >>>>>> ./archesproject/arches/Search/engines/elasticsearch-0.90.3/bin/elasticsearch >>>>>> >>>>>> # Start django >>>>>> source "archesproject/virtualenv/ENV/bin/activate" >>>>>> python manage.py runserver 0.0.0.0:8000 >>>>>> >>>>>> Any help to rectify these errors is much appreciated. >>>>>> Thanks, >>>>>> >>>>>> [1] >>>>>> http://www.fargeo.com/blog/setting-up-an-arches-development-environment-using-vagrant/ >>>>>> >>>>>> -- >>>>>> M.P. Tharindu Rusira Kumara >>>>>> >>>>>> Department of Computer Science and Engineering, >>>>>> University of Moratuwa, >>>>>> Sri Lanka. >>>>>> +94757033733 >>>>>> www.tharindu-rusira.blogspot.com >>>> >>>> -- >>>> -- To post, send email to [email protected]. To unsubscribe, send >>>> email to [email protected]. For more information, visit >>>> https://groups.google.com/d/forum/archesproject?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google Groups >>>> "Arches Project" 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. >>> >>> >>> >>> -- >>> M.P. Tharindu Rusira Kumara >>> >>> Department of Computer Science and Engineering, >>> University of Moratuwa, >>> Sri Lanka. >>> +94757033733 >>> www.tharindu-rusira.blogspot.com >> >> -- >> -- To post, send email to [email protected]. To unsubscribe, >> send email to [email protected]. For more >> information, visit https://groups.google.com/d/forum/archesproject?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Arches Project" 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. > > > > -- > M.P. Tharindu Rusira Kumara > > Department of Computer Science and Engineering, > University of Moratuwa, > Sri Lanka. > +94757033733 > www.tharindu-rusira.blogspot.com > > <output.txt> > <vagrant_setup.sh> -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" 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.
