search

archesproject / hip

Heritage inventory package for Arches
2 stars 2 forks source link

Crash suddenly occurring on Classification section #5

Open 1000camels opened 8 years ago

1000camels commented 8 years ago

I am getting an error suddenly because of the query when I try to load the Classification section. I suppose it could be a postgresql configuration issue, but nothing indicates this.

Here's the Postgresql Log:

< 2016-04-05 07:41:43.547 HKT >LOG: statement: WITH RECURSIVE children AS ( SELECT d.conceptidfrom, d.conceptidto, c2.value, c2.valueid as valueid, c.value as valueto, c.valueid as valueidto, c.valuetype as vtype, 1 AS depth, array[d.conceptidto] AS conceptpath, array[c.valueid] AS idpath ---|NonRecursive Part FROM concepts.relations d JOIN concepts.values c ON(c.conceptid = d.conceptidto) JOIN concepts.values c2 ON(c2.conceptid = d.conceptidfrom) WHERE d.conceptidfrom = '5ff92cb0-df58-11e5-ae4b-179456d280d9' and c2.valuetype = 'prefLabel' and c.valuetype in ('prefLabel', 'sortorder', 'collector') and (d.relationtype = 'member' or d.relationtype = 'hasTopConcept') UNION SELECT d.conceptidfrom, d.conceptidto, v2.value, v2.valueid as valueid, v.value as valueto, v.valueid as valueidto, v.valuetype as vtype, depth+1, (conceptpath || d.conceptidto), (idpath || v.valueid) ---|RecursivePart FROM concepts.relations d JOIN children b ON(b.conceptidto = d.conceptidfrom) JOIN concepts.values v ON(v.conceptid = d.conceptidto) JOIN concepts.values v2 ON(v2.conceptid = d.conceptidfrom) WHERE v2.valuetype = 'prefLabel' and v.valuetype in ('prefLabel','sortorder', 'collector') and (d.relationtype = 'member' or d.relationtype = 'hasTopConcept') ) SELECT conceptidfrom, conceptidto, value, valueid, valueto, valueidto, depth, idpath, conceptpath, vtype FROM children ORDER BY depth, conceptpath;

