Re: [Archivesspace_Users_Group] ASpace Website/URL setting(s)?

[Blake Carver]

The techdocs do have nginx settings here:
https://archivesspace.github.io/tech-docs/provisioning/https.html#Nginx

If something's not clear, let me know.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Sarah 
Frieldsmith 
Sent: Friday, May 20, 2022 5:57 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] ASpace Website/URL setting(s)?

Would really appreciate any help. First timer here. Set up database (MariaDB), 
set up tables, set up solr, and created the solr core. Ran the AS install and 
*can* successfully access ports via curl.

I don't know where to put our external URL information, so I can actually visit 
the site(s). In looking at other ASpace sites, none of them have "public" as 
part of their URL (per the tech-docs instructions).

We're using Ansible to control nginx. Our public URL is/should be:
archivesspace-2022.sandiego.edu
(I realize that's not ideal, but that is what has been assigned and I'm just 
trying to get ASpace going at this point.)

If anyone knows what should go in the config file and what needs to go to 
Ansible, I'd be super grateful!

Sarah Frieldsmith
Systems Librarian
University of San Diego
sfrieldsm...@sandiego.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ASpace Website/URL setting(s)?

[Sarah Frieldsmith]

Would really appreciate any help. First timer here. Set up database
(MariaDB), set up tables, set up solr, and created the solr core. Ran the
AS install and *can* successfully access ports via curl.

I don't know where to put our external URL information, so I can actually
visit the site(s). In looking at other ASpace sites, none of them have
"public" as part of their URL (per the tech-docs instructions).

We're using Ansible to control nginx. Our public URL is/should be:
archivesspace-2022.sandiego.edu
(I realize that's not ideal, but that is what has been assigned and I'm
just trying to get ASpace going at this point.)

If anyone knows what should go in the config file and what needs to go to
Ansible, I'd be super grateful!

*Sarah Frieldsmith*
*Systems Librarian*
University of San Diego
sfrieldsm...@sandiego.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Permission to Post to Archivesspace List

[Jessica Crouch]

Hi John,

Feel free to post any questions you have about getting started with 
ArchivesSpace. This group has a wealth of experience to draw from.

And as a reminder, all ArchivesSpace members are entitled to technical support, 
including support installing ArchivesSpace.  If you’d like to get a tech 
support ticket started, email the program team at 
archivesspaceh...@lyrasis.org.

Best,
Jessica

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org





From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of John 
Hawthorn 
Date: Friday, May 20, 2022 at 7:23 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Permission to Post to Archivesspace List
Just looking for permission to post to the list for queries on setting up 
Archivesspace server.  Thank you,

John Hawthorn
Systems Administrator

Mitchell College
437 Pequot Ave
New London, CT 06320-4498
(860)701-



