[Archivesspace_Users_Group] Components not displaying in one of our repositories

Thu Nov 9 10:49:27 EST 2017

We seem to be experiencing this at Northwestern University too (on 2.1.2). Initially the cause was identified as a line break plugin we’d installed as part of our migration from Archon, but after removing that and correcting the underlying line break issue, the problem remains. Indexing seems to come to a halt right around repository 3 or 4 (of 9 total repositories), and won’t continue. As a result, all Resource records in the PUI after Repository 3 (our Music Library) are lacking the “Collection Organization” tab (we just get that circle/slash ghostbusters icon) and the “Container Inventory” tab displays top containers but no components within them.

Lisa, it’s pretty much the equivalent of what you’re seeing in this record: http://archivesspace.williams.edu:8081/repositories/4/resources/292

Here’s an example on our end: https://northwestern-staging-public.as.atlas-sys.com/repositories/6/resources/892

We haven’t run that NULL query Mark sent below, nor have we yet tried the steps Chris lays out in that Google group, so we’ll probably give those a try next.

Best,
--Benn

Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.joseph at northwestern.edu<mailto:benn.joseph at northwestern.edu%0d>
847.467.6581

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joanne Archer
Sent: Thursday, November 09, 2017 6:30 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Components not displaying in one of our repositories

Hi Lisa,

We are experiencing this problem at the University of Maryland as well. One of our developers, Chris, is working on it (see message above from Mark). He is making progress but it is not resolved yet. In my limited understanding of the issue it has to do with running out of heap space regularly which causes the indexer to loop and then crash. It also looks like Chris may have recently discovered a problem with jruby that is related to this issue.

We'll report back when we have more information.

Joanne

On Wed, Nov 8, 2017 at 3:46 PM, Conathan, Lisa <lc7 at williams.edu<mailto:lc7 at williams.edu>> wrote:
Thanks to Mark for the tips on this issue. We haven't been able to solve it. We tried running the query that Mark suggested and got a null response. The problem persists. Some, if not all, of the components display in the PUI, they just have no connection to their parent<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.williams.edu-3A8081_repositories_4_archival-5Fobjects_9109&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=2sN-ywVJ3a9K7-JBeG_IPOBSR3dgV-J1XphnzUq4DDw&s=k1s-2DZmUXDaXspOvwksQ3EZbrT8wC9DYiKa_ZrIUNQ&e=> collection. Anyone else who is facing this issue, please get in touch.

Lisa

+++++++++++++++++++++
Lisa Conathan
Head of Special Collections
Williams College Libraries
413-597-2930<tel:(413)%20597-2930>

On Mon, Nov 6, 2017 at 1:32 PM, Custer, Mark <mark.custer at yale.edu<mailto:mark.custer at yale.edu>> wrote:
Hi Lisa,

I’ve no clue what could be causing this, but others have reported the issue as well.  Hopefully the root cause of the issue can be identified with enough eyes on the problem.  So far, I haven’t seen this happen in Yale’s TEST PUI instance (on 2.1.2) or on our DEV instance (on version 20171105-1021).

Chris Fitzpatrick started a thread on the Apace Google Groups about this, though, which might be helpful:  https://groups.google.com/forum/#!topic/archivesspace/PhgUjukaNzQ<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_forum_-23-21topic_archivesspace_PhgUjukaNzQ&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=2sN-ywVJ3a9K7-JBeG_IPOBSR3dgV-J1XphnzUq4DDw&s=T02HRDPgZkUwYGhFSI4fR1Q3haFFWH38z-WNPDxs4Uo&e=>

My first inclination would be that things are stuck in an indexing loop (e.g. https://groups.google.com/d/msg/archivesspace/mRH_eCDHpwE/2fjb5EAfAgAJ<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msg_archivesspace_mRH-5FeCDHpwE_2fjb5EAfAgAJ&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=2sN-ywVJ3a9K7-JBeG_IPOBSR3dgV-J1XphnzUq4DDw&s=inKE91Aq3Hz4iO8idJML3jpummDjkdRrqr-QYfP0Qjg&e=>), but that could be completely wrong.  In any event, can you ask someone who has database access to run this query:

select * from archival_object where root_record_id is null;

If they get any results that way, that would cause an issue.

As for whey it would happen in just one repository, I believe that once the indexer gets stuck (and it goes through the record types one repository at a time, I think) then it just won’t ever get to the rest of the record types in that particular repository.  Some of the archival objects in this repository are indeed being indexed (e.g. http://archivesspace.williams.edu:8081/repositories/4/archival_objects/10484<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.williams.edu-3A8081_repositories_4_archival-5Fobjects_10484&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=2sN-ywVJ3a9K7-JBeG_IPOBSR3dgV-J1XphnzUq4DDw&s=xbAvLbQOFhGZ26KD_yoNyxhavkBnuTv-1-TUbDPXp6Y&e=>), but not completely, since this archival object doesn’t even know which collection it’s supposed to be part of.

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Conathan, Lisa
Sent: Monday, 06 November, 2017 1:12 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Components not displaying in one of our repositories

Hi everyone,

Williams College is running 2.2.0 and we have two repositories publishing to the PUI<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.williams.edu-3A8081_&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=JzBHIZxvRNvhkRySA5RldRIIZdP1kv2X96NkBAW8OIU&s=jAORfSXBDnqTaD_cf0ibihSXV3M8AJY0fAiK5Tt6Y4U&e=>. One repository is displaying resource records correctly, and the other<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.williams.edu-3A8081_repositories_4_resources-3F&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=JzBHIZxvRNvhkRySA5RldRIIZdP1kv2X96NkBAW8OIU&s=8vtBE8ji2nrH10jpy54p5xzHPpLvPeDnVVKE971Otdg&e=> is displaying only collection-level information (no collection organization, no container list on the right side of the screen). Components also do not display in the container inventory. We've double checked that everything is published, reindexed, and rebooted. We experienced this previously, and then the problem resolved with one of the patches, and now has re-appeared. Anyone know why we might be having this problem with just one of our repositories and what we might try to address it?

Lisa

+++++++++++++++++++++
Lisa Conathan
Head of Special Collections
Williams College Libraries
413-597-2930<tel:(413)%20597-2930>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=2sN-ywVJ3a9K7-JBeG_IPOBSR3dgV-J1XphnzUq4DDw&s=eI0_aGpBOii4VIFKlhQCtVCcljqAEqHyQbP_vPFAZ8Q&e=>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=2sN-ywVJ3a9K7-JBeG_IPOBSR3dgV-J1XphnzUq4DDw&s=eI0_aGpBOii4VIFKlhQCtVCcljqAEqHyQbP_vPFAZ8Q&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171109/18dd70e1/attachment.html>