[Arches] Re: Falling at first hurdle, then the next, then the next.

[Dennis Wuthrich]

Hello Researcher.

I'm sorry that you're having such a difficult time installing Arches.  And 
I get that it's very frustrating when you keep seeing errors at each step.  
However, please keep a few things in mind:

1. The Arches development team is not trying to make it hard for you to use 
the software.  However, it is sophisticated technology and we assume that 
people installing Arches have appropriate IT experience
2. There are many reasons your specific computer might not have installed 
the software properly.  That is, the problem might be your machine 
configuration, not necessarily Arches
3. Arches has been installed successfully many times by many people all 
over the world.  It can be done!

I've heard from several members of the Arches community, and there is a 
concern that the tone in your posts requesting help is a bit off-putting 
and not in line with the Arches community's guidelines.  Please have a look 
at https://www.archesproject.org/code-of-conduct/ to review our code of 
conduct.  Many of the people trying to help you have invested a lot of 
effort in building the software, and many volunteer their time to help 
community members like you who ask for assistance.

Cheers,

Dennis

On Friday, April 12, 2019 at 8:13:54 AM UTC-7, Researcher wrote:
>
> Latest update:
> I've been messing around again and managed to get back to the 'Arches 
> installed stage' and even created a project (step 5), and lo and behold 
> step 6 has also thrown up an issue.
> Firstly, I don't understand what *any* of this means:
> "Before you continue, you may need to open 
> my_project\my_project\settings_local.py and change some 
> environment-specific settings. 
>
>- 
>
>Depending on your Postgres/PostGIS installation, you may need to 
>uncomment the DATABASES section and change the username and password, as 
>well as the name of your PostGIS template database. If you will have 
>multiple Arches projects using the same Postgres server, make sure to 
>change the database name here as well."
>
>BUT I've tried the second part of step 6 and come up with this now too:
>
> (ENV) C:\Users\FIMNT>GDAL_LIBRARY_PATH = "C:\OSGeo4W64\bin\gdal204.dll"
> 'GDAL_LIBRARY_PATH' is not recognized as an internal or external command,
> operable program or batch file.
>
> Any more thoughts from anyone on this one, so I can get to stage 7 and see 
> what new problems that has?
> (in simple/step-by-step terms, ideally)
>
> Thanks,
>
> On Wednesday, April 10, 2019 at 4:01:54 PM UTC-3, Researcher wrote:
>>
>> Hi all,
>> I've been struggling through trying to install Arches all day today 
>> (historian background, not IT professional!) and I thought I was getting 
>> somewhere reaching the point where it told me Arches had been installed (in 
>> Windows command prompt) but even our IT support are unable to get very far 
>> beyond that. Anyone got any advice? Is there a simpler way? I just wanted 
>> to try out the software, not get a degree in coding before I had even seen 
>> what it looked like.
>> I tried to run step 7 on the install guide: 
>> https://arches.readthedocs.io/en/stable/installation/
>> but it says you need elasticsearch running. I tried to install 
>> elasticsearch from the "easiest way" (dread to think what the hard way 
>> looks like) as per below:
>>
>> The easiest way to install Elasticsearch is to use a command that comes 
>> with Arches. Once you have installed Arches (either with pip or from the 
>> Arches 
>> repo ), activate your virtual 
>> environment, enter your app/project root directory (the one that contains 
>> manage.py), run
>>
>> python manage.py es install
>>
>> Elasticsearch will be installed in the root folder. You can specify an 
>> alternate destination for the installation by using the -d argument. For 
>> example
>>
>> python manage.py es install -d C:\Projects
>>
>> will result in a new directory C:\Projects\elasticsearch-5.2.1 from 
>> which you’ll be able to run Elasticsearch.
>>
>> I tried this and got the following:
>> (ENV) C:\Users\FIMNT\my_project>python manage.py es install
>> Traceback (most recent call last):
>>   File "manage.py", line 27, in 
>> from django.core.management import execute_from_command_line
>> ImportError: No module named django.core.management
>>
>> Obviously I or the software have done something wrong but I've spent the 
>> entire day working like this with every single step having some kind of 
>> problem and our IT support service is also struggling to see why it's 
>> having so many issues. 
>> Anyone able to guide us through in a simpler way, enlighten me past this 
>> step and onto the next error or should I give up on Arches now seeing as 
>> it's taken me a day and I can't even install it, yet alone set it up or 
>> operate it?
>>
>> Thanks,
>>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@google

Re: [Arches] Re: Proper procedure to close and open server on Ubuntu

[couimet . hcd]

Thanks Cyrus,

I was able to get the maps working, and I'm experimenting with adding 
resources. The issue now is that when doing this, the browser (Firefox) 
starts taking lots of RAM (all of the dedicated 10GB that I increased to on 
the VM), and some for Java (a constant 2.4GB). This is especially evident 
when modifying a resource, and the browser becomes unworkable for a few 
minutes. The maps do not seem to be the culprit, since I experimented with 
it on and off.

ElasticSearch seems to now be working fine when re-starting the VM.

Thanks for your help.

Christian