[https://community.mitchell.edu/image/Mitchell_College_email_logo_7_2015.jpg]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

[Blake Carver]

It should look something like these  lines, where you should see "GET whatever" 
and then the crash is happening at the "GET"

I've found it usually happens around the archival objects so "GET 
/repositories/2/archival_objects" whatever and then FATAL or maybe ERROR

Sometimes running it 1x1 will cause it to stop crashing though. And on large 
sites it takes a heckuva long time to get through all the records.

, [2022-05-19T13:32:55.617646 #93541]  INFO -- : Thread-2952: Staff Indexer 
[2022-05-19 13:32:55 -0400] Indexed 1 records in 2 seconds
D, [2022-05-19T13:32:55.700686 #93541] DEBUG -- : Thread-2960: GET 
/repositories/2/digital_objects?all_ids=true_since=0 [session: 
#"search_indexer", :login_time=>2022-05-19 
13:32:52 -0400, :expirable=>false}, @system_mtime=2022-05-19 17:32:52 UTC, 
@id="238c65ef0b6ba04ccf6120ce85df6d8daa77135ec9a972eaca6deb521c74714b">]

I, [2022-05-19T13:32:57.817094 #93541]  INFO -- : Thread-2952: Staff Indexer 
[2022-05-19 13:32:57 -0400] Indexed 1 records in 1 seconds
D, [2022-05-19T13:32:57.899146 #93541] DEBUG -- : Thread-2960: GET 
/agents/people?all_ids=true_since=0 [session: #"search_indexer", :login_time=>2022-05-19 13:32:52 -0400, 
:expirable=>false}, @system_mtime=2022-05-19 17:32:56 UTC, 
@id="238c65ef0b6ba04ccf6120ce85df6d8daa77135ec9a972eaca6deb521c74714b">]

I, [2022-05-19T13:33:02.485591 #93541]  INFO -- : Thread-2952: Staff Indexer 
[2022-05-19 13:33:02 -0400] ~~~ Indexed 1 of 1 classification records in 
repository Blake
D, [2022-05-19T13:33:02.544059 #93541] DEBUG -- : Thread-2970: GET 
/repositories/2/classifications?id_set=1%5B%5D=location_profile%5B%5D=container_profile%5B%5D=container_locations%5B%5D=subjects%5B%5D=places%5B%5D=linked_agents%5B%5D=linked_records%5B%5D=classifications%5B%5D=digital_object%5B%5D=agent_representation%5B%5D=repository%5B%5D=repository%3A%3Aagent_representation%5B%5D=related_agents%5B%5D=top_container%5B%5D=top_container%3A%3Acontainer_profile%5B%5D=related_agents%5B%5D=records%5B%5D=collections%5B%5D=surveyed_by%5B%5D=reviewer%5B%5D=creator%5B%5D=related_accessions
 [session: #"search_indexer", 
:login_time=>2022-05-19 13:32:52 -0400, :expirable=>false}, 
@system_mtime=2022-05-19 17:33:01 UTC, 
@id="238c65ef0b6ba04ccf6120ce85df6d8daa77135ec9a972eaca6deb521c74714b">]
D, [2022-05-19T13:33:02.568091 #93541] DEBUG -- : Thread-2970: Post-processed 
params: {"id_set"=>[1], "resolve"=>["location_profile", "container_profile", 
"container_locations", "subjects", "places", "linked_agents", "linked_records", 
"classifications", "digital_object", "agent_representation", "repository", 
"repository::agent_representation", "related_agents", "top_container", 
"top_container::container_profile", "related_agents", "records", "collections", 
"surveyed_by", "reviewer", "creator", "related_accessions"], "repo_id"=>2, 
"modified_since"=>0, "sort_field"=>:id, "sort_direction"=>:asc}

D, [2022-05-19T13:33:23.296930 #93541] DEBUG -- : Thread-2970: GET 
/repositories/2/archival_objects?all_ids=true_since=0 [session: 
#"search_indexer", :login_time=>2022-05-19 
13:33:22 -0400, :expirable=>false}, @system_mtime=2022-05-19 17:33:22 UTC, 
@id="28669392a202b2532b3e9029ee3582888c889fe2c43b697ad61b04d6adfca7c3">]
D, [2022-05-19T13:33:23.310005 #93541] DEBUG -- : Thread-2970: Post-processed 
params: {"all_ids"=>true, "modified_since"=>0, "repo_id"=>2, "sort_field"=>:id, 
"sort_direction"=>:asc}
D, [2022-05-19T13:33:23.376931 #93541] DEBUG -- : Thread-2970: Responded with 
[200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"10"}, ["[1,2,3,4]\n"]]... in 
104ms
I, [2022-05-19T13:33:23.389366 #93541]  INFO -- : Thread-3270: PUI Indexer 
[2022-05-19 13:33:23 -0400] ~~~ Indexed 4 of 4 archival_object records in 
repository Blake



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Thursday, May 19, 2022 9:58 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

Thanks again.

So, I currently break up my logs into four different individual logs with these 
settings:

## Possible Log levels: debug, info, warn, error, fatal (severe only)
#
AppConfig[:frontend_log] = "/var/log/archivesspace/frontend.log"
AppConfig[:frontend_log_level] = "debug"
#
AppConfig[:backend_log] = "/var/log/archivesspace/backend.log"
AppConfig[:backend_log_level] = "debug"
#
AppConfig[:pui_log] = "/var/log/archivesspace/pui.log"
AppConfig[:pui_log_level] = "debug"
#
AppConfig[:indexer_log] = "/var/log/archivesspace/indexer.log"
AppConfig[:indexer_log_level] = "debug"

In each of the other logs I see both INFO and DEBUG statements, sometimes a 
lot, other times fewer. But in the indexer.log file, I only see INFO 
statements, no DEBUG.

But your suggestion above that the line is like "indexed ..." got me searching 
other logs and I found a couple of lines like this in my backend log:

D, 

Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

[Mary Weppler]

Mary Weppler-Van Diver
Library Faculty, Librarian & 
CA
Special Collections and University 
Archives
Email:  mwepp...@csustan.edu
Phone:  209-664-6538

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Thursday, May 19, 2022 6:58 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1


CAUTION: This message originated from outside of Stanislaus State. Do not click 
on links or open attachments unless you recognize the sender and are expecting 
the message.


Thanks again.

So, I currently break up my logs into four different individual logs with these 
settings:

## Possible Log levels: debug, info, warn, error, fatal (severe only)
#
AppConfig[:frontend_log] = "/var/log/archivesspace/frontend.log"
AppConfig[:frontend_log_level] = "debug"
#
AppConfig[:backend_log] = "/var/log/archivesspace/backend.log"
AppConfig[:backend_log_level] = "debug"
#
AppConfig[:pui_log] = "/var/log/archivesspace/pui.log"
AppConfig[:pui_log_level] = "debug"
#
AppConfig[:indexer_log] = "/var/log/archivesspace/indexer.log"
AppConfig[:indexer_log_level] = "debug"

In each of the other logs I see both INFO and DEBUG statements, sometimes a 
lot, other times fewer. But in the indexer.log file, I only see INFO 
statements, no DEBUG.

But your suggestion above that the line is like "indexed ..." got me searching 
other logs and I found a couple of lines like this in my backend log:

D, [2022-05-16T14:31:45.734159 #5273] DEBUG -- : Thread-4912: Responded with 
[200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"21295"}, 
["{\"page_size\":1,\"first_page\":1,\"last_page\":1,\"this_page\":1,\"offset_first\":1,\"offset_last\":1,\"total_hits\":1,\"results\":[{\"id\":\"/repositories/2/archival_objects/1702566#pui\",\"uri\":\"/repositories/2/archival_objects/1702566\",\"title\":\"Brother
 Paul Hermit CSC not 
indexed.\",\"primary_type\":\"archival_object\",\"types\":[\"archival_object\",\"pui\",\"pui_archival...
 in 73ms

Is this the type of thing I should continue to look for?

Thanks,
Tom

On Wed, May 18, 2022 at 4:12 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
> - Even though the config setting is for DEBUG, the indexer log is only 
> showing INFO. Should there be more than that?

Yep. Something must not be quite right in the config, you should see DEBUG 
showing up in the logs.

If it's running 1x1 AND on DEBUG you should see something better by the crash, 
you should be able to spot the record. I can't remember what exactly it looks 
like, but something like "indexed some/path/with/an/id/in/it/here" and then you 
can see the Resource or Archival Object ID in the line there.



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Tom Hanstra mailto:hans...@nd.edu>>
Sent: Wednesday, May 18, 2022 3:21 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

Blake and others,

Overall, we went for a week or so with no errors in terms of re-indexing. I'm 
looking into some database timeouts which are occurring periodically (AS and 
our database server are in two different locations) but with the connection 
getting re-established, I can work to address that separately.

But last night we did run into some errors which we are trying to track down.  
A couple of things:

- Even though the config setting is for DEBUG, the indexer log is only showing 
INFO. Should there be more than that?

- If the log says:

I, [2022-05-17T22:27:11.756683 #5273]  INFO -- : Thread-2890: Staff Indexer 
[2022-05-17 22:27:11 -0400] ~~~ Indexed 216
of 20898 archival_object records in repository UNDA

immediately followed by an error, how do we determine which record that is in 
ArchivesSpace?  We are not sure how to find the record which is indicated in 
the log.

Thanks again,
Tom



On Mon, May 16, 2022 at 5:19 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
That could be it, looks like some kind of "funny" character ArchivesSpace 
doesn't like in there probably. Do the "Indexed x of x whatever " numbers start 
over right there in the log?
You should see what record it was working on just before there.


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Tom Hanstra mailto:hans...@nd.edu>>
Sent: Monday, May 16, 2022 10:43 AM
To: Archivesspace Users Group 

[Archivesspace_Users_Group] Due today: Apply now for the second cohort of the ArchivesSpace Member Match program

[Jessica Crouch]

Dear ArchivesSpace Users,

The deadline to apply to participate in the ArchivesSpace Member Match program 
is today, Friday, May 20th.

The Member Match program is an initiative to engage the ArchivesSpace 
membership community, created and organized by the Member Engagement sub-team 
of the ArchivesSpace User Advisory Council, with support from the ArchivesSpace 
Community Engagement Coordinator. The program is intended to be a resource and 
venue for peer-to-peer support between ArchivesSpace members. For one, 
year-long term, participants will be matched with a member with whom they can 
receive and offer professional insight, advice, and camaraderie. The program 
will also offer participants the opportunity to engage in exclusive events and 
enlightening discussions about ArchivesSpace and its active user community.

Thanks to valuable feedback from the first cohort of Member Match Participants, 
we’ve implemented the following updates to the program:


  *   Monthly Listserv Discussion Topics
 *   Each month, a member of the Member Engagement sub-team will reach out 
to the Member Match listserv to spur discussion and encourage continued 
engagement between matches.
  *   Quarterly Member Match Meet-Ups
 *   These will be opportunities for large group socializing as well as the 
potential for dedicated time to spend with matches in breakout rooms.
  *   Option to participate in small group matches of 3 people
Eligibility
Any individual affiliated with an ArchivesSpace member organization is eligible 
to participate in the ArchivesSpace Member Match program and there is no limit 
to the number of individuals from a member organization that may participate.

If you are unsure of your organization’s ArchivesSpace membership status, visit 
https://archivesspace.org/community/whos-using-archivesspace or email 
archivesspaceh...@lyrasis.org.
To Apply
There is a short application to complete at 
https://airtable.com/shrDL4wQhc3gkBAlH
Applications should be submitted by May 20th, 2022. Applicants will be notified 
of their matches no later than June 30th.
To Learn More
Visit the Member Match wiki: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program
Please feel free to direct any questions to 
archivesspaceh...@lyrasis.org

Sent on behalf of the ArchivesSpace Member Engagement sub-team

Regina Carra, American Folk Art Museum
Bailey Hoffner, University of Oklahoma
Patrick Milhoan, University of Notre Dame
Sarah Ponichtera, Seton Hall University
Jessica Crouch, ArchivesSpace Community Engagement Coordinator


Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org





___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Permission to Post to Archivesspace List

[John Hawthorn]

Just looking for permission to post to the list for queries on setting up 
Archivesspace server.  Thank you,

John Hawthorn
Systems Administrator

Mitchell College
437 Pequot Ave
New London, CT 06320-4498
(860)701-




[https://community.mitchell.edu/image/Mitchell_College_email_logo_7_2015.jpg]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group