Hi Chris, also just wanted to double check that you have the virtual 
environment activated when you try the elasticsearch installation...

On Friday, April 22, 2016 at 10:20:32 AM UTC-6, Adam Cox wrote:
>
> Hi Chris and Alexei, I think the django import error is evidence that the 
> install did not work correctly. Somehow it finished thinking that it had, 
> but some of the pieces did not get fully installed.  To start over in the 
> same virtual environment you can run
> pip uninstall arches
>
> I'm surprised that you are getting this error in Ubuntu.  One thing I like 
> to recommend is printing the entire install process output to a text file. 
> Use 
> pip install arches > full_output.txt 2>&1
> Looking through the resulting "full_output.txt" may give us some clues 
> about what is going on.  However, as Alexei mentioned, there are certain 
> errors or warnings that you can ignore. 
>
> What virtual machine are you using?  I'm surprised that you are finding 
> these errors with Ubuntu.  It make have something to do with the privileges 
> that your user has.
>
> Adam
>
> On Sunday, April 17, 2016 at 11:59:27 AM UTC-6, [email protected] wrote:
>>
>> Hello,
>>
>> I'm attempting a new setup on a virtual machine, and I have some 
>> questions regarding my setup. I think I'm almost there, including the 
>> installation of the provided HIP.
>>
>> Here is some info on my setup.
>> -Running Ubuntu Linux 14-04 via Parallels for Mac.
>> -I believe that I successfully installed the pre-requisites.
>> -I think I was successful in installing PIP and have Python (from what I 
>> could find out, Python comes with Ubuntu/Linux?) 
>>
>> On my first attempt, I had most of it set up, and could see the setup 
>> running when looking at the http://localhost:8000/ page. The only thing 
>> that was not working was the Map menu, which was blank probably due to the 
>> settings in the "settings.py" file, and the search menu was not working, 
>> probably due to the Database settings in the "settings.py" file. 
>>
>> I've since modified the "settings.py" file (mainly for the map settings 
>> and obtained the map key for  Bing), and I completely powered down my 
>> virtual machine. I'm attempting to re-run my setup to see if my changes to 
>> the settings.py file is working, but I'm now having problems re-starting 
>> the elasticsearch (with several permission denied messages) and re-staring 
>> Arches by running the "python manage.py run server" (receiving a 
>> "SyntaxError: invalid syntax").
>>
>> I'm probably not doing things in the right order when re-starting my 
>> setup. The following is the order I tried to follow to re-launch.
>>
>> 1-In terminal, run "source ENV/bin/activate"
>> 2-In 2nd terminal window, start the elastic search (errors such as: 
>> "AccessDeniedException" 
>> and "Failed to obtain node lock, is the following location writable?")
>> 3-Even though the elastiseach is not working, I attempted to run Arches 
>> on the 1st terminal with "python manage.py run server" but receive 
>> "SyntaxError: 
>> invalid syntax". I also tried to re-run the "python manage.py packages 
>> -o install" script/command but receive the same error.
>>
>> I suspect that I'm not following the correct order, or I need to go 
>> further back such as re-installing the HIP package. I'll be regularly 
>> shutting down Ubuntu/Linux, and re-starting it.
>>
>> I'm not at all an expert with all of this, and I don't neccesarly know 
>> what all the pieces do (or using the correct terminology), which can 
>> be part of the problem when trying to troubleshoot. Any help 
>> is appreciated, and I'm sure I'll have more questions once I get my setup 
>> figured out.
>>
>> Thanks,
>>
>> Christian
>>
>

-- 
-- 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.

Reply via email to