On Saturday, April 13, 2019 at 8:22:35 AM UTC-4, Cyrus Hiatt wrote:
>
> Hi Christian - 
>
> I generally run elasticsearch with the `-d` option so that it runs as a 
> daemon. This allows me to close the terminal and shut down the machine on 
> which ES is running and later resume without any additional steps. Other 
> than that there really are no special steps that need to be taken to shut 
> down Arches. The error that you got seems to be an issue with virtualenv. 
> Once you pip install arches, arches and its Python dependencies (including 
> Django) should be installed in your virtualenv and be available regardless 
> of how you stop arches or shutdown your server.  So, I'm not sure what went 
> wrong to cause the error you saw, and I'm sorry it resulted in you having 
> to reinstall everything.  Hopefully it doesn't happen again, but I would 
> take a snapshot of my VM before shutting down, just in case it does.
>
> Regarding your map issue, getting a mapbox API key and adding it to your 
> system settings should resolve that issue.
>
> Cheers -
>
> Cyrus
>
>
>
> On Fri, Apr 12, 2019 at 6:29 PM > wrote:
>
>> I think I found the solution as follows, after starting from scratch with 
>> a complete reinstall.
>>
>> For both elasticsearch and runserver, prior to shutting down Ubuntu, I 
>> quit them in their respective terminal windows with Control-C. 
>>
>> Is there still a solution to the error I received, in the event that the 
>> operating system would crash without the opportunity to close elasticsearch 
>> and runserver with Control-C.
>>
>> I'm now onto the next steps, and just loaded the branch.zip package. This 
>> seems to be working with the exception of the maps. But I think I need to 
>> do some reading regarding this under Configuring Settings section which 
>> talks about providing a key.
>>
>> Thanks,
>>
>> Christian
>>
>> On Friday, April 12, 2019 at 9:48:56 AM UTC-4, couim...@gmail.com wrote:
>>>
>>> Hello,
>>>
>>> I was able to successfully install Arches on a virtual machine 
>>> (VirtualBox) running Ubuntu!
>>>
>>> I was able to run ElasticSearch, run the Development Server and view the 
>>> default Arches setup in a web browser via localhost:8000
>>>
>>> I closed everything down (Virtualmachine), and am now attempting to 
>>> reactivate the ElasticSearch and Development Server. I was able to 
>>> run/reactivate ElasticSearch, then I opened a new terminal window, and ran 
>>> (in the virtual ENV) "python manage.py runserver" but this seems to not 
>>> be working, with the following message:
>>>
>>>
>>> Traceback (most recent call last):
>>>   File "manage.py", line 27, in 
>>> from django.core.management import execute_from_command_line
>>> ImportError: No module named django.core.management
>>>
>>> Any help would be appreciated.
>>>
>>> Also, is there a procedure or best practice to follow when closing and 
>>> re-opening elasticsearch and/or the server? I also want to make sure I'm 
>>> not running things twice and create conflicts.
>>>
>>> Thanks,
>>>
>>> Christian
>>>
>>> -- 
>> -- To post, send email to arches...@googlegroups.com . To 
>> unsubscribe, send email to arches...@googlegroups.com . 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 arches...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Arches] Re: Proper procedure to close and open server on Ubuntu

[Cyrus Hiatt]

Hi Christian -

I generally run elasticsearch with the `-d` option so that it runs as a
daemon. This allows me to close the terminal and shut down the machine on
which ES is running and later resume without any additional steps. Other
than that there really are no special steps that need to be taken to shut
down Arches. The error that you got seems to be an issue with virtualenv.
Once you pip install arches, arches and its Python dependencies (including
Django) should be installed in your virtualenv and be available regardless
of how you stop arches or shutdown your server.  So, I'm not sure what went
wrong to cause the error you saw, and I'm sorry it resulted in you having
to reinstall everything.  Hopefully it doesn't happen again, but I would
take a snapshot of my VM before shutting down, just in case it does.

Regarding your map issue, getting a mapbox API key and adding it to your
system settings should resolve that issue.

Cheers -

Cyrus



On Fri, Apr 12, 2019 at 6:29 PM  wrote:

> I think I found the solution as follows, after starting from scratch with
> a complete reinstall.
>
> For both elasticsearch and runserver, prior to shutting down Ubuntu, I
> quit them in their respective terminal windows with Control-C.
>
> Is there still a solution to the error I received, in the event that the
> operating system would crash without the opportunity to close elasticsearch
> and runserver with Control-C.
>
> I'm now onto the next steps, and just loaded the branch.zip package. This
> seems to be working with the exception of the maps. But I think I need to
> do some reading regarding this under Configuring Settings section which
> talks about providing a key.
>
> Thanks,
>
> Christian
>
> On Friday, April 12, 2019 at 9:48:56 AM UTC-4, couim...@gmail.com wrote:
>>
>> Hello,
>>
>> I was able to successfully install Arches on a virtual machine
>> (VirtualBox) running Ubuntu!
>>
>> I was able to run ElasticSearch, run the Development Server and view the
>> default Arches setup in a web browser via localhost:8000
>>
>> I closed everything down (Virtualmachine), and am now attempting to
>> reactivate the ElasticSearch and Development Server. I was able to
>> run/reactivate ElasticSearch, then I opened a new terminal window, and ran
>> (in the virtual ENV) "python manage.py runserver" but this seems to not
>> be working, with the following message:
>>
>>
>> Traceback (most recent call last):
>>   File "manage.py", line 27, in 
>> from django.core.management import execute_from_command_line
>> ImportError: No module named django.core.management
>>
>> Any help would be appreciated.
>>
>> Also, is there a procedure or best practice to follow when closing and
>> re-opening elasticsearch and/or the server? I also want to make sure I'm
>> not running things twice and create conflicts.
>>
>> Thanks,
>>
>> Christian
>>
>> --
> -- To post, send email to archesproject@googlegroups.com. To unsubscribe,
> send email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.