< 2016-04-05 07:43:08.534 HKT >LOG: server process (PID 29550) was terminated by signal 9: Killed < 2016-04-05 07:43:08.549 HKT >DETAIL: Failed process was running: WITH RECURSIVE children AS ( SELECT d.conceptidfrom, d.conceptidto, c2.value, c2.valueid as valueid, c.value as valueto, c.valueid as valueidto, c.valuetype as vtype, 1 AS depth, array[d.conceptidto] AS conceptpath, array[c.valueid] AS idpath ---|NonRecursive Part FROM concepts.relations d JOIN concepts.values c ON(c.conceptid = d.conceptidto) JOIN concepts.values c2 ON(c2.conceptid = d.conceptidfrom) WHERE d.conceptidfrom = '5ff92cb0-df58-11e5-ae4b-179456d280d9' and c2.valuetype = 'prefLabel' and c.valuetype in ('prefLabel', 'sortorder', 'collector') and (d.relationtype = 'member' or d.relationtype = 'hasTopConcept') UNION SELECT d.conceptidfrom, d.conceptidto, v2.value, v2.valueid as valueid, v.value as valueto, v.valueid as valueidto, v.valuetype as vtype, depth+1, (conceptpath || d.conceptidto), (idpath || v.valueid) ---|RecursiveP < 2016-04-05 07:43:08.549 HKT >LOG: terminating any other active server processes < 2016-04-05 07:43:08.614 HKT >WARNING: terminating connection because of crash of another server process < 2016-04-05 07:43:08.614 HKT >DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. < 2016-04-05 07:43:08.614 HKT >HINT: In a moment you should be able to reconnect to the database and repeat your command. < 2016-04-05 07:43:08.687 HKT >LOG: archiver process (PID 14458) exited with exit code 1 < 2016-04-05 07:43:08.687 HKT >LOG: all server processes terminated; reinitializing < 2016-04-05 07:43:08.782 HKT >LOG: database system was interrupted; last known up at 2016-04-05 03:35:03 HKT < 2016-04-05 07:43:08.890 HKT >LOG: database system was not properly shut down; automatic recovery in progress < 2016-04-05 07:43:08.895 HKT >LOG: record with zero length at 0/7F000090 < 2016-04-05 07:43:08.895 HKT >LOG: redo is not required < 2016-04-05 07:43:08.908 HKT >LOG: MultiXact member wraparound protections are now enabled < 2016-04-05 07:43:08.911 HKT >LOG: database system is ready to accept connections < 2016-04-05 07:43:08.912 HKT >LOG: autovacuum launcher started

apeters commented 8 years ago

Was this previously working? Did anything recently change with your data base or configuration?

Director of Web Development - Farallon Geographics, Inc. - 971.227.3173

On Mon, Apr 4, 2016 at 4:50 PM, Darcy W. Christ notifications@github.com wrote:

I am getting an error suddenly because of the query when I try to load the Classification section. I suppose it could be a postgresql configuration issue, but nothing indicates this.

Here's the Postgresql Log:

< 2016-04-05 07:41:43.547 HKT >LOG: statement: WITH RECURSIVE children AS ( SELECT d.conceptidfrom, d.conceptidto, c2.value, c2.valueid as valueid, c.value as valueto, c.valueid as valueidto, c.valuetype as vtype, 1 AS depth, array[d.conceptidto] AS conceptpath, array[c.valueid] AS idpath ---|NonRecursive Part FROM concepts.relations d JOIN concepts.values c ON(c.conceptid = d.conceptidto) JOIN concepts.values c2 ON(c2.conceptid = d.conceptidfrom) WHERE d.conceptidfrom = '5ff92cb0-df58-11e5-ae4b-179456d280d9' and c2.valuetype = 'prefLabel' and c.valuetype in ('prefLabel', 'sortorder', 'collector') and (d.relationtype = 'member' or d.relationtype = 'hasTopConcept') UNION SELECT d.conceptidfrom, d.conceptidto, v2.value, v2.valueid as valueid, v.value as valueto, v.valueid as valueidto, v.valuetype as vtype, depth+1, (conceptpath || d.conceptidto), (idpath || v.valueid) ---|RecursivePart FROM concepts.relations d JOIN children b ON(b.conceptidto = d.conceptidfrom) JOIN concepts.values v ON(v.conceptid = d.conceptidto) JOIN concepts.values v2 ON(v2.conceptid = d.conceptidfrom) WHERE v2.valuetype = 'prefLabel' and v.valuetype in ('prefLabel','sortorder', 'collector') and (d.relationtype = 'member' or d.relationtype = 'hasTopConcept') ) SELECT conceptidfrom, conceptidto, value, valueid, valueto, valueidto, depth, idpath, conceptpath, vtype FROM children ORDER BY depth, conceptpath;

< 2016-04-05 07:43:08.534 HKT >LOG: server process (PID 29550) was terminated by signal 9: Killed < 2016-04-05 07:43:08.549 HKT >DETAIL: Failed process was running: WITH RECURSIVE children AS ( SELECT d.conceptidfrom, d.conceptidto, c2.value, c2.valueid as valueid, c.value as valueto, c.valueid as valueidto, c.valuetype as vtype, 1 AS depth, array[d.conceptidto] AS conceptpath, array[c.valueid] AS idpath ---|NonRecursive Part FROM concepts.relations d JOIN concepts.values c ON(c.conceptid = d.conceptidto) JOIN concepts.values c2 ON(c2.conceptid = d.conceptidfrom) WHERE d.conceptidfrom = '5ff92cb0-df58-11e5-ae4b-179456d280d9' and c2.valuetype = 'prefLabel' and c.valuetype in ('prefLabel', 'sortorder', 'collector') and (d.relationtype = 'member' or d.relationtype = 'hasTopConcept') UNION SELECT d.conceptidfrom, d.conceptidto, v2.value, v2.valueid as valueid, v.value as valueto, v.valueid as valueidto, v.valuetype as vtype, depth+1, (conceptpath || d.conceptidto), (idpath || v.valueid) ---|RecursiveP < 2016-04-05 07:43:08.549 HKT >LOG: terminating any other active server processes < 2016-04-05 07:43:08.614 HKT >WARNING: terminating connection because of crash of another server process < 2016-04-05 07:43:08.614 HKT >DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. < 2016-04-05 07:43:08.614 HKT >HINT: In a moment you should be able to reconnect to the database and repeat your command. < 2016-04-05 07:43:08.687 HKT >LOG: archiver process (PID 14458) exited with exit code 1 < 2016-04-05 07:43:08.687 HKT >LOG: all server processes terminated; reinitializing < 2016-04-05 07:43:08.782 HKT >LOG: database system was interrupted; last known up at 2016-04-05 03:35:03 HKT < 2016-04-05 07:43:08.890 HKT >LOG: database system was not properly shut down; automatic recovery in progress < 2016-04-05 07:43:08.895 HKT >LOG: record with zero length at 0/7F000090 < 2016-04-05 07:43:08.895 HKT >LOG: redo is not required < 2016-04-05 07:43:08.908 HKT >LOG: MultiXact member wraparound protections are now enabled < 2016-04-05 07:43:08.911 HKT >LOG: database system is ready to accept connections < 2016-04-05 07:43:08.912 HKT >LOG: autovacuum launcher started

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/archesproject/hip/issues/5

1000camels commented 8 years ago

Not that I know of. I am running two installations off of the same base. The other works fine.

1000camels commented 8 years ago

Is there an easy way to save out the data from arches_hip and rebuild the installation?

apeters commented 8 years ago

Hi Darcy, There is a way to do this.

  1. The steps would be to backup your database (all schema, etc..) to a postgres .backup file.
  2. Make a copy of the elasticsearch/elasticsearch-1.4.1/data directory
  3. Reinstall arches-hip
  4. Restore the database from the backup
  5. Run the management command from the command line: python manage.py packages -o index_database

I would highly recommend that before you do this you test this on a dev machine first to make sure this fixes the issue you're seeing.

Cheers, Alexei

Director of Web Development - Farallon Geographics, Inc. - 971.227.3173

On Mon, Apr 11, 2016 at 2:05 AM, Darcy W. Christ notifications@github.com wrote:

Is there an easy way to save out the data from arches_hip and rebuild the installation?

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/archesproject/hip/issues/5#issuecomment-208241948