Re: [Arches] Arches 5.0 Docker setup problems
Im going to guess that the elasticsearch container is not ready and the migration script fails when it attempts to run the first time through and Arches ends up in a bad state which it generally can never recover from. docker-compose down -v This will kill and delete all the badly formed docker containers created by a failed initial run. docker-compose up --no-start This will initialize the containers and network for the stack. docker-compose start elasticsearch db This will start the elasticsearch instance and the database. docker logs -f elasticsearch This will let you watch what it is doing. Ctrl-c to get back to normal. I've found that if you run antivirus checkers and have some network slowness, it can take a while (30s to 1min) for elasticsearch to actually be ready. It sadly lies on its health check command and reports "green" while it is still doing its random clustering things. docker-compose up After elasticsearch has finished doing whatever it does on start up that takes so long, run this and watch to make sure there are no connection errors. Ben On Thu, 5 Mar 2020, 07:44 David Osborne, wrote: > Thanks, Ben: your comment helped me make some progress (to another error > ;-) > > The problem is that the Readme.md in the docker directory of the Github > archesproject/arches repo (file last revised 17 months ago!) is inaccurate > or vague when it says "Create a new folder for your custom Arches code" > without specifying where. I created one alongside my cloned arches repo, > with the result that the path to /docker-entrypoint-initdb.d/init.sql did > not exist, so Docker created directories instead. > > Having located the arches/install/init-unix.sql file referred to in the db > service, I worked out that it's easiest to run docker-compose in the cloned > arches directory itself, so I edited the docker-compose.yml file, and that > file and the resulting output from docker-compose is in > https://gist.github.com/daosborne/bc83812e33d9396d679af54f31565895 (with > the lines from couchdb and elasticsearch edited out from the docker-compose > log as not relevant). > > It gets further but has some problems (partly because I want the default > graphs and concepts installed): > >1. error setting up db (traceback starting line 133) >2. database tables graphs, ontologies, concepts, d_value_types don't >exist (lines 222--648) >3. db connection error during migrations (line 734) >4. db column nodes.fieldname doesn't exist (lines 1123, 1185) > > I had also tried setting a project name, as suggested in the Readme but > abandoned that because the directory was missing from /web_root (and > produces a spurious error message about the project name clashing with a > Python module). > > I hoped that using Docker would be a quick and easy way of getting a new > Arches installation running but it seems it still has some rough edges. As > I need to get some development done to make some slides for a conference > paper, I think I'll go back to the tried and tested method of setting up a > Vagrant VM! > > Cheers > David > > On Wednesday, 4 March 2020 00:33:38 UTC, Ben O'Steen wrote: >> >> Hi, >> >> I think the key error is on line 63 of the gist you posted. For some >> reason, it is interpreting file bind mount as a directory and not as a >> file. If I run the default docker compose file here, and start up the db >> container, this is the log output I get: >> >> $ docker logs db >> Add rule to pg_hba: 0.0.0.0/0 >> Add rule to pg_hba: replication replicator >> Setup master database >> 2020-03-04 00:28:12.848 UTC [25] LOG: starting PostgreSQL 12.1 (Debian >> 12.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) >> 8.3.0, 64-bit >> 2020-03-04 00:28:12.849 UTC [25] LOG: listening on IPv4 address >> "127.0.0.1", port 5432 >> 2020-03-04 00:28:12.855 UTC [25] LOG: listening on Unix socket >> "/var/run/postgresql/.s.PGSQL.5432" >> 2020-03-04 00:28:12.928 UTC [36] LOG: database system was shut down at >> 2019-12-03 16:35:30 UTC >> 2020-03-04 00:28:12.931 UTC [37] postgres@postgres FATAL: the database >> system is starting up >> psql: error: could not connect to server: FATAL: the database system is >> starting up >> 2020-03-04 00:28:12.948 UTC [25] LOG: database system is ready to accept >> connections >> List of databases >>Name| Owner | Encoding | Collate | Ctype | Access privileges >> >> ---+--+--+-+-+--- >> postgres | postgres | UTF8 | C.UTF-8 | C.UTF-8 | >> template0 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres >>+ >>| | | | | >> postgres=CTc/postgres >> template1 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres >>+ >>| | | | | >> postgres=CTc/postgres >> (3 rows) >> >> postgres ready >> Setup postgres User:Password >> Creating superuser
[Arches] Map overlay
Dear all, I have been informed by several people that it is possible to add a rectified geoTIFF as a map overlay in Arches, but I have failed to find how to do this. Is there a guide that I haven't found, or is this a more esoteric issue? I have a site-plan (georeffed in WGS84) of a particular archaeological site, and we would need it as the local basemap showing where specific archaeological finds have been found. Robin -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/archesproject/5770137b-e27c-4e9b-a626-ffe1756d042c%40googlegroups.com.
[Arches] Re: Arches Newbie: Introduction and problems
Dear Annabel, I realised I hadn't replied to this, but I just wanted to thank you for you reply. All worked out, except for the basemap zoom problem, which only got solved by the upgrade to version 5. Best, Robin Den onsdag 12 februari 2020 kl. 04:10:53 UTC+2 skrev Annabel Enriquez: > > Hello Robin, > > First of all welcome to the Arches community! > > In regards to your first issue, I'd like to direct you to this forum > thread: > https://groups.google.com/forum/#!searchin/archesproject/resource$20descriptors%7Csort:date/archesproject/zrG_hBA17yE/AjKo8QKHAQAJ > While > this is referring to an implementation of Arches v4, the Resource > Descriptor function in v5 will still help you in defining what nodes carry > the display name and display descriptions for each of your resource models. > > In regards to modeling in general, I wanted to let you know that members > of the Arches team and community are working on providing more > documentation and tools to help Arches implementors, like yourself, create > or leverage existing CIDOC CRM-compliant resource models to serve their > individual use cases. We are hoping on making this available within the > next couple months. In addition, Part 3 of the Intro the Arches Platform > webinar series will have a basic overview of the modeling process as well > as an introduction to the documentation and tools that I just mentioned. > This webinar will take place at some point in the spring. In the meantime, > the past webinars might interest you: > https://www.archesproject.org/videos/ > > In regards to your issue regarding the basemap default zoom area, I > personally don't have an answer, but hope that someone else will chime in > in regards to that soon. > > Thanks! > > Annabel > The Arches team > > > > On Monday, February 10, 2020 at 9:58:22 AM UTC-8, Robin Rönnlund wrote: >> >> Dear all, >> >> My name is Robin Rönnlund and I'm an archaeologist working for the >> Swedish Archaeological Institute in Athens, Greece. Currently, I'm employed >> in an ambitious project aiming at digitising (and publish online) >> archaeological artifacts from Swedish excavations in Greece, Italy and >> Turkey, and we (the project team) have decided to use Arches for this >> purpose. So far, I have tried to get into CIDOC-CRM (+ CRMarchaeo) to see >> how we should map the already extant databases, but now I have also started >> to delve into Arches itself. >> >> Having never worked with this system before, I am somewhat struggling >> with the implementation. Not to list all of them at once, I will start with >> some of the more pressing ones, and if someone has an idea how to solve >> them, I'd be more than grateful! >> >> First, as there are no "preset" resource models even close to what we >> need for the project, I have tried to make my own with various levels of >> success. The biggest problem right now is that whatever I do, all added >> resources (including ones made with the Lincoln "preset" resource models) >> are listed as "(undefined)". Only in one case, a dummy resource model >> without any complex structure, does the string value of *E19 + P45 + E57* >> turn up as the "definition" of a resource entry. When I try to add this to >> another resource model, it doesn't work, for some reason. As all generated >> resources are listed as "(undefined)", I cannot tell which resource is what >> and everything looks incomprehensible. What governs the "definition" of a >> resource, and why isn't it working in the same way in two parallel cases? >> >> Second, I have tried to modify the basemap default zoom area, which was >> by default set to Lincoln. Modifying this makes that my browser (Firefox, >> Chrome) instantly crashes as soon as I go to the search page. I had to >> remove the project extent to get it working again, which is not ideal as >> now I always have to start in the Atlantic ocean. What to do with this? >> >> I hope someone can help me with this! >> >> All my very best, >> >> Robin >> > -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/archesproject/44f55ad3-a125-462e-838c-5d815a5d60fc%40googlegroups.com.
Re: [Arches] Arches 5.0 Docker setup problems
Thanks, Ben: your comment helped me make some progress (to another error ;-) The problem is that the Readme.md in the docker directory of the Github archesproject/arches repo (file last revised 17 months ago!) is inaccurate or vague when it says "Create a new folder for your custom Arches code" without specifying where. I created one alongside my cloned arches repo, with the result that the path to /docker-entrypoint-initdb.d/init.sql did not exist, so Docker created directories instead. Having located the arches/install/init-unix.sql file referred to in the db service, I worked out that it's easiest to run docker-compose in the cloned arches directory itself, so I edited the docker-compose.yml file, and that file and the resulting output from docker-compose is in https://gist.github.com/daosborne/bc83812e33d9396d679af54f31565895 (with the lines from couchdb and elasticsearch edited out from the docker-compose log as not relevant). It gets further but has some problems (partly because I want the default graphs and concepts installed): 1. error setting up db (traceback starting line 133) 2. database tables graphs, ontologies, concepts, d_value_types don't exist (lines 222--648) 3. db connection error during migrations (line 734) 4. db column nodes.fieldname doesn't exist (lines 1123, 1185) I had also tried setting a project name, as suggested in the Readme but abandoned that because the directory was missing from /web_root (and produces a spurious error message about the project name clashing with a Python module). I hoped that using Docker would be a quick and easy way of getting a new Arches installation running but it seems it still has some rough edges. As I need to get some development done to make some slides for a conference paper, I think I'll go back to the tried and tested method of setting up a Vagrant VM! Cheers David On Wednesday, 4 March 2020 00:33:38 UTC, Ben O'Steen wrote: > > Hi, > > I think the key error is on line 63 of the gist you posted. For some > reason, it is interpreting file bind mount as a directory and not as a > file. If I run the default docker compose file here, and start up the db > container, this is the log output I get: > > $ docker logs db > Add rule to pg_hba: 0.0.0.0/0 > Add rule to pg_hba: replication replicator > Setup master database > 2020-03-04 00:28:12.848 UTC [25] LOG: starting PostgreSQL 12.1 (Debian > 12.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) > 8.3.0, 64-bit > 2020-03-04 00:28:12.849 UTC [25] LOG: listening on IPv4 address > "127.0.0.1", port 5432 > 2020-03-04 00:28:12.855 UTC [25] LOG: listening on Unix socket > "/var/run/postgresql/.s.PGSQL.5432" > 2020-03-04 00:28:12.928 UTC [36] LOG: database system was shut down at > 2019-12-03 16:35:30 UTC > 2020-03-04 00:28:12.931 UTC [37] postgres@postgres FATAL: the database > system is starting up > psql: error: could not connect to server: FATAL: the database system is > starting up > 2020-03-04 00:28:12.948 UTC [25] LOG: database system is ready to accept > connections > List of databases >Name| Owner | Encoding | Collate | Ctype | Access privileges > > ---+--+--+-+-+--- > postgres | postgres | UTF8 | C.UTF-8 | C.UTF-8 | > template0 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres > + >| | | | | > postgres=CTc/postgres > template1 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres > + >| | | | | > postgres=CTc/postgres > (3 rows) > > postgres ready > Setup postgres User:Password > Creating superuser postgres > ALTER ROLE > Creating replication user replicator > CREATE ROLE > postgres db already exists > List of databases >Name| Owner | Encoding | Collate | Ctype | Access privileges > > ---+--+--+-+-+--- > postgres | postgres | UTF8 | C.UTF-8 | C.UTF-8 | > template0 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres > + >| | | | | > postgres=CTc/postgres > template1 | postgres | UTF8 | C.UTF-8 | C.UTF-8 | =c/postgres > + >| | | | | > postgres=CTc/postgres > (3 rows) > > /docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init.sql > CREATE DATABASE > UPDATE 1 > You are now connected to database "template_postgis" as user "postgres". > CREATE EXTENSION > GRANT > GRANT > GRANT > CREATE EXTENSION > > 2020-03-04 00:28:16.764 UTC [25] LOG: received smart shutdown request > 2020-03-04 00:28:16.783 UTC [25] LOG: background worker "logical > replication launcher" (PID 44) exited with exit code 1 > 2020-03-04 00:28:16.791 UTC [39] LOG: shutting down >
