Re: [Archivesspace_Users_Group] Browser Access Not Working

[Peter Heiner]

Heidi R. Pettitt wrote on 2022-05-12 15:02:30:
> Hi All,
> 
> The issue I'm having is I'm trying to access ArchivesSpace through a web 
> browser by typing in Http://IP Address of my Archives Space server:8080.  
> This is supposed to bring me to an Archives Space login in web page but it 
> says it is unable to connect.  When I enter the command netstat -an -p tcp | 
> find "8080" at a command prompt, it is not showing anything which means port 
> 8080 is not listening.  I don't know what to do to get port 8080 to listen.

The intended effect of the command you posted is to search for the string
8080 anywhere in the output of the netstat command, however, on a Posix system
'find' searches for files, you'd want 'grep' to filter netstat's piped output.

In any case, 'unable to connect' means that the connection could not be
established, so netstat output is unlikely to be helpful. Verify each
component of the full URL: scheme, IP address and port.

Hope that helps,
p
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Take a Break with ArchivesSpace on Friday

[Christine Di Bella]

Dear ArchivesSpace users,


After a one-week hiatus, our Friday break call returns this week. These casual 
open calls take place on zoom at 12pm ET on Fridays and don't have agendas or 
presentations. They're just an opportunity to connect, chat and recharge. Use 
this as a time to get help or talk about ArchivesSpace (or anything else) in an 
informal setting or have a beverage with other ArchivesSpace users during this 
stressful time.


Whether you can attend once or plan to be there every Friday, these calls are 
open to everyone but registration is required to join.


Register once to join any open call at 
https://lyrasis.zoom.us/meeting/register/tZcldOGuqjotE9cNSaa6j45issVCKrEQKQYv


We seek to provide a welcoming, fun, and safe community experience for 
everyone. The full text of the code of conduct is available at 
https://archivesspace.org/archivesspace-code-of-conduct.


Please email 
archivesspaceh...@lyrasis.org with any 
questions.
We hope to see you tomorrow!
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



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

[Archivesspace_Users_Group] Browser Access Not Working

[Heidi R. Pettitt]

Hi All,

My IT department is having trouble setting up ArchivesSpace and sent me the 
following details:

The issue I'm having is I'm trying to access ArchivesSpace through a web 
browser by typing in Http://IP Address of my Archives Space server:8080.  This 
is supposed to bring me to an Archives Space login in web page but it says it 
is unable to connect.  When I enter the command netstat -an -p tcp | find 
"8080" at a command prompt, it is not showing anything which means port 8080 is 
not listening.  I don't know what to do to get port 8080 to listen.

Does anyone have any suggestions for what's going on and how to fix it? You can 
reply to this email and I'll forward the information to him or you can email 
him at kevin.kr...@loras.edu.

Thanks,

~Heidi

HEIDI PETTITT (she/her)
Director of the Center for Dubuque History
Access Services & Special Collections Librarian

LORAS COLLEGE
Library/Center for Dubuque History
Miller Academic Resource Center 154
1450 Alta Vista
Dubuque, IA 52001
O: 563.588.7873
Meet With Me!
http://library.loras.edu/



CONFIDENTIALITY NOTICE: This email, including any attachments, is the property 
of Loras College. The information may be legally privileged and/or confidential 
and is intended solely for the use of the addressee. If you are not the 
intended recipient be advised that any unauthorized disclosure, copying, 
distribution or use of the contents herein is strictly prohibited. If you have 
received this message in error, please notify the sender immediately and 
destroy all electronic and hard copies of the communication, including 
attachments.
___
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]

> Could it be that we added a big record which is now having issues being 
> extracted. Or a corrupted record which is causing such issues?

 I don't think so? It could be, but those errors make me think there's 
something else going on with the DB, or maybe the network between the 
application and DB server? I'm not really sure what the problem is, but it 
seems more like a hardware/network/server issue than an ArchivesSpace issue. I 
can't be sure, but those errors don't look like ArchivesSpace troubles to me. 
Those are pretty common errors, so I'd do some searching around to see what you 
can find to troubleshoot.

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

Thanks again for your help.

Late yesterday, both indexes indicated completion so I thought maybe things 
were going to be OK. Consequently, I did not do much in terms of testing.

This morning, the logs again had errors, however.  In the logs, I found this 
error in the indexer log:

I, [2022-05-10T21:36:07.181427 #30003]  INFO -- : Thread-2890: Staff Indexer 
[2022-05-10 21:36:07 -0400] Index round complete
I, [2022-05-10T21:36:37.182006 #30003]  INFO -- : Thread-2890: Staff Indexer 
[2022-05-10 21:36:37 -0400] Running index round
E, [2022-05-10T21:36:37.283423 #30003] ERROR -- : Thread-2890: 
uri:classloader:/jsonmodel_client.rb:493:in `all'
/home/app/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/periodic_indexer.rb:154:in
 `run_index_round'
/home/app/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/lib/periodic_indexer.rb:283:in
 `run'
/home/app/archivesspace/data/tmp/jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-/webapp/WEB-INF/app/main.rb:32:in
 `block in main'
E, [2022-05-10T21:36:37.284431 #30003] ERROR -- : Thread-2890: #mailto:andrew.morri...@bodleian.ox.ac.uk>> 
wrote:

Indexing can also fail at the commit stage, not related to any one record. That 
is when ArchivesSpace tells Solr to transfer changes made in memory to storage. 
It does that at several points in the indexing process, but the longest one is 
at the end of the PUI indexer's run. If, because you've got a lot of records, 
or slow storage on your Solr server, it takes longer it respond than the value 
of AppConfig[:indexer_solr_timeout_seconds], it will start all over again, and 
potentially go into a loop. The workaround is to increase the timeout.


You might not notice you've got enough records to cause this until you do a 
full re-index, or someone edits something linked to most or all records (e.g. a 
repository, or a very widely-used subject), triggering the re-indexing of most 
of the system's records.


Andrew.



On 10/05/2022 22:06, Blake Carver wrote:
 1x1 would mean setting both records_per_thread and thread_count to 1. Having 
loglevel on debug and running at 1x1, you'll be able to see exactly which thing 
is being indexed as it happens, and when it crashes, you'll see what it was 
working through at the time.

PUI will always take longer, and a VERY long time 1x1, but unless you're sure 
which indexer is crashing, I'd switch them both up.

You can just `grep Indexed archivesspace.out` after it's running and watch 
those numbers. As long as they're going up, all is well.

It is also possible that it will finish without crashing running so slow as 
well. I've seen that happen with LARGE records.

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 

 on behalf of Tom Hanstra 
Sent: Tuesday, May 10, 2022 4:15 PM
To: Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

Thanks, Blake.

Turns out we did add quite a few records recently, so maybe there was something 
in there that it did not like all that much.

How can you tell which record it is choking on?  Is that your "1x1" suggestion? 
 Or does the DEBUG option make that more clear?  I have my indexing set to:

AppConfig[:indexer_records_per_thread]  = 25
AppConfig[:indexer_thread_count]= 2

for both PUI and Staff records. I believe you are suggesting it would most 
easily be found using 1 and 1?  I can see where that could take a long time. 
But it if is going to choke over and over on the same record, then that may be 
the best way to address it.

Do you think if I just did staff indexing without PUI, that it would be 
identified faster?  Or could it pass the staff side but then die on PUI later?

I hope to try some of these ideas after hours today, so if you can confirm that 
I've got the right idea, t