[Archivesspace_Users_Group] Error with Collection Organization tree in Public UI in 2.3.0

Wed Feb 7 17:57:38 EST 2018

Just an update. Rerunning the indexer *and* upping the memory assigned to the app (I gave it 8GB) seems to have sorted the initial issue in that the collection organization tree now draws as expected.

I still see the second 500 (the node error) that I mentioned when viewing the resource itself. Looks like that particular bit of code is firing for resources as well as AOs and is (perhaps?) flailing since resources aren't nodes.

Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, February 7, 2018 1:20 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error with Collection Organization tree in Public UI in 2.3.0

This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>
        Feedback<http://aka.ms/SafetyTipsFeedback>

Hi Mark-

That's what I'm in the middle of right now. I've also shut off our plugins - a few of which add to the indexer - in case that's complicating the issue.

What's puzzling is that a fresh install with minimal data - just one ead import and one hand created collection show similar/related(?) issues with fetching nodes.

Is there anything in the log that I should be looking for especially to let me know if the indexer is unhappy? I haven't seen the usual indexer failed type messages this time.

Thanks!

Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Mark Cooper <mark.cooper at lyrasis.org>
Sent: Wednesday, February 7, 2018 1:11 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error with Collection Organization tree in Public UI in 2.3.0

Hi Joshua,

I’ve seen that error — it’s complaining about data missing from Solr, but reindexing has always resolved it (so far). Try blowing away the contents of your data directory / Solr index and restart.

Mark

LYRASIS

On Feb 7, 2018, at 9:18 AM, Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu<mailto:Joshua.D.Shaw at dartmouth.edu>> wrote:

Hi Christine-

I'm seeing it with all published resources in our data - I'm using a clone of our production data currently at 1.5.3. The same data does not produce the error in 2.2.1, so its something different between the 2.2 series and 2.3 is my guess.

For what its worth, I spun up a new instance of 2.3.0 and imported some ead and created a completely new resource with ao children as well. While I'm not seeing that particular error in the clean instance of AS, I am now seeing a sporadic 500 error in the public frontend when attempting to fetch nodes. For example:

http://localhost:8081/repositories/2/resources/2/tree/node?node=/repositories/2/archival_objects/76

throws a 500. Stack trace

