Hello Alexei and Adam,

Thanks a lot for your suggestions. It was indeed an internal network access 
problem.
Now it seems that the next step would be installing Apache, hope we don't 
run in a lot of troubles when doing that.

And again loads of thanks for your efforts and support.

--
Sincerely,
Mai

On Wednesday, September 16, 2015 at 7:31:27 PM UTC+2, Alexei Peters wrote:
>
> Hi Mai,
> Just so you understand what happened.  When you initially installed pip it 
> was installed in the global python location.  From there you could install 
> virtualenv.  Virtualenv comes with it's own instance of pip, so that when 
> you create a virtualenv you can pip install from an activated environment.
> To install arches you need to run the pip install arches command from the 
> activated environment.
>
> As far as using the runserver command goes, I'd first try running it from 
> the default ip to see if that works.  You simply need to run this:
> python manage.py runserver
>
> The site should then be accessable from:
> http://localhost:8000
>
> Try that a see if that works.  If it does that would lead me to believe 
> there's an issue with the routing of the ip to the dev server that comes 
> with django.
> For production you should use apache to host you app.
>
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Tue, Sep 15, 2015 at 6:11 AM, Mai Abdelaziz El Kady <
> [email protected] <javascript:>> wrote:
>
> Hi Alexei,
>
> Apparently I ended up using the pip installation that was outside the 
> virtual environment, so arches was installed outside it as well. After 
> using the proper pip, I've got Arches-hip in the right place and after 
> troubleshooting some more psql related errors, the command "python 
> manage.py packages -o install" seems to run fine without any errors. so 
> Thanks a zillion for your continued help and support!! we really appreciate 
> it.
> Now I think we're almost there, we are running this command:
>  "python manage.py runserver 12.*.*.*:**" 
> and it runs fine on a terminal returning zero errors and saying "Starting 
> development server at http://12.*.*.*:**/";, however when opening "
> http://12.*.*.* : **/" in a browser, we get a message that the page is 
> not available. So do you have any idea what could have gone wrong?
>
> Thanks a lot
>
>
>
> On Mon, Sep 14, 2015 at 6:57 PM, Alexei Peters <[email protected] 
> <javascript:>> wrote:
>
> Hi Mai,
> Wow this is really baffling!  
>
> Just to confirm the steps you took to install arches from a clean machine 
> (generally):
>
>    1. Install pip
>    2. pip install virtualenv
>    3. $ virtualenv ENV
>    4. $ source ENV/bin/activate
>    5. (ENV)$ pip install arches_hip
>    
> After doing that, you said that you have arches and arches_hip directories 
> in the default python location?  Is that true?
>
> -Alexei
>
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Mon, Sep 14, 2015 at 12:32 AM, Mai Abdelaziz El Kady <
> [email protected] <javascript:>> wrote:
>
> Hi Alexei,
>
> Actually, I used pip install arches_hip
>
> Thanks
>
>
> On Sun, Sep 13, 2015 at 7:54 PM, Alexei Peters <[email protected] 
> <javascript:>> wrote:
>
> Hi Mai,
> Did you pip install arches, or arches-hip?
> From the looks of the error message arches-hip isn't installed.
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Sun, Sep 13, 2015 at 1:50 AM, <[email protected] <javascript:>> 
> wrote:
>
> Hi Adam and Alexei,
>
> We have decided to start a clean installation of Arches on a new sever, we 
> are now installing it on Red Hat Enterprise Linux Server release 6.7.
> There are good news and bad news, the bad news is that we got a brand new 
> error message when running:  python manage.py packages -o install from 
> the virtual environment, the error is listed below. 
> The good news is that the error message refers to the python that is in 
> the virtual environment not outside it and when running which python, it 
> refers to the one inside the virtual environment 
> (/projects/ENV/bin/python). However, arches and arches-hip still have 
> directories in (/usr/local/lib/python2.7/site-packages/) and what I got 
> from Alexei's reply is that this is not okay. So should I try uninstalling 
> it again or not. Should these arches directories be in 
> (/projects/ENV/lib/python2.7/site-packages/) instead, for it to function 
> correctly?
>
> The new error that we get is:
> Traceback (most recent call last):
>   File "manage.py", line 28, in <module>
>     execute_from_command_line(sys.argv)
>   File 
> "/opt/projects/ENV/lib/python2.7/site-packages/django/core/management/__init__.py",
>  
> line 338, in execute_from_command_line
>     utility.execute()
>   File 
> "/opt/projects/ENV/lib/python2.7/site-packages/django/core/management/__init__.py",
>  
> line 303, in execute
>     settings.INSTALLED_APPS
>   File 
> "/opt/projects/ENV/lib/python2.7/site-packages/django/conf/__init__.py", 
> line 48, in __getattr__
>     self._setup(name)
>   File 
> "/opt/projects/ENV/lib/python2.7/site-packages/django/conf/__init__.py", 
> line 44, in _setup
>     self._wrapped = Settings(settings_module)
>   File 
> "/opt/projects/ENV/lib/python2.7/site-packages/django/conf/__init__.py", 
> line 92, in __init__
>     mod = importlib.import_module(self.SETTINGS_MODULE)
>   File "/usr/local/lib/python2.7/importlib/__init__.py", line 37, in 
> import_module
>     __import__(name)
>   File "/opt/projects/my_hip_app/my_hip_app/settings.py", line 3, in 
> <module>
>     from arches_hip.settings import *
> ImportError: No module named arches_hip.settings
>  
> Once again, Thanks a lot for your continued help and support.
>
> --
> Sincerely,
> Mai Abdelaziz
>
>
> On Wednesday, September 9, 2015 at 6:52:59 PM UTC+2, Alexei Peters wrote:
>
> Hi Mai,
> It looks like you have 'arches' installed in the default python location 
> (at /usr/lib/python2.7/site-packages/).  Maybe you installed arches there 
> first before realizing that you needed to use a virtual environment.
> I would try un-installing "arches' from the default python instance.
>
> Open a new terminal window and make sure the virtual environment IS NOT 
> activated.
> run the command "pip uninstall arches"
>
> Go to /usr/lib/python2.7/site-packages/ and confirm that the arches 
> directory is gone (if not you can simply delete it).
> I'd also recommend uninstalling all the arches dependencies (found in 
> arches/arches/install/requirements.txt)
>
> Once you've done that, re-activate your virtualenv and try running 
>
> *python manage.py packages -o install*
>
>
> Let us know if that helps.
> Cheers,
> Alexei 
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Tue, Sep 8, 2015 at 10:47 AM, Adam Cox <[email protected]> wrote:
>
> Hello Mai, it still bothers me that your error messages were coming from 
> python files that were not within your virtual environment, but in the 
> default python installation instead (even though I can see that you had the 
> virtual environment activated).  The last error message you sent looked 
> like you were using CentOS.  CentOS 7 ships with Python 2.7.5 (as you can 
> see here <http://mirror.centos.org/centos/7/os/x86_64/Packages/>), but 
> Arches needs Python 2.7.6.  I'm unclear what problems that version 
> difference may cause, but this may be one of them.  While your virtual 
> environment is activated, try *python --version *and *which python *to 
> see what version of Python you are running and where it is located.
>
> I know this is kind of a step behind the other troubleshooting you've been 
> doing, but it may be worth checking out.
>
> Adam
>
> On Thursday, September 3, 2015 at 3:15:12 AM UTC-5, Mai Abdelaziz El Kady 
> wrote:
>
> Hi Alexei,
>
> I am sorry about the delayed response.
> I am stumped as well, I have tried your last suggestion and the results 
> were the same.
> When accessing psql through a terminal we found that the table concepts is 
> created and there are even values in it!
> We tried selecting from it using the command "SELECT * FROM 
> concepts.concepts;" and it did return some values, 
> However when we tried "SELECT * FROM concepts;" the previous error was 
> shown; that is "relation concepts does not exist".
> Now I am not an experienced psql user but isn't there a search path that 
> should be checked by sql in case the schema is omitted?
> Do you think this has anything to do with the problem that we're facing?
> One last thing, do you know where the errors are logged in Arches?
>
> Thanks a lot for your tremendous help!
>
> --
> Sincerely,
> Mai Abdelaziz 
>
>
> On Thu, Aug 27, 2015 at 9:52 PM, Alexei Peters <[email protected]> wrote:
>
> Hi Mai,
> I'm a bit stumped!  Every time I've seen an error like 
> "django.db.utils.ProgrammingError: 
> relation "concepts" does not exist" it invariably means that the table 
> hasn't been created or is somehow inaccessible.
>
> My only other suggestion would be to change your db settings to this and 
> test again:
>
> DATABASES = {
>     'default': {
>    'ENGINE': 'django.db.backends.postgresql_psycopg2',
>         'NAME': 'arches_%s' % (PACKAGE_NAME),
>         'USER': 'd********',
>         'PASSWORD': '****',
>         'HOST': '127.0.0.1',
>         'PORT': '5432',
>    'POSTGIS_TEMPLATE' : 'template_postgis'
>     }
> }
>
> See if that works.
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Thu, Aug 27, 2015 at 5:51 AM, Mai Abdelaziz El Kady <
> [email protected]> wrote:
>
> Hi Alexei,
>
> Thanks for your suggestions.
> I have tried loading the system using the "postgres" user and checked that 
> there is indeed a scheme called "concepts", and within it a table called 
> "concepts" as well (shown in the screenshot attached), and yet still the 
> same error remains unchanged. 
>
> I really appreciate your help.
>
> --
> Sincerely,
> Mai Abdelaziz
>
> On Wed, Aug 26, 2015 at 6:39 PM, Alexei Peters <[email protected]> wrote:
>
> Hi Mai,
> It appears that your database called "arches_my_hip_app" wasn't installed 
> correctly.  If you have pgadmin3 or access to a terminal can you confirm 
> that you have a schema called "concepts" and within that a table called 
> "concepts".
> Your database user "django" needs to have the privilege to create tables, 
> functions, etc..  Can you confirm that as well.  As a test you might 
> temporarily load the system using the "postgres" user.
> Thanks,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Wed, Aug 26, 2015 at 12:43 AM, 'Mai Abdelaziz El Kady' via Arches 
> Project <[email protected]> wrote:
>
> Hi Cyrus,
>
> My name is Mai and I am working with Asmaa in installing Arches.
> Thank you for your quick reply.
> We tried your suggestion but unfortunately the error remained the same, so 
> do you have any more ideas about what could be the cause of it?
>
> Thanks a lot for your help and support
>
> --
> Sincerely,
> Mai Abdelaziz
>
>
> On Mon, Aug 24, 2015 at 5:01 PM, Cyrus Hiatt <[email protected]> wrote:
>
> Hi Asmaa - 
>
> Glad to hear you got a bit further.
>
> Sorry I didn't catch this last time, but I see that the paths (e.g. 
> 'os.path....') in: RESOURCE_GRAPH_LOCATIONS, CONCEPT_SCHEME_LOCATIONS, and 
> BUSINESS_DATA_FILES have been uncommented. You should try commenting those 
> lines back out again until you are ready to modify or add to the files in 
> those directories. The settings for those variables should look like this: 
>
>
> # RESOURCE_GRAPH_LOCATIONS = (
> #     # Put strings here, like "/home/data/resource_graphs" or 
> "C:/data/resource_graphs".
> #     # Always use forward slashes, even on Windows.
> #     # Don't forget to use absolute paths, not relative paths.
> #     os.path.join(PACKAGE_ROOT, 'source_data', 'resource_graphs'),
> # )
>
> CONCEPT_SCHEME_LOCATIONS = (
>     # Put strings here, like "/home/data/authority_files" or 
> "C:/data/authority_files".
>     # Always use forward slashes, even on Windows.
>     # Don't forget to use absolute paths, not relative paths.
>     
>     #'absolute/path/to/authority_files',
>     # os.path.normpath(os.path.join(PACKAGE_ROOT, 'source_data', 
> 'concepts', 'authority_files')),
> )
>
> BUSISNESS_DATA_FILES = (
>     # Put strings here, like "/home/html/django_templates" or 
> "C:/www/django/templates".
>     # Always use forward slashes, even on Windows.
>     # Don't forget to use absolute paths, not relative paths.
>     # os.path.normpath(os.path.join(PACKAGE_ROOT, 'source_data', 
> 'business_data', 'sample.arches')),
> )
>
>
>
> Cheers,
>
> Cyrus
>
> On Mon, Aug 24, 2015 at 3:18 AM, Asmaa Ayman <[email protected]> wrote:
>
> Hi Cyrus,
>
> Thanks a lot for the help! We did what you said and it passed that error 
> but now we are facing this one: 
>
> django.db.utils.ProgrammingError: relation "concepts" does not exist
> LINE 1: ...concepts"."nodetype", "concepts"."legacyoid" FROM "concepts"...
>
> You can find below a more informative log, and I am also attaching the 
> entire log.
>
>
> LOADING GRAPHS 
> (/usr/share/sandboxes/egyarch/my_hip_app/my_hip_app/source_data/resource_graphs)
> ---------------
>
> INDEXING ENTITY NODES
> ---------------------
> Traceback (most recent call last):
>   File "manage.py", line 28, in <module>
>     execute_from_command_line(sys.argv)
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
> 399, in execute_from_command_line
>     utility.execute()
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
> 392, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 242, in run_from_argv
>     self.execute(*args, **options.__dict__)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 285, in execute
>     output = self.handle(*args, **options)
>   File 
> "/usr/lib/python2.7/site-packages/arches/management/commands/packages.py", 
> line 67, in handle
>     self.install(package_name)
>   File 
> "/usr/lib/python2.7/site-packages/arches/management/commands/packages.py", 
> line 114, in install
>     install()
>   File "/usr/share/sandboxes/egyarch/my_hip_app/my_hip_app/setup.py", line 
> 6, in install
>     setup.install()
>   File "/usr/lib/python2.7/site-packages/arches_hip/setup.py", line 24, in 
> install
>     load_resource_graphs()
>   File "/usr/lib/python2.7/site-packages/arches_hip/setup.py", line 47, in 
> load_resource_graphs
>     resource_graphs.load_graphs(break_on_error=True)
>   File 
> "/usr/lib/python2.7/site-packages/arches/management/commands/package_utils/resource_graphs.py",
>  
> line 69, in load_graphs
>     concepts.index_entity_concept_lables()
>   File 
> "/usr/lib/python2.7/site-packages/arches/management/commands/package_utils/concepts.py",
>  
> line 17, in index_entity_concept_lables
>     domains_concept = Concept('00000000-0000-0000-0000-000000000003')
>   File "/usr/lib/python2.7/site-packages/arches/app/models/concept.py", 
> line 60, in __init__
>     self.get(args[0])
>   File "/usr/lib/python2.7/site-packages/arches/app/models/concept.py", 
> line 97, in get
>     self.load(models.Concepts.objects.get(pk=id))
>   File "/usr/lib/python2.7/site-packages/django/db/models/manager.py", 
> line 151, in get
>     return self.get_queryset().get(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 
> 304, in get
>     num = len(clone)
>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 
> 77, in __len__
>     self._fetch_all()
>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 
> 857, in _fetch_all
>     self._result_cache = list(self.iterator())
>   File "/usr/lib/python2.7/site-packages/django/db/models/query.py", line 
> 220, in iterator
>     for row in compiler.results_iter():
>   File 
> "/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 
> 713, in results_iter
>     for rows in self.execute_sql(MULTI):
>   File 
> "/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 
> 786, in execute_sql
>     cursor.execute(sql, params)
>   File "/usr/lib/python2.7/site-packages/django/db/backends/util.py", line 
> 69, in execute
>     return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/usr/lib/python2.7/site-packages/django/db/backends/util.py", line 
> 53, in execute
>     return self.cursor.execute(sql, params)
>   File "/usr/lib/python2.7/site-packages/django/db/utils.py", line 99, in 
> __exit__
>     six.reraise(dj_exc_type, dj_exc_value, traceback)
>   File "/usr/lib/python2.7/site-packages/django/db/backends/util.py", line 
> 53, in execute
>     return self.cursor.execute(sql, params)
> django.db.utils.ProgrammingError: relation "concepts" does not exist
> LINE 1: ...concepts"."nodetype", "concepts"."legacyoid" FROM "concepts"...
>                                                              ^
>
>
> I, my colleagues and everyone here at AUC really appreciate your help.
>
>
> All the best,
>
> Asmaa
>
>
>
> --
> Stay Focused. Stay Productive!
>
> On Sun, Aug 23, 2015 at 6:29 PM, Cyrus Hiatt <[email protected]> wrote:
>
> Hi Asmaa - 
>
> I see your RESOURCE_MODEL and RESOURCE_TYPE_CONFIGS are uncommented in 
> settings.py overriding the hip resource model. Could you re-comment them 
> and run the install command again?
>
> Thanks,
>
> Cyrus
>
> On Sun, Aug 23, 2015 at 8:13 AM, Asmaa Ayman <[email protected]> wrote:
>
> Hi Cyrus,
>
> I am using a different user and password, but all written in the 
> settings.py file. my postgis template database matches the one in the 
> settings.py file. It is 'template_postgis'. What do you advise. 
>
> I am attaching the entire output file, starting from the installation 
> command and including the error I am stuck at. Also attached the 
> settings.py file.
>
> I really appreciate your help!
>
> Thanks a lot,
>
> Asmaa
>
>
> --
> Stay Focused. Stay Productive!
>
> On Sun, Aug 23, 2015 at 4:30 PM, Cyrus Hiatt <[email protected]> wrote:
>
> Hi Asmaa - 
>
> Are you using the default user ('postgres') and password ('postgis') for 
> your postgres connection?  If so, does the name of your postgis template 
> database match what's in your Django database settings (probably 
> 'template_postgis_20'?
>
> Cheers,
>
> Cyrus
>
> On Sun, Aug 23, 2015 at 6:36 AM, 'Asmaa Ayman' via Arches Project <
> [email protected]> wrote:
>
> Dear Adam,
>
> Yes, we are using a virtual Environment and it was active, my colleague 
> followed the exact steps in the link you provided and still the error 
> remained unchanged.
>
>
> Your advice is highly appreciated!
>
> >>>
>
>
>
> On Wed, Aug 19, 2015 at 12:05 PM, Asmaa Ayman <[email protected]> wrote:
>
> Dear Mai,
>
> Kindly check the reply of Arches' Support. Can you please re-install 
> Arches again following the instructions sent
>
> Server: 10.2.2.33
> username: django
> pwd: AUC$123
>
> directory: /usr/share/sandboxes/egyarch
>
> you can download PuTTY from here: http://www.putty.org/
>
>
> Many thanks for your invaluable help and continuous support!
>
> Asmaa
>
> --
> Stay Focused. Stay Productive!
>
> On Mon, Aug 17, 2015 at 8:38 PM, Adam Cox <[email protected]> wrote:
>
> HI Asmaa, are you using a virtual environment?  It looks like you are 
> using the default python installation.  You should make a virtual 
> environment, activate it, and then install arches-hip there.  Here's more 
> information on that: 
> https://arches-hip.readthedocs.org/en/latest/getting-started/#installating-arches-hip
> .
>
> Good luck!
>
>
> On Sunday, August 16, 2015 at 10:59:07 AM UTC-5, [email protected] 
> wrote:
>
> Dear All,
>
> I am trying to install Arches-HIP and I am getting an error at the last 
> step before running arches: *(ENV)$ python manage.py packages -o install*
>
> I tried it on Centos 7 and on ubuntu, using the install dependencies 
> script; yet both give me the same error.
>
> *Centos 7*
> VACUUM
> deleting index : concept_labels
> deleting index : term
> Traceback (most recent call last):
>   File "manage.py", line 28, in <module>
>     execute_from_command_line(sys.argv)
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
> 399, in execute_from_command_line
>     utility.execute()
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
> 392, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 242, in run_from_argv
>     self.execute(*args, **options.__dict__)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 285, in execute
>     output = self.handle(*args, **options)
>   File 
> "/usr/lib/python2.7/site-packages/arches/management/commands/packages.py", 
> line 67, in handle
>     self.install(package_name)
>   File 
> "/usr/lib/python2.7/site-packages/arches/management/commands/packages.py", 
> line 114, in install
>     install()
>   File "/usr/share/sandboxes/Projects/my_hip_app/my_hip_app/setup.py", 
> line 6, in install
>     setup.install()
>   File "/usr/lib/python2.7/site-packages/arches_hip/setup.py", line 22, in 
> install
>     Resource().prepare_term_index(create=True)
>
> ...

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