I, [2018-02-07T12:08:31.262675 #1055]  INFO -- : [999ef8d5-6081-43c1-9519-f3c1b63efbfa] Completed 500 Internal Server Error in 26ms
F, [2018-02-07T12:08:31.264174 #1055] FATAL -- : [999ef8d5-6081-43c1-9519-f3c1b63efbfa]
F, [2018-02-07T12:08:31.264402 #1055] FATAL -- : [999ef8d5-6081-43c1-9519-f3c1b63efbfa] RecordNotFound (RecordNotFound):
F, [2018-02-07T12:08:31.264501 #1055] FATAL -- : [999ef8d5-6081-43c1-9519-f3c1b63efbfa]
F, [2018-02-07T12:08:31.264611 #1055] FATAL -- : [999ef8d5-6081-43c1-9519-f3c1b63efbfa] app/services/archives_space_client.rb:86:in `get_raw_record'
[999ef8d5-6081-43c1-9519-f3c1b63efbfa] app/controllers/resources_controller.rb:216:in `tree_node'

Thanks!
Joshua
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>>
Sent: Wednesday, February 7, 2018 12:12:04 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error with Collection Organization tree in Public UI in 2.3.0

Hi Joshua,

Just to clarify – are you seeing this with one particular resource record since upgrading, or with your resource records in general?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

<image001.jpg>

<image002.png>
             Applications are now open for the 2018 Catalyst Fund<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lyrasis.org%2FLeadership%2FPages%2FCatalyst-Fund.aspx&data=02%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C877e0da9e68d41b4624808d56e4debfe%7C6359f5dafcc84832ac9d0cb7b2d9e6d1%7C0%7C0%7C636536203319295395&sdata=LdVdoznbFAhyNYOK0KP23wt4E1UKGh3tacXP8jcuCvQ%3D&reserved=0>

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] On Behalf Of Joshua D. Shaw
Sent: Wednesday, February 7, 2018 11:52 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Error with Collection Organization tree in Public UI in 2.3.0

This appears to be an issue with updating/migrating from an older version - perhaps a data issue - as I don't see this problem after spinning up a new empty instance.
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu<mailto:Joshua.D.Shaw at dartmouth.edu>>
Sent: Tuesday, February 6, 2018 5:32:54 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Error with Collection Organization tree in Public UI in 2.3.0

This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing<http://aka.ms/LearnAboutSpoofing>

Feedback<http://aka.ms/SafetyTipsFeedback>

Hi All-

I've been testing the 2.3.0 release (and the RC) and noticed that in my local instance I'm getting a 500 when the app tries to draw the Collection Organization tree in the public UI for an archival object. The Collection Organization tab is also "disabled" - presumably because of the same issue - as I'm also seeing a 500 on rendering the resource in the public UI.

The stack trace is pretty unhelpful (see below). Anyone else seeing this behavior? I do not see this in 2.2.1, which does render the collection organization tree properly.

Thanks!
Joshua

-backend/log stack trace

I, [2018-02-06T17:16:59.359202 #3284]  INFO -- : [d831d9d3-3302-41de-8ddb-81d94d6db927] Completed 500 Internal Server Error in 34ms
F, [2018-02-06T17:16:59.362704 #3284] FATAL -- : [d831d9d3-3302-41de-8ddb-81d94d6db927]
F, [2018-02-06T17:16:59.362880 #3284] FATAL -- : [d831d9d3-3302-41de-8ddb-81d94d6db927] RecordNotFound (RecordNotFound):
F, [2018-02-06T17:16:59.363288 #3284] FATAL -- : [d831d9d3-3302-41de-8ddb-81d94d6db927]
F, [2018-02-06T17:16:59.363532 #3284] FATAL -- : [d831d9d3-3302-41de-8ddb-81d94d6db927] app/services/archives_space_client.rb:86:in `get_raw_record'
[d831d9d3-3302-41de-8ddb-81d94d6db927] app/controllers/resources_controller.rb:210:in `tree_root'

-Frontend stack trace
GET XHR http://localhost:8081/repositories/2/resources/1/tree/root
send http://localhost:8081/assets/application.js:3:30483<http://localhost:8081/assets/application-f62a0ab55845719a256b7ff2bb84f4ae5883927854d18c55e9a5ca8ba98e542e.js>
ajax http://localhost:8081/assets/application.js:3:27184<http://localhost:8081/assets/application-f62a0ab55845719a256b7ff2bb84f4ae5883927854d18c55e9a5ca8ba98e542e.js>
o.prototype.fetchRootNode http://localhost:8081/assets/largetree.js:1:9439<http://localhost:8081/assets/largetree-cec54e9841d383f055bbcd66b0a195c7706e2e7d13e7fc8863c5acd7ef1ba05c.js>
e.prototype.renderRoot http://localhost:8081/assets/largetree.js:1:6727<http://localhost:8081/assets/largetree-cec54e9841d383f055bbcd66b0a195c7706e2e7d13e7fc8863c5acd7ef1ba05c.js>
e http://localhost:8081/assets/largetree.js:1:540<http://localhost:8081/assets/largetree-cec54e9841d383f055bbcd66b0a195c7706e2e7d13e7fc8863c5acd7ef1ba05c.js>
<anonymous> http://localhost:8081/repositories/2/archival_objects/2:300:16<http://localhost:8081/repositories/2/archival_objects/2>
_______________________________________________
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://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7Cfcb3f9d611a646a50fe408d56e5635c2%7C6359f5dafcc84832ac9d0cb7b2d9e6d1%7C0%7C0%7C636536238900415411&sdata=FWGTquKHqYYCVUs8PRznzKREfNSqiQ4eiBzkDkM1gPw%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180207/348ea8ea/attachment.html>