Re: [Archivesspace_Users_Group] Trying to spin up a new server and it won't load... Unhandled Java exception: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8089 error

[Blake Carver]

Is this set in your config?


AppConfig[:enable_solr] = false




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Gadsby, 
Eric T. 
Sent: Friday, May 19, 2023 11:22 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Trying to spin up a new server and it 
won't load... Unhandled Java exception: java.io.IOException: Failed to bind to 
0.0.0.0/0.0.0.0:8089 error


ps -ef  | grep java =



“java -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem 
-XX:+ParallelRefProcEnabled -XX 
:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch 
-XX:+ExplicitGCInvokesConcurrent 
-Xlog:gc*:file=/var/solr/logs/solr_gc.log:time,uptime:filec 
ount=9,filesize=20M 
-Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= 
-Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983
  -DSTOP.KEY=solrrocks 
-Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow 
-XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs 
-Djetty.home 
=/opt/solr/server -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= 
-Dsolr.install.dir=/opt/solr 
-Dsolr.default.confdir=/opt/solr/server/solr/configsets/
 _default/conf 
-Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k -Dsolr.log.muteconsole 
-jar start.jar --module=http --module=gzip

egadsby+65612546  0 11:18 pts/000:00:00 grep --color=auto java”



Right now it just seems to be Solr running…. Based on my read of this output.   
I might be wrong.



It is a new 3.3.1 server with a fresh install with the data base from an old 
server being imported from a SQL dump and then migrated using the script.  
Thanks!







[Towson University logo]

Eric T. Gadsby

Pronouns: he/him/his

IT Operations Specialist  |  Albert S. Cook Library

—

P: 410-704-3340
egad...@towson.edu  |  
libraries.towson.edu
 —



Confidentiality Notice: This message may contain information that is 
confidential, privileged, proprietary, or otherwise legally exempt from 
disclosure. If you are not the intended recipient, you are notified that you 
are not authorized to read, print, copy or disseminate this message, any part 
of it, or any attachments. If this message has been sent to you in error, 
please notify the sender by replying to this transmission, or by calling Albert 
S. Cook Library at 410-704-3340 .







From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Date: Friday, May 19, 2023 at 11:14 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Trying to spin up a new server and it 
won't load... Unhandled Java exception: java.io.IOException: Failed to bind to 
0.0.0.0/0.0.0.0:8089 error

[ CAUTION: This email is from outside of TU. Use caution before clicking links 
or opening attachments. If suspicious, report to phish...@towson.edu. ]

When connected to the server, use the command:

ps -ef  | grep java

and look to see if there are java processes running. If there is an old one, 
you will have to stop/kill it before starting the new one.

Is this a completely new server only running 3.3.1 ? If so, the solr process 
will also show up using that command.



Tom



On Fri, May 19, 2023 at 10:55 AM Gadsby, Eric T. 
mailto:egad...@towson.edu>> wrote:

I wondered that, how would I check? Going to a browser yields nothing… that 
said my firewall rules may not be in place? Thanks!







[Towson University logo]

Eric T. Gadsby

Pronouns: he/him/his

IT Operations Specialist  |  Albert S. Cook Library

—

P: 410-704-3340
egad...@towson.edu  |  
libraries.towson.edu
 —



Confidentiality Notice: This message may contain information that is 
confidential, privileged, proprietary, or otherwise legally exempt from 
disclosure. If you are not the intended recipient, you are notified that you 
are not authorized to read, print, copy or disseminate this message, any part 
of it, or any attachments. If this message has been sent to you in error, 
please notify the sender by replying to this transmission, or by calling Albert 
S. Cook Library at 410-704-3340 .







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>>
Date: Friday, May 19, 2023 at 10:53 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>

Re: [Archivesspace_Users_Group] Trying to spin up a new server and it won't load... Unhandled Java exception: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8089 error

[Blake Carver]

Are you sure ArchivesSpace isn't already running?
ps auxww | grep archives
If netstat doesn't show anything you could try lsof or maybe nmap

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Gadsby, 
Eric T. 
Sent: Friday, May 19, 2023 11:06 AM
To: jesse.marti...@bc.edu ; Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] Trying to spin up a new server and it 
won't load... Unhandled Java exception: java.io.IOException: Failed to bind to 
0.0.0.0/0.0.0.0:8089 error


Hi,



So running the command yields no output. This may be a bad guess but this 
server is running SPLUNK and is bound to AD.  I did some googling and it seems 
SPLUNK can use 8089. But the no output has me stumped. Thanks!







[Towson University logo]

Eric T. Gadsby

Pronouns: he/him/his

IT Operations Specialist  |  Albert S. Cook Library

—

P: 410-704-3340
egad...@towson.edu  |  
libraries.towson.edu
 —



Confidentiality Notice: This message may contain information that is 
confidential, privileged, proprietary, or otherwise legally exempt from 
disclosure. If you are not the intended recipient, you are notified that you 
are not authorized to read, print, copy or disseminate this message, any part 
of it, or any attachments. If this message has been sent to you in error, 
please notify the sender by replying to this transmission, or by calling Albert 
S. Cook Library at 410-704-3340 .







From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jesse 
Martinez 
Date: Friday, May 19, 2023 at 10:57 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Trying to spin up a new server and it 
won't load... Unhandled Java exception: java.io.IOException: Failed to bind to 
0.0.0.0/0.0.0.0:8089 error

[ CAUTION: This email is from outside of TU. Use caution before clicking links 
or opening attachments. If suspicious, report to phish...@towson.edu. ]

Hi Eric,



It looks like port 8089 is already in use. That may mean you might have a 
separate instance of the ASpace backend running, or it conflicts with another 
application that is using the same port. For the former, I'd check running 
processes and make sure to close them before continuing. For the latter I'd 
just check if port 8089 is already in use. For that I usually use a command like



lsof -i -P -n | grep 8089 | grep LISTEN



Hope this helps!

Jesse



On Fri, May 19, 2023 at 10:44 AM Gadsby, Eric T. 
mailto:egad...@towson.edu>> wrote:

Dear Friends,



I am in the process of moving our old v2.7.1 to V3.3.1. I have been able to set 
up Solr, the application, move the data and start ArchivesSpace twice in our 
testing environment (CentOS8 Stream). Today I ran the same procedure in our 
production environment (RHEL8.5) and ArchivesSpace won't start.



The log reports this error: "Unhandled Java exception: java.io.IOException: 
Failed to bind to 0.0.0.0/0.0.0.0:8089" -- of at 
least I think that's the problem (I'm going to provide the whole log:



"$ cat archivesspace.out

OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in 
version 9.0 and will likely be removed in a future release.

Loading ArchivesSpace configuration file from path: 
/opt/archivesspace/config/config.rb

Loading ArchivesSpace configuration file from path: 
/opt/archivesspace/config/config.rb

Loading ArchivesSpace configuration file from path: 
/opt/archivesspace/config/config.rb

May 19, 2023 10:01:02 AM org.eclipse.jetty.util.log.Log initialized

INFO: Logging initialized @7281ms to org.eclipse.jetty.util.log.Slf4jLog

May 19, 2023 10:01:03 AM org.eclipse.jetty.server.Server doStart

INFO: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 
8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.19+7-LTS

May 19, 2023 10:01:03 AM 
org.eclipse.jetty.server.session.DefaultSessionIdManager doStart

INFO: DefaultSessionIdManager workerName=node0

May 19, 2023 10:01:03 AM 
org.eclipse.jetty.server.session.DefaultSessionIdManager doStart

INFO: No SessionScavenger set, using defaults

May 19, 2023 10:01:03 AM org.eclipse.jetty.server.session.HouseKeeper 
startScavenging

INFO: node0 Scavenging every 60ms

May 19, 2023 10:01:03 AM 
org.eclipse.jetty.server.handler.ContextHandler$Contextlog

INFO: INFO: jruby 9.2.20.1 (2.5.8) 2021-11-30 2a2962fbd1 OpenJDK 64-Bit Server 
VM 11.0.19+7-LTS on 11.0.19+7-LTS +jit [linux-x86_64]

May 19, 2023 10:01:03 AM 
org.eclipse.jetty.server.handler.ContextHandler$Contextlog

INFO: INFO: using a shared (threadsafe!) runtime

uri:classloader:/jruby/rack/response.rb:294: warning: constant ::Fixnum is 
deprecated

uri:classloader:/jruby/rack/core_ext.rb:26: warning: constant 
::NativeExceptionis deprecated

Loading ArchivesSpace configuration file from path: 
/opt/archivesspace/config/config.rb

Re: [Archivesspace_Users_Group] Database migration error creating table

[Blake Carver]

Your DB is in a bad place.
It has tables from the failed upgrade, so every time you try to run it again it 
sees those tables and says "nope, can't keep going, you have this one already"
Make sure you do this on a COPY of the DB and not the live site.
drop table lang_material
./scripts/setup-database.sh
it will probably fail with another "already exists" error
now drop lang_material AND that new one. You'll need to drop both because they 
get recreated each time you run setup again.
Keep doing that until it finishes up. There will be probably 4 or 5.
Hopefully that'll do the trick and the DB isn't messed up in any other ways.
You may also need to delete some enumeration values in there also.

ArchivesSpace expects certain things to be in certain places, and certain other 
things to NOT be in certain places when upgrading, if the upgrade fails only 
some of those things are in the right place, so it can't get past that weird 
state.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Crimi, 
Nick 
Sent: Thursday, May 18, 2023 4:17 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Database migration error creating table

Thank you! I tried running the setup database script for 2.7.0 and 2.7.1. Both 
want to create the lang_material table but it already exists.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Benn 
Joseph 
Sent: Thursday, May 18, 2023 3:43:28 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Database migration error creating table

You don't often get email from benn.jos...@northwestern.edu. Learn why this is 
important
This email originated from outside ECU.


Wasn’t there also a version somewhere around 2.7 where the data model changed 
re: languages? I remember having to upgrade to 2.7 (and running some sort of 
tool) before going to 2.8, a couple of upgrades ago.

--Benn



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Valerie 
Addonizio
Sent: Thursday, May 18, 2023 2:27 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Database migration error creating table



Nick I’m not sure it’s related, but aspace-import-excel (the plugin) was added 
to core code as of 2.8.0, so you can drop that plugin and enjoy that 
functionality without it.



-Valerie



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Crimi, Nick
Sent: Thursday, May 18, 2023 3:10 PM
To: 
archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Database migration error creating table



Hi team,



My library is trying to upgrade AS from 2.51 to 3.3.1. We are using mysql for 
the dB and aspace-import-excel is enabled for plug-in.

The dB migration throws an error that table lang_material already exists. 
Please let me know how to complete the upgrade. Maybe I need to upgrade to the 
latest 2.x version first?



Nick crimi

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

Re: [Archivesspace_Users_Group] Error trying to load via spredsheet

[Blake Carver]

If I remember correctly, that pulls the proxy URLs?

https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L178-L184


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Robert 
T. Wilson 
Sent: Wednesday, May 10, 2023 11:12 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Error trying to load via spredsheet


Blake, one other question. Background job links in 3.3.1 all point to localhost 
instead of domain http://localhost:8080/jobs/208/file/309?ext=.xlsx for 
example. I had setup a few instances before migrating prod, and these all 
reflected that. I was wondering if this was a configuration issue on my end and 
possibly related. If configuration issue, I'm all out of ideas on what could be 
causing it. Links in 2.5 with same setup as my original 3.3.1. test box show 
the domain url instead.


Robert



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, May 10, 2023 09:10
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Error trying to load via spredsheet


It looks like you're hitting a known issue, with no known fix yet. Here's the 
JIRA with some details:

https://archivesspace.atlassian.net/browse/ANW-1427



Long story short, the importer just falls apart sometimes.  If you can 
replicate this problem reliably, be sure to comment there.



All I can say is SOMETHING goes wrong, and then it just stops working.


Restarting always clears it up.




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Robert 
T. Wilson 
Sent: Wednesday, May 10, 2023 9:58 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Error trying to load via spredsheet

Hi folks,

We've just moved to 3.3.1, and I am seeing an odd issue when users try to load 
via spreadsheet. We can select our file, but when we click "import selected" we 
get the generic "something went wrong" 500 page.

I've attached debug logs, but these were logs at warn level

F, [2023-05-09T17:59:29.110284 #23230] FATAL -- :
F, [2023-05-09T17:59:29.110478 #23230] FATAL -- : RuntimeError (Couldn't make 
an ID out of URI: ):
F, [2023-05-09T17:59:29.110534 #23230] FATAL -- :
F, [2023-05-09T17:59:29.110576 #23230] FATAL -- : 
app/controllers/jobs_controller.rb:51:in `create'
app/controllers/application_controller.rb:744:in `set_locale'
E, [2023-05-09T17:59:31.130959 #23230] ERROR -- : Thread-8720: Unhandled 
exception!
E, [2023-05-09T17:59:31.131241 #23230] ERROR -- :
invalid byte sequence in UTF-8

If a user is seeing this, I am easily able to reproduce. With the invalid byte 
sequence message, I assumed it was something in the spreadsheet (attached is 
associated with debug log), BUT the workaround I've found makes me think this 
is something else. The workaround: If I try creating another background job for 
resource in question like generate pdf then I try the load via spreadsheet 
again, the job queues and runs without issue or delay.

Has anyone seen something like this or have any recommendations?

Thanks in advance for any assistance y'all can provide.

Robert

Robert T. Wilson (he/him)
Cloud Systems Administrator
Cornell University Library
rtwil...@cornell.edu
607.254.3483
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Error trying to load via spredsheet

[Blake Carver]

It looks like you're hitting a known issue, with no known fix yet. Here's the 
JIRA with some details:

https://archivesspace.atlassian.net/browse/ANW-1427



Long story short, the importer just falls apart sometimes.  If you can 
replicate this problem reliably, be sure to comment there.



All I can say is SOMETHING goes wrong, and then it just stops working.


Restarting always clears it up.




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Robert 
T. Wilson 
Sent: Wednesday, May 10, 2023 9:58 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Error trying to load via spredsheet

Hi folks,

We've just moved to 3.3.1, and I am seeing an odd issue when users try to load 
via spreadsheet. We can select our file, but when we click "import selected" we 
get the generic "something went wrong" 500 page.

I've attached debug logs, but these were logs at warn level

F, [2023-05-09T17:59:29.110284 #23230] FATAL -- :
F, [2023-05-09T17:59:29.110478 #23230] FATAL -- : RuntimeError (Couldn't make 
an ID out of URI: ):
F, [2023-05-09T17:59:29.110534 #23230] FATAL -- :
F, [2023-05-09T17:59:29.110576 #23230] FATAL -- : 
app/controllers/jobs_controller.rb:51:in `create'
app/controllers/application_controller.rb:744:in `set_locale'
E, [2023-05-09T17:59:31.130959 #23230] ERROR -- : Thread-8720: Unhandled 
exception!
E, [2023-05-09T17:59:31.131241 #23230] ERROR -- :
invalid byte sequence in UTF-8

If a user is seeing this, I am easily able to reproduce. With the invalid byte 
sequence message, I assumed it was something in the spreadsheet (attached is 
associated with debug log), BUT the workaround I've found makes me think this 
is something else. The workaround: If I try creating another background job for 
resource in question like generate pdf then I try the load via spreadsheet 
again, the job queues and runs without issue or delay.

Has anyone seen something like this or have any recommendations?

Thanks in advance for any assistance y'all can provide.

Robert

Robert T. Wilson (he/him)
Cloud Systems Administrator
Cornell University Library
rtwil...@cornell.edu
607.254.3483
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

[Blake Carver]

It looks like there's a bad date hiding somewhere else. It's ALMOST always in 
the user table, but not always always.

Try something like:

https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05

https://gist.github.com/Blake-/3c133ec7e42d039d85afbad5b3089eb4

You can update that year-month-day on those and see if you can find something.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Philip 
Webster 
Sent: Tuesday, March 28, 2023 7:07 AM
To: 'Archivesspace Users Group' 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2


Hi,

Ran into this yesterday, and I ran the SQL UPDATE query – I got a report of 4 
rows affected, but now our AS instance won’t start up due to initialisation 
errors. We are getting the same error as before.



Here is the console interaction for SQL:

mysql> UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Query OK, 4 rows affected (0.01 sec)

Rows matched: 4  Changed: 4  Warnings: 0



Here is the stack trace (first few lines):

Mar 28, 2023 12:00:08 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log

WARNING: ERROR: initialization failed

org.jruby.rack.RackInitializationException: Java::JavaSql::SQLException: 
HOUR_OF_DAY: 1 -> 2

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:129)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:97)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:89)

   from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:63)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:73)

from 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(com/mysql/cj/jdbc/exceptions/SQLExceptionsMapping.java:85)

from 
com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp(com/mysql/cj/jdbc/result/ResultSetImpl.java:947)

from java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)

from 
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456)

from 
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther0:getTimestamp(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.timestamp_convert(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from org.jruby.RubyMethod.call(org/jruby/RubyMethod.java:123)

from 
org.jruby.RubyMethod$INVOKER$i$call.call(org/jruby/RubyMethod$INVOKER$i$call.gen)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther9:call(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.process_result_set(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from org.jruby.RubyArray.each(org/jruby/RubyArray.java:1809)



This is affecting a production service, so I may have to raise a technical 
support request if there isn’t a community solution.



Regards,



Philip Webster

The University of Sheffield





From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: 27 March 2023 09:07
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2



A reminder to anyone in Europe, whose clocks changed this weekend, to check 
your ArchivesSpace system. If everything but the home page isn't working, try 
the fix below...



Andrew.





On 12/03/2023 19:57, Blake Carver wrote:



It's that time of year again! If ArchivesSpace isn't working for you today, 
check the logs... If you see

DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2



Try this and restart, that'll probably do the trick.



UPDATE user set user_mtime = NOW(), system_mtime=NOW();






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

Re: [Archivesspace_Users_Group] legality of using Java

[Blake Carver]

Hi Heidi
I can't comment on the license issues or legal issues. I'll just say I have 
heard of other places, large and small, pulling Oracle Java out of everything 
they can, just in case.

ON LINUX OpenJDK works just fine, my guess would be most places use that. 
That's what we use.

I don't know about Windows. My personal opinion is that ArchivesSpace works on 
Windows, but tends to be happier on Linux.

I think those docs should be updated a bit to reflect the use of OpenJDK as 
well, so thanks for pointing that out.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Heidi J. 
Webb 
Sent: Friday, March 24, 2023 2:56 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] legality of using Java


Hello ArchivesSpace experts!



We self-host ArchivesSpace on a Windows server and our central IT department 
has asked us to remove Oracle Java and run OpenJDK instead or switch to a Linux 
environment and run the system on the built in OpenJDK/Java. We are currently 
running Oracle Java 15 with a downgraded connector based on a listserv 
suggestion when we were having a problem with the JDBC connector on the older 
versions of Java.



IT is concerned that we are violating the oracle license agreement and it would 
get discovered if our campus was ever audited.  I’ve dug around oracle’s 
license agreements including the one for java 8 and 11 
(https://www.oracle.com/downloads/licenses/javase-license1.html) My 
interpretation is that you can use java 8 and 11 if it’s included in the source 
code for the program.  ArchivesSpace’s getting started technical docs say that 
it’s required before installing 
(https://github.com/archivesspace/tech-docs/blob/master/administration/getting_started.md).
 What allows ArchivesSpace users to use Java 8 or Java 11 without violating the 
license agreement?



Alternatively, is anyone successfully using OpenJDK?



Any insight would be appreciated before we dive into trying to use OpenJDK or 
switching the entire system to Linux.



Heidi



Heidi Webb

Discovery and Technology Services

Health Sciences Library | SUNY Upstate Medical University

we...@upstate.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] M1/M2 Mac - Initialize Plugins with Gem Dependencies - Issues

[Blake Carver]

Since I have a Linux box here I gave up pretty quick, but I couldn't get it to 
run on my M1 either.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Thursday, March 23, 2023 10:33 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] M1/M2 Mac - Initialize Plugins with Gem 
Dependencies - Issues

Hey all

Has anyone successfully used the included initialize-plugin script to install 
plugins with gem dependencies on an M* mac? I've patched jRuby as per Mark 
Triggs (https://teaspoon-consulting.com/articles/archivesspace-on-the-m1.html), 
but the plugin init script still flails.

I've created a workaround script (happy to share if that's helpful) that uses 
an rbenv managed jruby, but just wondering if I'm missing something obvious?

I'm testing against 3.3.1, but I think the issue will be the same across all AS 
releases.

Thanks!
Joshua

___
Joshua Shaw (he, him)
Library Web & Application Developer
Digital Library Technologies Group
Dartmouth College
603.646.0405
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Resource Records Not Showing Up

[Blake Carver]

Could be the indexer, could also be that ID is in the deleted_records table so 
it gets deleted from the index.
Check that table and see what's in there.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Thursday, March 23, 2023 11:56 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Resource Records Not Showing Up

Kinda sounds like the indexer is having trouble, but that the records are in 
the database. You probably want to take a look at the logs to see if you spot 
anything - typically look for 'error' or 'fatal'. That'll help point to the 
issue.

Joshua

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Michelle 
Romero 
Sent: Thursday, March 23, 2023 10:59 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Resource Records Not Showing Up

You don't often get email from michelle_rome...@emerson.edu. Learn why this is 
important
Hi All,

We recently upgraded from ArchivesSpace v2.8.0 to 3.3.1 on our Development 
server and we're running into an issue. When we create a resource, it will not 
appear in the Resources list on the backend/frontend and I can't find it in the 
system by searching for it. If I try to recreate the record using the same 
identifier, I get an error message saying the ID is already in use. We tried 
forcing a re-index, but it caused the existing records to vanish. Does anyone 
have any ideas of what the problem might be?

Thank you for your help,
Michelle
__
Michelle Romero (she/her/hers)
Digital Archivist
Emerson College
120 Boylston Street
Boston, MA 02116-4624
617-824-8337

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

Re: [Archivesspace_Users_Group] Multiple ASpace instances and External Solr

[Blake Carver]

> Does anybody know of any issues with running two versions of ASpace on the 
> same system, one with built in Solr and another with external Solr.

Other than the ports, I think that should be fine?

 > Also, the introductory Lyrasis video at 
 > https://www.youtube.com/watch?v=1KbD0M_XfqI, shows Solr being started 
 > manually. Presumably, we would need to take appropriate actions to start 
 > Solr as a service? (Ubuntu 18 & systemmd)

Yeah, since the video was meant to be very basic, I left that part out.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Matthew 
Adair 
Sent: Thursday, March 23, 2023 10:29 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Multiple ASpace instances and External Solr

Greetings hivemind!

We're in the process of ASpace to the latest running external Solr from 3.0 
which still had built in Solr. We currently have two "sandboxes" of 
ArchiveSpace setup on the same system. One for testing api scripts, etc. before 
we use them on production, and another specifically for testing out upgrades.

Does anybody know of any issues with running two versions of ASpace on the same 
system, one with built in Solr and another with external Solr.

Also, the introductory Lyrasis video at 
https://www.youtube.com/watch?v=1KbD0M_XfqI, shows Solr being started manually. 
Presumably, we would need to take appropriate actions to start Solr as a 
service? (Ubuntu 18 & systemmd)

Matt



Matt Adair
Archivist for Digital Imaging and Infrastructure

[https://ci3.googleusercontent.com/mail-sig/AIorK4zQSmqLoMdUNhv3966x340KqFDspUjPLDP2yUhADeQmdyoueQpr4Qg5-GGeIU6zcksd6KYM5Ik]
Bentley Historical Library
1150 Beal Avenue
Ann Arbor, Michigan 48109-2113
734-647-3537
http://bentley.umich.edu
@UmichBentley

The Bentley Historical Library acknowledges that coerced cessions of land by 
the Anishnaabeg and Wyandot made the University of Michigan possible, and we 
seek to reaffirm the ancestral and contemporary ties of these peoples to the 
lands where the University now stands.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] issue adding new subject and agent records

[Blake Carver]

Could be an indexer issue.

Check the logs for ERROR or FATAL, there should be something there.

It might also help to reset the loglevels to debug

AppConfig[:backend_log_level]  = "debug"
AppConfig[:frontend_log_level] = "debug"
AppConfig[:indexer_log_level]  = "debug"
AppConfig[:pui_log_level]  = "debug"

Also could help to slow the indexer down, choose a low-ish number:

AppConfig[:indexer_records_per_thread] = 5
AppConfig[:pui_indexer_records_per_thread] = 5



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Anthony 
Morgano 
Sent: Tuesday, March 14, 2023 4:16 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] issue adding new subject and agent records

Hello, all!

I run the library and archives for the Milwaukee Art Museum and we recently 
started putting our collections onto ArchivesSpace. We've run into a problem as 
of yesterday: we are no longer able to add new subjects or agents. When anyone 
(including admins) try to either upload an agent from LCNAF/LCSH or create a 
new subject or agent record, it appears as if the request was completed, but 
the new subject/agent is not listed with the rest of the records and cannot be 
added to any resources. We've also noticed that if we try to manually add the 
subject/agent, we're usually met with an error message making it appear as if 
the subject/agent already exists. We can even click to view the conflicting 
record, which leads to an actual record that appears to have been created, but 
is listed with the rest of the subjects/agents and cannot be added to any 
resources.

One processor was able to add subjects and agents as of Thursday afternoon, but 
not as of yesterday.

Thank you so much for your help!

Cheers,

Anthony Morgano
Librarian/Archivist
Milwaukee Art Museum–Research Center
700 North Art Museum Drive
Milwaukee, WI 53202

T: 414.224.3819
anthony.morg...@mam.org
Pronouns: he/him/his




MILWAUKEE ART MUSEUM
700 N. Art Museum Drive, Milwaukee, WI 53202
mam.org


Native America: In Translation

See the work of 10 artists considering Indigenous histories, cultures, and 
representation through a contemporary lens. Plan your visit at 
mam.org/native-america.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] [EXTERNAL] Re: Manage Top Containers search not showing changes

[Blake Carver]

Still sounds like the indexer is failing or caught in a fail loop and never 
gets past a bad record.

Check the logs for ERROR or FATAL
It might also help to reset the loglevels to debug

AppConfig[:backend_log_level]  = "debug"
AppConfig[:frontend_log_level] = "debug"
AppConfig[:indexer_log_level]  = "debug"
AppConfig[:pui_log_level]  = "debug"

Also could help to slow the indexer down, choose a low-ish number:

AppConfig[:indexer_records_per_thread] = 5
AppConfig[:pui_indexer_records_per_thread] = 5

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Barrett 
Codieck 
Sent: Tuesday, March 14, 2023 3:38 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [EXTERNAL] Re: Manage Top Containers 
search not showing changes


IT reindexed our instance, which solved the top container search problem. Now 
all recently created resource records are not appearing in any searches. The 
records are still there, and older resource records are not affected. Our IT 
will try another reindex next week. Any thoughts on why this issue may have 
emerged after the first reindex?



Barrett



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Valerie 
Addonizio
Sent: Monday, March 6, 2023 3:21 PM
To: Archivesspace Users Group 
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Manage Top Containers 
search not showing changes



  **EXTERNAL EMAIL**
  This email originated outside of The University of Texas at San Antonio.
  Please exercise caution when clicking on links or opening attachments.



Hi Barrett,



On the surface this sounds like you need to reindex your database. Your IT or 
hosting provider can do so using these instructions: 
https://archivesspace.github.io/tech-docs/administration/indexes.html



I can give you this video clip for why I think that: 
https://youtu.be/b-jl0CfH7F8?t=3625



-Valerie





From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Barrett Codieck
Sent: Monday, March 6, 2023 1:53 PM
To: 
archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Manage Top Containers search not showing 
changes



Hello all,



Starting two months ago our Manage Top Containers search results stopped 
reflecting any recent changes (locations, container profiles, etc). Changes are 
displayed correctly when viewing individual top container records. We run 
v2.5.0. Has anyone else encountered this?



Thanks,



Barrett Codieck

Collections Management Archivist



The University of Texas at San Antonio

Special Collections

One UTSA Circle

San Antonio, TX 78249

o: 210.458.8593


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

Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

[Blake Carver]

It's that time of year again! If ArchivesSpace isn't working for you today, 
check the logs... If you see
DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

Try this and restart, that'll probably do the trick.

UPDATE user set user_mtime = NOW(), system_mtime=NOW();




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 11:05 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Thanks Blake. It looks like the one-liner (UPDATE user set user_mtime = NOW(), 
system_mtime=NOW();) did the trick. I'll remember that for future seasonal 
changes.

Cheers
Scott



==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: 28 March 2022 16:00
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email 
is genuine and the content is safe.
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2022-March/009092.html

You can probably just:
UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Though might need to:

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 10:55 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Little bit more information- running v.2.8.1 and MariaDB 5.5.68.

Time complained about is eg

Time: 2022-03-28 15:46:28 +0100



So basically any startup time + 0100 (I'm not sure which table it would be 
writing to there), which puts it into the future- no longer blaming users! I am 
guessing that a reindex won't solve this; my time_zone settings are unchanged.


MariaDB [(none)]> SELECT @@global.time_zone, @@session.time_zone;

++-+

| @@global.time_zone | @@session.time_zone |

++-+

| SYSTEM | SYSTEM  |

++-+

1 row in set (0.00 sec)


Cheers

Scott


Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

--- System

jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.322-b06 on 1.8.0_322-b06 +jit [linux-x86_64]

Time: 2022-03-28 15:46:28 +0100

Server: jetty/8.1.5.v20120716

jruby.home: uri:classloader://META-INF/jruby.home


--- Context Init Parameters:

jruby.max.runtimes = 1

jruby.min.runtimes = 1

public.root = /

rack.env = production


--- Backtrace

Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

   raise_error at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/misc.rb:419

 statement at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:677

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:239

  hold at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/connection_pool/threaded.rb:87

   synchronize at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/connecting.rb:270

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:238

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:1082

fetch_rows at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:726

 with_sql_each at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:934

with_sql_first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:944

single_record! at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:700

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:243

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/plugins.rb:33

[] at 
/apps/archivesspace/gems/gems/sequ

Re: [Archivesspace_Users_Group] Delay publishing resources

[Blake Carver]

Maybe stick a date in a user defined field, call that "Publish After" and then 
run a report on that once a quarter and look for those dates?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
McLaughlin, Brianna Jean 
Sent: Tuesday, March 7, 2023 4:27 PM
To: 'Archivesspace_Users_Group@lyralists.lyrasis.org' 

Subject: [Archivesspace_Users_Group] Delay publishing resources


Hi everyone,



Sorry, I have been sending a lot of e-mails to this list lately!



A collection manager at my institution asked if there was a way to delay 
publication in ArchivesSpace. We host many political papers, so those finding 
aids cannot be public until a certain date. I’m 99.9% positive that 
ArchivesSpace doesn’t have this functionality, and I’m not sure how sustainable 
it would even be if it were possible. With that said, do any of you have 
workflows in place (in or outside of ArchivesSpace) to automate publishing 
finding aids for similar reasons?



Thanks,



Bri McLaughlin, she/her/hers

Visiting Metadata Services Librarian

Indiana University

812-856-3321


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

Re: [Archivesspace_Users_Group] External Solr - Memory Allocation?

[Blake Carver]

> I'm running default config values for the AS log levels so they are all set 
> to 'debug'.

I'm seeing "INFO" and not "DEBUG" there.

> Deleted 186992 documents

How much is in the deleted_records table? Try truncating that. ArchivesSpace is 
going and deleting anything in that table.

> So I'm falling back to this just being super​ slow for some reason.

Could be some complex records, could be there's way too much in the deleted 
table.

> but I'm not sure why the PUI indexer would become so much slower (21 hours)

Yep, sounds about right. The PUI is slow.

> We do have some collections that are quite large (10s of thousands of AOs), 
> so maybe that's part of the issue.

No doubt that's slowing it down too.



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Thursday, January 26, 2023 6:02 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] External Solr - Memory Allocation?

Thanks, Blake!

I'm running default config values for the AS log levels so they are all set to 
'debug'. I took a closer look, and the timeout message happens exactly after 
the timeout amount I set (as you'd expect). Interestingly, Solr is in the 
middle of deleting documents when it goes silent

I, [2023-01-26T09:18:40.357101 #78764]  INFO -- : Thread-3384: Deleted 100 
documents: #

 40 minutes pass with all the other AS log chatter ...

E, [2023-01-26T09:58:40.400971 #78764] ERROR -- : Thread-3384: SolrIndexerError 
when deleting records: Timeout error with  POST {}
I, [2023-01-26T09:58:40.410522 #78764]  INFO -- : Thread-3384: Deleted 100 
documents: #

This continuing delete phase goes on for a bit until it stops logging batch 
deletes.

I, [2023-01-26T09:59:11.734200 #78764]  INFO -- : Thread-3384: Deleted 9 
documents: #

 40 minutes pass with all the other AS log chatter ... And then the commit 
error pops up

E, [2023-01-26T10:39:11.746166 #78764] ERROR -- : Thread-3384: SolrIndexerError 
when committing:
Timeout error with  POST {"commit":{"softCommit":false}}.

Then after some more time

I, [2023-01-26T11:06:35.678926 #78764]  INFO -- : Thread-3384: Deleted 186992 
documents: #

 This all seems to indicate to me that the commit phase is taking an 
inordinate amount of time (almost 2 hours - maybe that's what I need to set the 
timeout to?). After that, the indexer starts the 2nd repo

I, [2023-01-26T11:06:35.765797 #78764]  INFO -- : Thread-3384: PUI Indexer 
[2023-01-26 11:06:35 -0500] Indexed 2 additional PUI records in repository 
Sherman

 The indexer waits for a looong time with no timeout and no messaging - 
even though this is a tiny repo - and then starts the 3rd repo

I, [2023-01-26T11:31:32.795602 #78764]  INFO -- : Thread-3384: PUI Indexer 
[2023-01-26 11:31:32 -0500] Indexed 188 additional PUI records in repository 
Rauner-XO

And then the indexer starts the 4th repo soon after and seems to go on to 
complete normally

I, [2023-01-26T11:31:33.369369 #78764]  INFO -- : Thread-3384: PUI Indexer 
[2023-01-26 11:31:33 -0500] ~~~ Indexed 25 of 74785 archival_object records in 
repository thedartmouth

The Solr logs indicate that Solr is working this entire time doing adds and 
deletes. For example in one of the quiet phases:

2023-01-26 10:23:35.928 INFO  (qtp2101153819-523) [   x:archivesspace] 
o.a.s.u.p.LogUpdateProcessorFactory [archivesspace]  webapp=/solr path=/update 
params={}{add=...
2023-01-26 10:23:38.195 INFO  (qtp2101153819-468) [   x:archivesspace] 
o.a.s.u.p.LogUpdateProcessorFactory [archivesspace]  webapp=/solr path=/update 
params={}{deleteByQuery=...

So I'm falling back to this just being super​ slow for some reason. I do have 
some custom indexer addons, but I'm not sure why the PUI indexer would become 
so much slower (21 hours) when the Staff indexer completes in a normal amount 
of time (a little under 6 hours). For previous versions this hasn't been quite 
that different (6hrs vs about 13hrs). We do have some collections that are 
quite large (10s of thousands of AOs), so maybe that's part of the issue.

I haven't checked to see if the PUI indexer is gathering that much more data 
(and traversing the tree more times - maybe?) than it was in 3.1.1, but that's 
on my 'to check' list.

Joshua

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Thursday, January 26, 2023 4:12 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] External Solr - Memory Allocation?

That's... interesting.

That RAM allocation seems fine. That Solr timeout is way higher than I would 
think is needed.

Maybe set the loglevel to debug and see if it spits out something more useful? 
Maybe you'll be able to see what it's up to during that long time. I like 
your theory on that.



From: archiv

Re: [Archivesspace_Users_Group] External Solr - Memory Allocation?

[Blake Carver]

That's... interesting.

That RAM allocation seems fine. That Solr timeout is way higher than I would 
think is needed.

Maybe set the loglevel to debug and see if it spits out something more useful? 
Maybe you'll be able to see what it's up to during that long time. I like 
your theory on that.



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Thursday, January 26, 2023 3:38 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] External Solr - Memory Allocation?

Following up on this. And looking for some advice!

Even with the Solr timeout set to 40 minutes, I'm seeing some random Solr 
Timeout errors, though these do NOT cause the indexer to restart. In the latest 
test run I see one Solr Timeout for delete and one for commit - both following 
the PUI indexer run for AOs for the first and largest repo (~630k AOs).

The indexer throws the delete timeout error, waits for a lng time with 
seemingly no activity, throws the commit timeout error, waits again, and then 
picks back up as if nothing had gone wrong and continues with the initial index 
run. All of the index data looks correct (ie correct number of objects in both 
the staff and PUI).

My theory is that the Solr update phase really is taking a super lng time, 
but that the data has all been sent to Solr so the timeouts are really just 
ArchivesSpace waiting for Solr in between indexing one object type and the next 
and no index data is lost.

There are no corresponding log entries in the Solr logs that I can find.

I'm running solr 8.11.6 with 4GB and AS 3.3.1 with 4GB. Both bare metal on my 
laptop, so no container issues that might be at play. Solr memory use peaks at 
around 3.5GB.

I've kept the stock thread and records per thread settings and just upped the 
timeout (to 2400). I guess the next step is to set the timeout even higher - 
maybe an hour (3600)? I don't see a reason to run a lower thread or record 
count, but can certainly try that as well, though I'm not looking forward to 
the time it will take (the current run takes 21 hours as it is - up from about 
15 for 3.1.1)

Any advice appreciated!

Thanks!
Joshua


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Tuesday, January 24, 2023 6:56 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] External Solr - Memory Allocation?

Hey all

We're about to jump to v3.3.1 and I'm wondering if anyone has any suggestions 
for memory allocation for Solr?

Currently we're running 6GB for the entire suite in v3.1.1 and are looking to 
keep the same overall memory footprint. Wondering if something like a 75/25 
split (ie 4GB for AS and 2GB for Solr) would be a reasonable allocation? Or are 
people finding that Solr is more demanding?

Thanks!
Joshua

___
Joshua Shaw (he, him)
Library Web & Application Developer
Digital Library Technologies Group
Dartmouth College
603.646.0405
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] ArchivesSpace v3.3.1 with External Solr v 9.1.1

[Blake Carver]

It'll be best to stick to 8.x for now. Last I checked ArchivesSpace  didn't 
like 9.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jerry 
Boggio 
Sent: Thursday, January 26, 2023 2:06 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] ArchivesSpace v3.3.1 with External Solr v 
9.1.1


Hello Archivesspace Users Group;



We are planning to upgrade to version 3.3.1 or ArchivesSpace and were 
considering upgrading our local installation of External Solr from version 
8.11.2 to 9.1.1. Has anyone had experience with running ASpace 3.3.1 with the 
latest version of External Solr? Is Solr 9.1.1 compatible with ASpace 3.3.1?



Look forward to hearing your opinions.



Thank you!

Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info 
Management | 781-271-2719


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

Re: [Archivesspace_Users_Group] [External] Advice requested on updating public texts with yml

[Blake Carver]

Agreeing with Andrew on that permissions error, might be important, might not 
be.

For that path though, I think you want it more like
/public/locales/en.yml
I think you have an extra /public/ in there?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Holland, 
Andrew S 
Sent: Thursday, January 12, 2023 11:19 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [External] Advice requested on 
updating public texts with yml


I’m not sure that I completely understand what all is going on with this, but 
the permissions denied on /data/tmp/* seems like the first thing you might want 
to address. You could see how it goes after you change the permissions on that 
directory?





Andrew Holland (h/h/h)
Administrative Lead, LIT
5023 Main Library, Iowa City, Iowa 52242
Office: 319-335-1193
lib.uiowa.edu

[The University of Iowa Logo]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Matthew 
Lawson
Sent: Thursday, January 12, 2023 9:52 AM
To: Archivesspace Users Group 
Subject: [External] [Archivesspace_Users_Group] Advice requested on updating 
public texts with yml



I have modified the title, among other things, in a new en.yml file that I want 
to be visible to the public.  But even after a restart, the public site 
continues to display the old info.  I renamed the old en.yml files so as not to 
lose them and I know via grep results that there can be no other hiding place 
for where the public website data is coming from.  Is there a better way to 
force Ruby to display current info?



  $/usr/local/archivesspace$ grep -rnw '/usr/local/archivesspace' -e 
'Archives at UNI'
/usr/local/archivesspace/locales/public/locales/public/en.jan.yml:24:title: 
Archives at UNI
/usr/local/archivesspace/locales/public/locales/public/en.jan.yml:32:
welcome_page_title: Archives at UNI
/usr/local/archivesspace/locales/public/public/en.jan.yml:24:title: 
Archives at UNI
/usr/local/archivesspace/locales/public/public/en.jan.yml:32:
welcome_page_title: Archives at UNI
/usr/local/archivesspace/locales/public/en.jan.yml:24:title: Archives at UNI
/usr/local/archivesspace/locales/public/en.jan.yml:32:welcome_page_title: 
Archives at UNI
grep: /usr/local/archivesspace/data/tmp/index_batch_: Permission denied
grep: /usr/local/archivesspace/data/tmp/index_batch_: Permission denied
/usr/local/archivesspace/plugins/local/public/locales/en.jan.yml:24:title: 
Archives at UNI
/usr/local/archivesspace/plugins/local/public/locales/en.jan.yml:32:
welcome_page_title: Archives at UNI
  $/usr/local/archivesspace$ grep -rnw '/usr/local/archivesspace' -e 
'Archives and Finding Aids'
/usr/local/archivesspace/locales/public/locales/public/en.yml:24:title: 
Archives and Finding Aids
/usr/local/archivesspace/locales/public/locales/public/en.yml:30:
welcome_page_title: Archives and Finding Aids
/usr/local/archivesspace/locales/public/public/en.yml:24:title: Archives 
and Finding Aids
/usr/local/archivesspace/locales/public/public/en.yml:31:
welcome_page_title: Archives and Finding Aids
/usr/local/archivesspace/locales/public/en.yml:24:title: Archives and 
Finding Aids
/usr/local/archivesspace/locales/public/en.yml:30:welcome_page_title: 
Archives and Finding Aids
grep: /usr/local/archivesspace/data/tmp/index_batch_: Permission denied
/usr/local/archivesspace/plugins/local/public/locales/en.yml:24:title: 
Archives and Finding Aids
/usr/local/archivesspace/plugins/local/public/locales/en.yml:33:
welcome_page_title: Archives and Finding Aids




--

Matt Lawson
Cloud Systems Application Administrator
IT :: Network & Infrastructure Services :: Specialized Systems
319-273-3931
ITTC 117

  /  Cedar Falls, IA 50614
uni.edu  /  #1UNI
[UNI / University of Northern Iowa]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Changing PUI inheritance

[Blake Carver]

Best to stick with what's in the official ArchivesSpace  config.rb

https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L389-L434


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Matthew 
Lawson 
Sent: Thursday, January 12, 2023 10:40 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Changing PUI inheritance


My goal was to change PUI inheritance in the config.rb so that the “Preferred 
Citation” text is inherited by child records



So I uncommented this section at bottom and added the last property myself 
which I found at 
https://gist.github.com/fordmadox/6f91ee378ae9d8a471bb8720fd6f2bd9

I then removed the files in /data/indexer_pui_state and restarted the service.  
But the public and staff websites never came back up.  And I noticed that even 
after a half hour indexer_pui_state was not repopulating as I thought it 
should.  So I reverted to my old config.rb file and restarted.  Some indexer 
files came back but the public website gave a (rails error warning?)



We're sorry, but something went wrong.



I have now reverted to a save point but do not know how to fix record 
inheritance.  I am on 3.1.1



AppConfig[:record_inheritance] = {

  :archival_object => {

:inherited_fields => [

  {

:property => 'title',

:inherit_directly => false

  },

  {

:property => 'component_id',

:inherit_directly => false

  },

  {

:property => 'language',

:inherit_directly => false

  },

  {

:property => 'dates',

:inherit_directly => false

  },

  {

:property => 'extents',

:inherit_directly => false

  },

  {

:property => 'linked_agents',

:inherit_if => proc {|json| json.select {|j| 
j['role'] == 'creator'} },

:inherit_directly => false

  },

  {

:property => 'notes',

:inherit_if => proc {|json| json.select {|j| 
j['type'] == 'accessrestrict'} },

:inherit_directly => false


  },

  {

:property => 'notes',

:inherit_if => proc {|json| json.select {|j| 
j['type'] == 'scopecontent'} },

:inherit_directly => false

  },


  {

:property => 'notes',

:inherit_if => proc { |json| json.select {|j| 
j['type'] == 'prefercite'} },

:inherit_directly => true

  },

 ]

  }

}

--
Matt Lawson
Cloud Systems Application Administrator
IT :: Network & Infrastructure Services :: Specialized Systems
319-273-3931
ITTC 117
  /  Cedar Falls, IA 50614
uni.edu  /  #1UNI
[UNI / University of Northern Iowa]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] [External] Re: Preferred Citation Notes

[Blake Carver]

I think it just shows up in the button thingy there on the top?

There is a JIRA in about notes in general here
https://archivesspace.atlassian.net/browse/ANW-968
And there's a comment there that calls out the preferred cite as well, though 
I'm not quite sure how to read it

"The default would also include all notes expect “preferred citation”."

I THINK that means all notes but NOT preferred cite?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Holland, 
Andrew S 
Sent: Friday, January 6, 2023 9:49 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [External] Re: Preferred Citation Notes


Thank you for the response, Blake. This section of the docs explains kind of 
how preferred citation is used, but my issue is that the citation doesn’t 
display to the public. We have information in the preferred citation field but 
you can’t see that unless you’re viewing the resource in the admin interface.



https://aspace.lib.uiowa.edu/repositories/4/resources/2762



Abstract, Arrangement, Scope, etc. all display under their own header, but 
there is no preferred citation section even though we have that filled out. I 
can’t figure out why that wouldn’t display. -Andrew







From: Blake Carver<mailto:blake.car...@lyrasis.org>
Sent: Thursday, December 15, 2022 11:48 AM
To: Archivesspace Users 
Group<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [External] Re: [Archivesspace_Users_Group] Preferred Citation Notes



I think the docs explain it here?



https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-CitationactionbuttonandthePreferredCitationnote





From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Holland, 
Andrew S 
Sent: Thursday, December 15, 2022 8:25 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Preferred Citation Notes



Hello all,



I can seem to figure out how to get our notes put in to the Preferred Citation 
field to show up on the public site. Can anyone help me?



Thanks,



Andrew Holland

University of Iowa Libraries








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

Re: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem

[Blake Carver]

I don't know much about Archivematica, but it looks like it's just throwing a 
"I can't find that URL" error.
When you go to that same URL in a web browser, do you get anything?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Kirill 
Batyuk 
Sent: Thursday, December 15, 2022 1:04 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Archivematica DIP upload into 
Archivesspace problem


I am sure it is. All the records in public interface in our ASpace are in 
/repositories/2/



Kirill.



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Thursday, December 15, 2022 12:47 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Archivematica DIP upload into 
Archivesspace problem



Are you sure the repository ID is 2? Could it be 3?





From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Kirill Batyuk mailto:kbat...@whoi.edu>>
Sent: Thursday, December 15, 2022 12:24 PM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Archivematica DIP upload into 
Archivesspace problem



Hello,



Possible I can get some help with setting up DIP upload from Archivematica to 
ArchivesSpace.

I see to have set everything up per instructions. But, when I try to upload the 
DIP I get an error. The Archivematica log shows the following:



ERROR 2022-12-15 17:12:53  
agentarchives.archivesspace.client:client:_request:165:  Response code: 404

ERROR 2022-12-15 17:12:53  
agentarchives.archivesspace.client:client:_request:166:  Response body: 
{"error":"Sinatra::NotFound"}



ERROR 2022-12-15 17:12:53  
django.request:exception:handle_uncaught_exception:135:  Internal Server Error: 
/ingest/865b46b7-f16f-40a2-af7a-52e0ef433f85/upload/as/

Traceback (most recent call last):

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/exception.py",
 line 41, in inner

response = get_response(request)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py",
 line 187, in _get_response

response = self.process_exception_by_middleware(e, request)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py",
 line 185, in _get_response

response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 
79, in wrapper

return func(client, *args, **kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 
102, in ingest_upload_as

uuid,

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", 
line 74, in list_records

page = helpers.pager(resources, PAGE_SIZE, page_number)

  File "/usr/share/archivematica/dashboard/components/helpers.py", line 126, in 
pager

page = paginator.page(current_page_number)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/paginator.py",
 line 62, in page

return self._get_page(self.object_list[bottom:top], number, self)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py",
 line 57, in __getitem__

return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py",
 line 57, in 

return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py",
 line 64, in __getitem__

self.__cache[page_number] = self.page_func(page_number, self.page_size)

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", 
line 69, in 

sort_by=sort_by,

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 739, in find_collections

return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 739, in 

return [format_record(json.loads(r["json"])) for r 

Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

[Blake Carver]

Are you sure the 3.3.1 has finished up indexing 100% of everything? Could be 
it's stuck. Check the logs for ERROR or FATAL
It may also be the search just returns things a bit differently in 3 vs 2, but 
I'd make sure there's not an indexing issue first.
Can you get the record to show up in results other ways?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jesse 
Griffis 
Sent: Wednesday, December 14, 2022 1:14 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

Good Afternoon All,

My team is in the process of upgrading from 2.8.0 to 3.3.1 and we're 
encountering an odd error. In our 2.8.0 version we are able to search by 
identifier and obtain a specific record in the PUI. The same search in 3.3.1 
returns no records. We would greatly appreciate any advice or tips to point us 
in the right direction on this issue.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Preferred Citation Notes

[Blake Carver]

I think the docs explain it here?

https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-CitationactionbuttonandthePreferredCitationnote


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Holland, 
Andrew S 
Sent: Thursday, December 15, 2022 8:25 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Preferred Citation Notes


Hello all,



I can seem to figure out how to get our notes put in to the Preferred Citation 
field to show up on the public site. Can anyone help me?



Thanks,



Andrew Holland

University of Iowa Libraries






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

Re: [Archivesspace_Users_Group] Modifying User Defined fields

[Blake Carver]

Where do you have your locales en.yml file for that?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Erhan 
Tuskan 
Sent: Thursday, December 15, 2022 10:38 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Modifying User Defined fields


Hello Everybody,



At IISH we would like to use a few user defined fields for the Accessions. We 
have changed the translations in the en.yml as explained in the User manual but 
all our attempts failed, resulting in the following:



[cid:image002.jpg@01D910A3.98CB1520]



We have also tried, without success, the plug-in at 
https://github.com/hudmol/user_defined_in_basic. Our developer thinks that this 
is not compatible with v3.3.1 any more



Any tips and suggestions will be appreciated.



Thanks in advance,



Erhan Tuskan



International Institute of Social History
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem

[Blake Carver]

Are you sure the repository ID is 2? Could it be 3?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Kirill 
Batyuk 
Sent: Thursday, December 15, 2022 12:24 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Archivematica DIP upload into 
Archivesspace problem


Hello,



Possible I can get some help with setting up DIP upload from Archivematica to 
ArchivesSpace.

I see to have set everything up per instructions. But, when I try to upload the 
DIP I get an error. The Archivematica log shows the following:



ERROR 2022-12-15 17:12:53  
agentarchives.archivesspace.client:client:_request:165:  Response code: 404

ERROR 2022-12-15 17:12:53  
agentarchives.archivesspace.client:client:_request:166:  Response body: 
{"error":"Sinatra::NotFound"}



ERROR 2022-12-15 17:12:53  
django.request:exception:handle_uncaught_exception:135:  Internal Server Error: 
/ingest/865b46b7-f16f-40a2-af7a-52e0ef433f85/upload/as/

Traceback (most recent call last):

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/exception.py",
 line 41, in inner

response = get_response(request)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py",
 line 187, in _get_response

response = self.process_exception_by_middleware(e, request)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py",
 line 185, in _get_response

response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 
79, in wrapper

return func(client, *args, **kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 
102, in ingest_upload_as

uuid,

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", 
line 74, in list_records

page = helpers.pager(resources, PAGE_SIZE, page_number)

  File "/usr/share/archivematica/dashboard/components/helpers.py", line 126, in 
pager

page = paginator.page(current_page_number)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/paginator.py",
 line 62, in page

return self._get_page(self.object_list[bottom:top], number, self)

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py",
 line 57, in __getitem__

return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py",
 line 57, in 

return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py",
 line 64, in __getitem__

self.__cache[page_number] = self.page_func(page_number, self.page_size)

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", 
line 69, in 

sort_by=sort_by,

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 739, in find_collections

return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 739, in 

return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 703, in format_record

self._get(record["uri"] + "/tree", params={"page": 1}).json()[

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 185, in _get

self.session.get, url, params=params, expected_response=expected_response

  File 
"/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py",
 line 167, in _request

raise CommunicationError(response.status_code, response)

agentarchives.archivesspace.client.CommunicationError: ArchivesSpace server 
responded 404



What is interesting, is if I change my settings from repository 2 to repository 
1 it lets me to continue to next step, but it does not see any titles because 
repo 1 is empty . Repository 2 is a default and that is what giving me an error.



Any help would be greatly appreciated.



Thank you,







Kirill Batyuk [A button for name playback in email signature] 


Systems Librarian

MBLWHOI Library

Data Library and Archives

Woods Hole Oceanographic Institution

508-289-2850

Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin

[Blake Carver]

Try using the latest tag version on that plugin.


 https://github.com/lyrasis/aspace-oauth/tags

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of David P. 
Steelman 
Sent: Tuesday, December 6, 2022 2:02 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace 
v3.3.1/aspace-oauth plugin

Hello all,

In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am encountering 
the following error on startup:


  Dec 05, 2022 8:23:43 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
  WARNING: ERROR: initialization failed
  org.jruby.rack.RackInitializationException: Could not find 
public_suffix-4.0.6 in any of the sources
  from 
/apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize'
  from org/jruby/RubyArray.java:2621:in `map!'
  from 
/apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize'
  from 
/apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs'
  ...


We are using the "aspace-oauth" plugin 
(https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from the 
configuration the error does not occur.

Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" 
directory in the v3.3.1 distribution includes significantly fewer gems, and no 
longer includes a "public_suffix-3.0.6" directory.

Any pointers in handling this issue are appreciated.

Thanks,

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

Re: [Archivesspace_Users_Group] AWS/Linux/Solr

[Blake Carver]

We do have a note in the tech docs:
ArchivesSpace “officially” supports the version indicated in solrconfig.xml. 
That refers to a version that is used for development and tested between 
release cycles.

https://github.com/archivesspace/archivesspace/blob/master/solr/solrconfig.xml#L7


Currently 8.10, probably should be bumped to 8.11. As far as I can tell 
ArchivesSpace won't run with Solr 9 yet.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jesse 
Martinez 
Sent: Friday, November 4, 2022 10:05 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] AWS/Linux/Solr

Hi Kyle,

As a complete aside, I would strongly recommend you use the most recent version 
of Solr in the 8.x series, which is 8.11.2. There are some nasty 
vulnerabilities in the 8.10.x releases.

I'll make a note to ping the ASpace documentation team to update the tech-docs 
pages.

Thanks,
Jesse

On Fri, Nov 4, 2022 at 9:42 AM Peter Heiner 
mailto:ph...@cam.ac.uk>> wrote:
Kyle Breneman wrote on 2022-11-04 12:39:13:
> Thanks for your assistance, Don.  Yes, I did install Solr on the box.  I 
> created directories and put the ArchivesSpace configset in place, as per 
> instructions.
>
> What is giving me fits is that the command to start Solr isn’t working for 
> me, and I’m not sure why.  My working assumption is that I’m missing 
> something very simple.

It looks like you need to give the bin/solr script execute permissions:

chmod +x /opt/solr-8.10.0/bin/solr

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


--
Jesse Martinez
Senior Library Applications Developer
O'Neill Library, Boston College
jesse.marti...@bc.edu
617-552-2509
he/him/his
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Hard re-indexing question

[Blake Carver]

>> We recently tried a hard re-index and discovered that for the PUI, subjects 
>> linked only to digital objects were not re-indexed and dropped from the PUI. 
>> Is this expected behavior?


Maybe related to what's in your deleted_records table? How many rows in that 
table?



>> Related, is there a table/tables in the dbase that tell Solr when to index 
>> that we could investigate,


Many things have a system_mtime that you can set to NOW().



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

Re: [Archivesspace_Users_Group] Performance tuning

[Blake Carver]

> ASPACE_JAVA_XMX="-Xmx16144m"

If the site needs 16 gigs of RAM to keep going, something is probably wrong.

> AppConfig[:indexer_records_per_thread] = 25
> AppConfig[:indexer_thread_count] = 7
> AppConfig[:indexer_solr_timeout_seconds] = 300

Messing around with those indexer settings is generally a good idea for sites 
with ALLOTTA records and/or a decent number of people adding new records. "It 
Depends" is about the only answer for those settings. If you have really 
deep/complex resources you'll probably want to change those up. Try slowing it 
down a bit. Try 2/50 or 2/25. You could even slow it WAY down to 1/1. It'll 
take forever to finish, but you can see exactly what it's doing each time.

BUT

If your site was OK and now it's not, maybe something else has gone wrong.

Check your logs. Make sure you're running the log_level on debug to catch 
everything possible.

- Look for ERROR or FATAL, maybe Java out of memory errors?
Sometimes there will be an Error or error but it's usually ERROR

-Is your indexer just running forever? Maybe it's caught in a crashing loop?
 "grep Indexed" do those numbers keep going up and down?
You sould see:
 Indexed 102303 of 102303 archival_object records in repository
Only once, you don't want to see that count going up and up and then suddenly
 Indexed 1 of 102303 archival_object records in repository

- Also check your proxy logs, maybe there's a bad bot hitting the PUI way too 
hard.

- Also just check that the server doesn't have anything new running and using 
up all the resources.

The answer is usually in the logs.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Cowing 
[he], Jared 
Sent: Tuesday, September 13, 2022 12:33 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Performance tuning

Hi all,

I'm currently working with our campus IT to identify the cause(s) of a 
degradation in performance that we've been seeing. I'm relatively new to our 
library and to ArchivesSpace generally, but I've been told it's been slowing 
bit by bit for a few years, and the problem has escalated just in the past few 
weeks. Neither full re-indexes nor our nightly re-starts seem to help.

I'm aware of this page on 
tuning, 
which has been quite helpful in addition to suggestions already posted to this 
list. We're hopeful that moving to external Solr with our next upgrade will 
also help (currently on 2.7.1), but are still trying other measures just in 
case it doesn't. While we look more into general best practices for tuning our 
hosting environment, I'd also like to check with all of you to see if there are 
common issues that are more specific to ArchivesSpace that we have overlooked 
and should focus our attention on.

Here are a few of our key settings. Our Java memory variables are below. I get 
the sense that they are higher than average, is that so?
ASPACE_JAVA_XMX="-Xmx16144m"
ASPACE_JAVA_XSS="-Xss8m"

Indexer settings from config.rb:
AppConfig[:indexer_records_per_thread] = 25
AppConfig[:indexer_thread_count] = 7
AppConfig[:indexer_solr_timeout_seconds] = 300


And copied from our innodb settings:
innodb_file_per_table
innodb_flush_method=O_DIRECT
innodb_log_file_size=1G
innodb_buffer_pool_size=8G
symbolic-links=0
max_allowed_packet=128M
open_files_limit=9182

I appreciate any tips on what we ought to be looking for. I know it's hard to 
give advice from afar when each institution's situation is different, but 
thought it worth asking in case anything jumped out before we turn to technical 
support.

Thanks,
--

Jared Cowing | Systems Librarian | he/him
WILLIAMS COLLEGE LIBRARIES  | Williamstown, MA | 
(413)597-3061
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Problem attaching digital objects to resources in ArchivesSpace 3.1.1

[Blake Carver]

translation missing: 
validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha

Take a look at the Digital Objects Controlled Value lists 
(/staff/enumerations?id=12) I think you're missing something there.
"instance_type._invalid_value__digital_object_.__must_be_one_of__box" is saying 
"you're trying to add something that's not in this list, here's what's in that 
list"



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Scott 
Prater 
Sent: Friday, June 17, 2022 6:05 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Problem attaching digital objects to 
resources in ArchivesSpace 3.1.1

Hello,

We have recently begun testing out attaching digital object Instances to our 
resources in ArchivesSpace, version 3.1.1.  So far we have no success:  we can 
create a digital objects, and we can select one and add it to a resource in the 
Resource edit view, but when we then attempt to save the resource, we get the 
unhelpful "Validation Error" message with no other information.  The resource 
is not updated.

I poked around the code, and temporarily disabled the frontend code where 
validation error exceptions are swallowed 
(https://github.com/archivesspace/archivesspace/blob/v3.1.1/frontend/app/controllers/application_controller.rb#L366-L388).
  I then tried to save the resource with the attached digital object again, and 
this time saw the swallowed error:

translation missing: 
validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha

It looks like somehow a type is not getting set, or the backend is mistakenly 
requiring a type on the digital object.  There is no place I could see in the 
digital object edit interface where I can select any of those types.  I did 
select a "Moving image" type on my test digital object, but that did not change 
the error.

We've upgraded over the years from ArchivesSpace 2.5.1 to 3.1.1, following the 
upgrade steps for each new release.  Up to now, we haven't had any problems, 
but perhaps something has been left behind from previous versions?  Or a table 
is missing in our latest version?  We are running ArchivesSpace locally on our 
own server;  we have not made any changes to default distributions.

Any help or insight is appreciated (and yes, we did run a full reindex, to no 
avail).

Thanks in advance,

-- Scott

--
Scott Prater
Digital Library Architect
UW Digital Collections Center
University of Wisconsin - Madison


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

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

[Blake Carver]

Did you make any other changes to the config.rb file that might be changing up 
the logging?
I'm not really sure what might be wrong, this is one of those things that 
always "just works" and I don't know what could be wrong.
You're sure it's even running?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Thursday, June 16, 2022 11:36 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Thanks, Blake, and apologies -- I meant to say config.rb (not 
config-defaults.rb). Even with the suggested debug settings in place in 
config.rb, our Archivesspace instance doesn't produce error logging.

We are running an Archivesspace v3.2.0 release we built + local changes in 
locales and plugins. It was built on RHEL 7.9 with OpenJDK 11.0.14.1. All of 
our AppConfig[:_log_level] are set to "debug" in our config.rb.  All of the 
log destinations are set to "default".

There is an archivesspace.out file in the /logs directory, but it only contains 
startup info and a few warnings and is not modified as frequently as we would 
expect. As the archivesspace.out file does have some things written to it, 
there does not seem to be a write permissions error. We would expect there to 
be additional logging because we are encountering errors in the PUI.

Thanks again for any help,
Wendy

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 8, 2022 1:25 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Running in production mode means downloading and running the release, not the 
source code
https://github.com/archivesspace/archivesspace/releases/download/v3.2.0/archivesspace-v3.2.0.zip

Changing configuration variables would then be done in config.rb not 
config-defaults.rb.

Your archivesspace.out log file should then end up in the /logs/ directory.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Wednesday, June 8, 2022 12:26 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Thanks, Blake. We checked our config-defaults.rb, and those lines match what 
you linked to. So it seems like we've set the log levels to DEBUG, but we're 
still not seeing any error messages being logged. Is there something else we 
should check that might be getting in the way of the logs?

Here's what we have for those lines in config-defaults.rb :

57 AppConfig[:frontend_log] = "default"
59 AppConfig[:frontend_log_level] = "debug"

61 AppConfig[:backend_log] = "default"
62 AppConfig[:backend_log_level] = "debug"

64 AppConfig[:pui_log] = "default"
65 AppConfig[:pui_log_level] = "debug"

67 AppConfig[:indexer_log] = "default"
68 AppConfig[:indexer_log_level] = "debug"
________
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Tuesday, June 7, 2022 1:20 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

You can set the log levels to DEBUG here
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L49-L64

Keep in mind that on version 3.2 you'll have Solr stuff being written into the 
sperate Solr server logs.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Tuesday, June 7, 2022 12:59 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Hi Blake,

When running ASpace (3.2.0) in production mode (as opposed to development 
mode), should we be seeing information in our error logs?

We are preparing to go live with 3.2.0. After testing 3.2.0 in development 
mode, we want to test our stage instance of ASpace 3.2.0 in production mode to 
mimic what our production instance will look like. We aren't getting any info 
from the logs in production mode, making it difficult to troubleshoot. Is there 
a way we can enable logs in production mode?

Thank you,
Wendy

Wendy Hagenmaier
Digital Curation Archivist
Service Owner, University Archives & Special Collections Repository and 
retroTECH<https://www.library.gatech.edu/retrotech>
Archives, Records Management, and Digital Curation
Georgia Tech Library
Atlanta, GA 30332
wendy.hagenma...@library.gatech.edu
Pronouns: she/her
____
From: archivesspace_users_group-boun...@lyralists.ly

Re: [Archivesspace_Users_Group] Vagrant: "unable to connect to backend" error

[Blake Carver]

> Indicates a deprecation in the JDBC call, AND YET it successfully checks the 
> tables and confirms they are set to UTF-8.
> I am using the latest MySQL Connector jar for this:  
> mysql-connector-java-8.0.29.jar for Ubuntu

Yep, that's fine I think.


> It's just so weird to me that the JDBC connection seems to be working, yet 
> "can't connect to backend".

The problem is " undefined method `[]' for nil:NilClass " it's expectig a value 
there and it's not getting one. Did something change in the DB? Upgrade or 
something else that changed things?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Mark 
Cyzyk 
Sent: Wednesday, June 15, 2022 9:01 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Vagrant: "unable to connect to 
backend" error


More on this.

>From the log:

ArchivesSpaceThreadDump: Touch the file 
'/usr/share/archivesspace/thread_dump_backend.txt' to trigger a thread dump
I, [2022-06-15T11:54:40.827499 #9472]  INFO -- : Thread-2000: Connecting to 
database: 
jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]=[REDACTED]=true=UTF-8.
 Max c>
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class 
is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the 
SPI and manual loading of the driver class is genera>
I, [2022-06-15T11:54:42.592887 #9472]  INFO -- : Thread-2000: All tables 
checked and confirmed set to UTF-8.  Nice job!
  
  A trace file has been written to the following location: 
/usr/share/archivesspace/data/tmp/aspace_diagnostic_1655294083.txt

  This file contains information that will assist developers in diagnosing
  problems with your ArchivesSpace installation.  Please review the file's
  contents for sensitive information (such as passwords) that you might not
  want to share.
  
Jun 15, 2022 11:54:43 AM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: An exception happened during JRuby-Rack startup
undefined method `[]' for nil:NilClass
--- System
jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK 64-Bit Server VM 25.312-b07 
on 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 +jit [linux-x86_64]
Time: 2022-06-15 11:54:43 +
Server: jetty/8.1.5.v20120716
jruby.home: uri:classloader://META-INF/jruby.home

Indicates a deprecation in the JDBC call, AND YET it successfully checks the 
tables and confirms they are set to UTF-8.

I am using the latest MySQL Connector jar for this:  
mysql-connector-java-8.0.29.jar for Ubuntu

It's just so weird to me that the JDBC connection seems to be working, yet 
"can't connect to backend".

>From the trace file:

 "exception": {
"msg": "undefined method `[]' for nil:NilClass",
"backtrace": [
  "uri:classloader:/record_inheritance.rb:31:in `block in prepare_schemas'",
  "org/jruby/RubyArray.java:1735:in `each'",
  "uri:classloader:/record_inheritance.rb:16:in `block in prepare_schemas'",
  "org/jruby/RubyHash.java:1350:in `each'",
  "uri:classloader:/record_inheritance.rb:15:in `prepare_schemas'",
  
"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:108:in
 `block in ArchivesSpaceService'",
  
"/usr/share/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in 
`configure'",
  
"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:79:in
 `'",
  
"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:39:in
 `'",
  "org/jruby/RubyKernel.java:956:in `require'",
  
"uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in
 `require'",
  
"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1:in
 `block in (root)'",
  "org/jruby/RubyBasicObject.java:1691:in `instance_eval'",
  
"/usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4:in
 `(root)'",
  "uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `'",
  "launcher/launcher.rb:92:in `start_server'",
  "launcher/launcher.rb:157:in `main'",
  "launcher/launcher.rb:261:in `'"
]
  }
}

Advice appreciated!  Again, all I'm trying to do is duplicate our ASpace in 
Vagrant.

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.


On 6/11/22 17:08, Mark Cyzyk wrote:
All,

I am trying to duplicate our Archivesspace production app in a local Vagrant 
box.

I am getting an "unable to connect to backend" error when it boots.

I've checked to 

Re: [Archivesspace_Users_Group] material type plugin : translation missing error

[Blake Carver]

That plugin hasn't been updated in a lonng time. Assuming it still even 
works, it looks like you can add that missing value to your locales:

https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/common/locales/LOCALES_README.md

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Rajitha 
Mallempati 
Sent: Wednesday, June 15, 2022 4:28 PM
To: Archivesspace_Users_Group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] material type plugin : translation missing 
error

Hello all,

I am a student working at the University of delaware. I really need help with 
the translation issue that I am getting after adding the material types 
plugin-v1.5 to the archivesspace-v3.1.1. We are running archivesspace as a 
service.

For testing I created a dummy accession on local machine. I can successfully 
open staff and public interfaces but the material types plugin is not working 
as it supposed to.
I am getting the following error message on the left side of the staff 
interface :
  *   Basic Information 

  *   Languages 

  *   Dates 
  *   Extents 
  *   Agent Links 

  *   Related Resources 

  *   Related Accessions 

  *   Subjects 
  *   External Documents 

  *   Rights Statements 

  *   Metadata Rights Declarations 

  *   Instances 
  *   Deaccessions 

  *   Collection Management 

  *   Classifications 

  *   User Defined 

  *   translation missing: 
plugins.material-types._plural
  *

how to resolve the translation missing error. Please help me

Thanks,
rr40

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

Re: [Archivesspace_Users_Group] PDF export with a logo

[Blake Carver]

I've seen 2 things cause this

  1.  Just do a reindex, seems like sometime it just needs a kick in the 
indexes for some reason.
  2.  The server hosting that image is blocking access so ArchivesSpace can't 
grab that file. It's usually this.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 松山　ひとみ 

Sent: Thursday, June 16, 2022 12:23 AM
To: 'Archivesspace_Users_Group@lyralists.lyrasis.org' 

Subject: [Archivesspace_Users_Group] PDF export with a logo


Hello.



We've set up our museum logo in the repository field "Branding Image URL," with 
the URL; http://(--- ArchivesSpace URL ---)/assets/images/logo.jpg.

However, our logo doesn't appear on the cover page of an exported PDF from the 
SUI. The PDF was generated through the function; export -> generate pdf, which 
follows the path, Resource -> EAD -> xsl -> fop -> PDF.



Is there anything wrong with our logo data, or should we miss anything in the 
process?



We’d appreciate your kind help!



Hitomi Matsuyama, Audiovisual Archivist



Nakanoshima Museum of Art, Osaka

4-3-1 Nakanoshima, Kita-ku

Osaka 530-0005 JAPAN

tel. +81 (0)6 64 79 05 58

email. matsuyam...@nakka-art.jp


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

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

[Blake Carver]

Running in production mode means downloading and running the release, not the 
source code
https://github.com/archivesspace/archivesspace/releases/download/v3.2.0/archivesspace-v3.2.0.zip

Changing configuration variables would then be done in config.rb not 
config-defaults.rb.

Your archivesspace.out log file should then end up in the /logs/ directory.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Wednesday, June 8, 2022 12:26 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Thanks, Blake. We checked our config-defaults.rb, and those lines match what 
you linked to. So it seems like we've set the log levels to DEBUG, but we're 
still not seeing any error messages being logged. Is there something else we 
should check that might be getting in the way of the logs?

Here's what we have for those lines in config-defaults.rb :

57 AppConfig[:frontend_log] = "default"
59 AppConfig[:frontend_log_level] = "debug"

61 AppConfig[:backend_log] = "default"
62 AppConfig[:backend_log_level] = "debug"

64 AppConfig[:pui_log] = "default"
65 AppConfig[:pui_log_level] = "debug"

67 AppConfig[:indexer_log] = "default"
68 AppConfig[:indexer_log_level] = "debug"
____
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Tuesday, June 7, 2022 1:20 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

You can set the log levels to DEBUG here
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L49-L64

Keep in mind that on version 3.2 you'll have Solr stuff being written into the 
sperate Solr server logs.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Tuesday, June 7, 2022 12:59 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Hi Blake,

When running ASpace (3.2.0) in production mode (as opposed to development 
mode), should we be seeing information in our error logs?

We are preparing to go live with 3.2.0. After testing 3.2.0 in development 
mode, we want to test our stage instance of ASpace 3.2.0 in production mode to 
mimic what our production instance will look like. We aren't getting any info 
from the logs in production mode, making it difficult to troubleshoot. Is there 
a way we can enable logs in production mode?

Thank you,
Wendy

Wendy Hagenmaier
Digital Curation Archivist
Service Owner, University Archives & Special Collections Repository and 
retroTECH<https://www.library.gatech.edu/retrotech>
Archives, Records Management, and Digital Curation
Georgia Tech Library
Atlanta, GA 30332
wendy.hagenma...@library.gatech.edu
Pronouns: she/her
____
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 1, 2022 5:02 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

 https://archivesspace.github.io/tech-docs/development/dev.html
That explains the development mode.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Duckett, 
Brian (NIH/NLM) [C] 
Sent: Wednesday, June 1, 2022 4:45 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] 
; Kalyanasundaram, Sriram (NIH/NLM) [C] 

Subject: [Archivesspace_Users_Group] Requesting Clarification of development vs 
production mode


Hello,



A few weeks ago, we were attempting to resolve an issue with the Mizuno 
dependency being flagged during an internal security scan. During research 
efforts we came across the following post. 
https://archivesspace.org/archives/7226?utm_source=rss_medium=rss_campaign=archivesspace-update-december-2021



This post references two different modes ArchivesSpace can run in, development 
and production. We are seeking clarification of what the differences are 
between the two modes, how to implement one versus the other as well as verify 
which mode we are currently running in. Unfortunately, I have not found this 
information in the tech docs, so I do apologize in advance if the information 
is there and has been overlooked.



Thank You,

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

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

[Blake Carver]

You can set the log levels to DEBUG here
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L49-L64

Keep in mind that on version 3.2 you'll have Solr stuff being written into the 
sperate Solr server logs.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Hagenmaier, Wendy L 
Sent: Tuesday, June 7, 2022 12:59 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

Hi Blake,

When running ASpace (3.2.0) in production mode (as opposed to development 
mode), should we be seeing information in our error logs?

We are preparing to go live with 3.2.0. After testing 3.2.0 in development 
mode, we want to test our stage instance of ASpace 3.2.0 in production mode to 
mimic what our production instance will look like. We aren't getting any info 
from the logs in production mode, making it difficult to troubleshoot. Is there 
a way we can enable logs in production mode?

Thank you,
Wendy

Wendy Hagenmaier
Digital Curation Archivist
Service Owner, University Archives & Special Collections Repository and 
retroTECH<https://www.library.gatech.edu/retrotech>
Archives, Records Management, and Digital Curation
Georgia Tech Library
Atlanta, GA 30332
wendy.hagenma...@library.gatech.edu
Pronouns: she/her

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, June 1, 2022 5:02 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of 
development vs production mode

 https://archivesspace.github.io/tech-docs/development/dev.html
That explains the development mode.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Duckett, 
Brian (NIH/NLM) [C] 
Sent: Wednesday, June 1, 2022 4:45 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] 
; Kalyanasundaram, Sriram (NIH/NLM) [C] 

Subject: [Archivesspace_Users_Group] Requesting Clarification of development vs 
production mode


Hello,



A few weeks ago, we were attempting to resolve an issue with the Mizuno 
dependency being flagged during an internal security scan. During research 
efforts we came across the following post. 
https://archivesspace.org/archives/7226?utm_source=rss_medium=rss_campaign=archivesspace-update-december-2021



This post references two different modes ArchivesSpace can run in, development 
and production. We are seeking clarification of what the differences are 
between the two modes, how to implement one versus the other as well as verify 
which mode we are currently running in. Unfortunately, I have not found this 
information in the tech docs, so I do apologize in advance if the information 
is there and has been overlooked.



Thank You,

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

Re: [Archivesspace_Users_Group] Problems with oauth plugin

[Blake Carver]

add this:
  verify_ssl: false,
To you config, after metadata_parser_url and above the config: {

So it'll look something like this:


metadata_parser_url: "https://someloginurl.example;,
verify_ssl: false,
config: {
   blah blah blah



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Thursday, June 2, 2022 9:37 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Problems with oauth plugin

Thanks, Blake. Unfortunately, that did not do it. The install script works but 
we still get this complaint about the certificate verification:

I'm attaching the entire error as a separate file. Perhaps someone with more 
Ruby understanding will see something in there that I have not. If I could 
figure out what certificate/file it is looking at, perhaps I could track this 
down. Or maybe it is a red herring and there is something else going on in 
there.

Tom

On Wed, Jun 1, 2022 at 5:10 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
You might try this branch, there was a weird issue with that for a while, I 
think maybe this fixed that?
https://github.com/lyrasis/aspace-oauth/tree/unlock-address

This was the only change
https://github.com/lyrasis/aspace-oauth/pull/23/files

That was a while back, so things may have changed since on some of those gems.

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto: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, June 1, 2022 2:22 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Problems with oauth plugin

I'm having some problems with our Authentication with OKTA which I'm trying to 
understand.

Because of the problems, I've tried reinstalling the oauth plugin completely. 
The first problem I ran into was that the current download of:

https://github.com/lyrasis/aspace-oauth.git

Had a Gemfile containing the line:

gem 'addressable',   '2.8.0'

This caused some gem issues with our 2.81. version of ArchivesSpace because 
2.8.0 was evidently newer than the 2.7.0 version that is in the gems directory. 
I'm not savvy enough with Ruby to know how to deal with that so I simply 
updated the aspace-oauth Gemvile to read:

gem 'addressable',   '2.7.0'

Not sure if that is legit or not. But it allowed the initialize-plugin script 
to work.

But I'm still running into what was actually the original error we are getting. 
In the archivesspace.out file, we see this error:


INFO: An exception happened during JRuby-Rack startup
certificate verify failed
--- System
jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.312-b07 on 1.8.0_312-b07 +jit [linux-x86_64]
Time: 2022-06-01 13:57:45 -0400
Server: jetty/8.1.5.v20120716
jruby.home: uri:classloader://META-INF/jruby.home

--- Context Init Parameters:
jruby.max.runtimes = 1
jruby.min.runtimes = 1
public.root = /
rails.env = production

--- Backtrace
OpenSSL::SSL::SSLError: certificate verify failed
 connect at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1002
do_start at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:924
   start at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:913
 request at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1465

[and a lot more ruby stuff]
--

There seems to be some certificate that the plugin is not happy about. But I 
cannot determine what certificate it does not like. Both the local certificates 
and the OKTA certificates are valid. So what is the issue?

Anyone seen this before and have ideas?

Thanks,
Tom


--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://ci3.googleusercontent.com/mail-sig/AIorK4wQjvBdM9TFi5bR5RBsq_1dY3HTxh-Kg_4W690bwTCSKeVGyazMoj0wdmkNgJ0kfjeRnparhiw]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://ci3.googleusercontent.com/mail-sig/AIorK4wQjvBdM9TFi5bR5RBsq_1dY3HTxh-Kg_4W690bwTCSKeVGyazMoj0wdmkNgJ0kfjeRnparhiw]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Problems with oauth plugin

[Blake Carver]

You might try this branch, there was a weird issue with that for a while, I 
think maybe this fixed that?
https://github.com/lyrasis/aspace-oauth/tree/unlock-address

This was the only change
https://github.com/lyrasis/aspace-oauth/pull/23/files

That was a while back, so things may have changed since on some of those gems.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Wednesday, June 1, 2022 2:22 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Problems with oauth plugin

I'm having some problems with our Authentication with OKTA which I'm trying to 
understand.

Because of the problems, I've tried reinstalling the oauth plugin completely. 
The first problem I ran into was that the current download of:

https://github.com/lyrasis/aspace-oauth.git

Had a Gemfile containing the line:

gem 'addressable',   '2.8.0'

This caused some gem issues with our 2.81. version of ArchivesSpace because 
2.8.0 was evidently newer than the 2.7.0 version that is in the gems directory. 
I'm not savvy enough with Ruby to know how to deal with that so I simply 
updated the aspace-oauth Gemvile to read:

gem 'addressable',   '2.7.0'

Not sure if that is legit or not. But it allowed the initialize-plugin script 
to work.

But I'm still running into what was actually the original error we are getting. 
In the archivesspace.out file, we see this error:


INFO: An exception happened during JRuby-Rack startup
certificate verify failed
--- System
jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.312-b07 on 1.8.0_312-b07 +jit [linux-x86_64]
Time: 2022-06-01 13:57:45 -0400
Server: jetty/8.1.5.v20120716
jruby.home: uri:classloader://META-INF/jruby.home

--- Context Init Parameters:
jruby.max.runtimes = 1
jruby.min.runtimes = 1
public.root = /
rails.env = production

--- Backtrace
OpenSSL::SSL::SSLError: certificate verify failed
 connect at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1002
do_start at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:924
   start at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:913
 request at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/net/http.rb:1465

[and a lot more ruby stuff]
--

There seems to be some certificate that the plugin is not happy about. But I 
cannot determine what certificate it does not like. Both the local certificates 
and the OKTA certificates are valid. So what is the issue?

Anyone seen this before and have ideas?

Thanks,
Tom


--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu

[https://ci3.googleusercontent.com/mail-sig/AIorK4wQjvBdM9TFi5bR5RBsq_1dY3HTxh-Kg_4W690bwTCSKeVGyazMoj0wdmkNgJ0kfjeRnparhiw]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode

[Blake Carver]

 https://archivesspace.github.io/tech-docs/development/dev.html
That explains the development mode.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Duckett, 
Brian (NIH/NLM) [C] 
Sent: Wednesday, June 1, 2022 4:45 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] 
; Kalyanasundaram, Sriram (NIH/NLM) [C] 

Subject: [Archivesspace_Users_Group] Requesting Clarification of development vs 
production mode


Hello,



A few weeks ago, we were attempting to resolve an issue with the Mizuno 
dependency being flagged during an internal security scan. During research 
efforts we came across the following post. 
https://archivesspace.org/archives/7226?utm_source=rss_medium=rss_campaign=archivesspace-update-december-2021



This post references two different modes ArchivesSpace can run in, development 
and production. We are seeking clarification of what the differences are 
between the two modes, how to implement one versus the other as well as verify 
which mode we are currently running in. Unfortunately, I have not found this 
information in the tech docs, so I do apologize in advance if the information 
is there and has been overlooked.



Thank You,

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

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

Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

[Blake Carver]

r/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>
 
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>
 
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 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

I've been monitoring logs and have run into a couple of instances where I 
receive this type of error:

E, [2022-05-16T08:57:57.207392 #5273] ERROR -- : Thread-3962: Unhandled 
exception!
E, [2022-05-16T08:57:57.207810 #5273] ERROR -- :
invalid byte sequence in UTF-8

and then a lot of detail. Are these errors with data that should be addressed?  
I'm still in DEBUG mode in the backend log but it is not clear how to figure 
out which record(s) are being flagged. What am I looking for

Re: [Archivesspace_Users_Group] Errors Upgrading from 2.7.0 to 2.8.1

[Blake Carver]

That looks pretty bad, not sure what it means, but I would start over, maybe 
something is missing or there's a bad plugin or some other mysterious thing has 
failed.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Corinne 
Chatnik 
Sent: Wednesday, May 18, 2022 3:25 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Errors Upgrading from 2.7.0 to 2.8.1


Hi,



Trying to upgrade from 2.7.0 to 2.8.1 and we keep getting the same error 
repeated over and over for nearly every record and we don’t know where to start 
looking. I’ve done a complete reindex and redid the database migration etc. The 
log file keeps repeating this:

E, [2022-05-18T14:07:50.629287 #48326] ERROR -- : Thread-2902: Unhandled 
exception!

E, [2022-05-18T14:07:50.630620 #48326] ERROR -- :

comparison of NilClass with 0 failed

org/jruby/RubyEnumerable.java:574:in `sort_by'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/relationships.rb:347:in
 `find_by_participant'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/relationships.rb:411:in
 `who_participates_with'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/mixins/relationships.rb:545:in
 `related_records'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/top_container.rb:170:in
 `find_subcontainer_barcodes'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/top_container.rb:190:in
 `block in sequel_to_jsonmodel'

org/jruby/RubyArray.java:1809:in `each'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/top_container.rb:184:in
 `sequel_to_jsonmodel'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:336:in
 `block in resolve'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in
 `open'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:335:in
 `block in resolve'

org/jruby/RubyHash.java:1415:in `each'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:331:in
 `block in resolve'

org/jruby/RubyGenerator.java:104:in `each'

org/jruby/RubyEnumerator.java:396:in `each'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:247:in
 `block in fetch_records_by_uri'

org/jruby/RubyHash.java:1415:in `each'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:241:in
 `fetch_records_by_uri'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:130:in
 `resolve_references'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/uri_resolver.rb:44:in
 `resolve_references'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:113:in
 `listing_response'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/crud_helpers.rb:68:in
 `handle_listing'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/archival_object.rb:97:in
 `block in ArchivesSpaceService'

org/jruby/RubyBasicObject.java:2622:in `instance_eval'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:368:in
 `block in GET /repositories/:repo_id/archival_objects'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:105:in
 `block in open'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:69:in
 `block in transaction'

/opt/archivesspace-2.8.1/gems/gems/sequel-5.9.0/lib/sequel/database/transactions.rb:204:in
 `_transaction'

/opt/archivesspace-2.8.1/gems/gems/sequel-5.9.0/lib/sequel/database/transactions.rb:179:in
 `block in transaction'

/opt/archivesspace-2.8.1/gems/gems/sequel-5.9.0/lib/sequel/connection_pool/threaded.rb:91:in
 `hold'

/opt/archivesspace-2.8.1/gems/gems/sequel-5.9.0/lib/sequel/database/connecting.rb:270:in
 `synchronize'

/opt/archivesspace-2.8.1/gems/gems/sequel-5.9.0/lib/sequel/database/transactions.rb:145:in
 `transaction'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:68:in
 `transaction'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:104:in
 `block in open'

/opt/archivesspace-2.8.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:101:in

Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

[Blake Carver]

> - 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 
 on behalf of Tom 
Hanstra 
Sent: Wednesday, May 18, 2022 3:21 PM
To: Archivesspace Users Group 
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>
 
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 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

I've been monitoring logs and have run into a couple of instances where I 
receive this type of error:

E, [2022-05-16T08:57:57.207392 #5273] ERROR -- : Thread-3962: Unhandled 
exception!
E, [2022-05-16T08:57:57.207810 #5273] ERROR -- :
invalid byte sequence in UTF-8

and then a lot of detail. Are these errors with data that should be addressed?  
I'm still in DEBUG mode in the backend log but it is not clear how to figure 
out which record(s) are being flagged. What am I looking for?

Thanks,
Tom

On Thu, May 12, 2022 at 8:59 AM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
> 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<mailto: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 11, 2022 9:30 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
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-809

Re: [Archivesspace_Users_Group] Browser Access Not Working

[Blake Carver]

That sounds like it's not running at all. Check the archivesspace.out file in 
the logs directory for errors.



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Heidi R. 
Pettitt 
Sent: Friday, May 13, 2022 6:00 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Browser Access Not Working


Thanks to everyone that has responded. Kevin added the following details this 
afternoon:



I’m using the instructions linked below. I’m stuck on Step #11 which says to 
wait until you see port 8080 min a listening state and it never happens.  Is 
there a step I’m missing?



https://github.com/timpetro/archivesspace-install/blob/main/Install%20ArchivesSpace%20on%20Windows.txt



Thanks,



~ Heidi



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Heidi R. 
Pettitt
Sent: Thursday, May 12, 2022 10:03 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Browser Access Not Working



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.

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]

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 
 on behalf of Tom 
Hanstra 
Sent: Monday, May 16, 2022 10:43 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

I've been monitoring logs and have run into a couple of instances where I 
receive this type of error:

E, [2022-05-16T08:57:57.207392 #5273] ERROR -- : Thread-3962: Unhandled 
exception!
E, [2022-05-16T08:57:57.207810 #5273] ERROR -- :
invalid byte sequence in UTF-8

and then a lot of detail. Are these errors with data that should be addressed?  
I'm still in DEBUG mode in the backend log but it is not clear how to figure 
out which record(s) are being flagged. What am I looking for?

Thanks,
Tom

On Thu, May 12, 2022 at 8:59 AM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
> 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<mailto: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 11, 2022 9:30 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
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.

Re: [Archivesspace_Users_Group] Browser Access Not Working

[Blake Carver]

That sounds like it's not running at all. Check the archivesspace.out file in 
the logs directory for errors.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Heidi R. 
Pettitt 
Sent: Thursday, May 12, 2022 11:02 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Browser Access Not Working


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<mailto: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: Tuesday, May 10, 2022 4:15 PM
To: Archivesspace Users Group 
<mailto:archivesspace_users_group@lyralists.lyrasis.org>
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

Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

[Blake Carver]

 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, that would help.

Tom


On Tue, May 10, 2022 at 2:17 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
> Is this possible?

Short answer, Yes, it's possible your indexer is starting over.

Long answer. This can be tricky to figure out. Something is wrong, the indexer 
never wants to do that. Sometimes "something" "bad" gets into ArchivesSpace and 
the indexer will just crash and start over. The problem is the "something" can 
be anything and the "bad" can be hard to figure out. The more stuff you have in 
your DB, the harder it is to figure out.

First, I'd make sure this is happening. Your logs should make it obvious. You 
might see some FATAL errors just before it starts over.  You MIGHT be able to 
narrow it down from that. That is, what group of records had that error in the 
logs? Maybe that narrows it down enough. You just got lucky!

I don't think I've ever been so lucky. What I'd do next is set your loglevel to 
DEBUG and restart. If you're feeling lucky or just impatient or both, leave the 
indexer speed as is. You'll get more details out of the logs and you should be 
able to narrow it down better. Ideally, you want to run the indexers at 1x1, 
which means it could take forrreeevver to get back around to the crash 
again. If you're lucky, it'll crash on a record, you'll go look at that record, 
the problem will be obvious, and there will be much rejoicing. With it running 
1x1 you should see exactly what's causing the fail. If it's not crashing on the 
same record every time ugh. That's an even longer answer.




From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto: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: Tuesday, May 10, 2022 10:23 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] (re)indexing in 2.8.1

I don't look at the logs a lot unless there are issues with ArchivesSpace, so 
maybe this is something normal. But, after a restart due to some complaints 
about database connectivity, it looks like our ArchivesSpace instance has 
decided to do a full reindex. The index log sure looks as if it is starting 
from scratch and running through the indexing of both PUI and Staff indexes.

Is this possible?  Is it something that happens periodically and I just did not 
notice it? Nothing has changed in my data directory, so I don't see any reason 
for indexing to occur. Yet that is what the logs show.

If it is doing this for some reason, and knowing that we restart periodically, 
it seems like we will get into a loop where indexing just keeps happening all 
the time. Also, it would be helpful to understand what caused this to happen.

Any thoughts or experiences from those who have run this for longer would be 
appreciated. I'd like to understand if it would be a good idea to clear the 
data directory and perform a full index over the weekend ra

Re: [Archivesspace_Users_Group] (re)indexing in 2.8.1

[Blake Carver]

> Is this possible?

Short answer, Yes, it's possible your indexer is starting over.

Long answer. This can be tricky to figure out. Something is wrong, the indexer 
never wants to do that. Sometimes "something" "bad" gets into ArchivesSpace and 
the indexer will just crash and start over. The problem is the "something" can 
be anything and the "bad" can be hard to figure out. The more stuff you have in 
your DB, the harder it is to figure out.

First, I'd make sure this is happening. Your logs should make it obvious. You 
might see some FATAL errors just before it starts over.  You MIGHT be able to 
narrow it down from that. That is, what group of records had that error in the 
logs? Maybe that narrows it down enough. You just got lucky!

I don't think I've ever been so lucky. What I'd do next is set your loglevel to 
DEBUG and restart. If you're feeling lucky or just impatient or both, leave the 
indexer speed as is. You'll get more details out of the logs and you should be 
able to narrow it down better. Ideally, you want to run the indexers at 1x1, 
which means it could take forrreeevver to get back around to the crash 
again. If you're lucky, it'll crash on a record, you'll go look at that record, 
the problem will be obvious, and there will be much rejoicing. With it running 
1x1 you should see exactly what's causing the fail. If it's not crashing on the 
same record every time ugh. That's an even longer answer.




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

I don't look at the logs a lot unless there are issues with ArchivesSpace, so 
maybe this is something normal. But, after a restart due to some complaints 
about database connectivity, it looks like our ArchivesSpace instance has 
decided to do a full reindex. The index log sure looks as if it is starting 
from scratch and running through the indexing of both PUI and Staff indexes.

Is this possible?  Is it something that happens periodically and I just did not 
notice it? Nothing has changed in my data directory, so I don't see any reason 
for indexing to occur. Yet that is what the logs show.

If it is doing this for some reason, and knowing that we restart periodically, 
it seems like we will get into a loop where indexing just keeps happening all 
the time. Also, it would be helpful to understand what caused this to happen.

Any thoughts or experiences from those who have run this for longer would be 
appreciated. I'd like to understand if it would be a good idea to clear the 
data directory and perform a full index over the weekend rather than an 
unexpected and possibly never ending round in the background.

Thanks,
Tom
--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu

[https://ci3.googleusercontent.com/mail-sig/AIorK4wQjvBdM9TFi5bR5RBsq_1dY3HTxh-Kg_4W690bwTCSKeVGyazMoj0wdmkNgJ0kfjeRnparhiw]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Searching by Agents and Subjects Results in "something went wrong."

[Blake Carver]

It's only agents and subjects? Resources look fine?
I'd really expect that error to put a FATAL or ERROR in the logs, especially on 
debug. If not, did you bring over anything from the /data/ directory from 2.6 
to 3.2?
If so, get rid of that stuff.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Patterson, Eli 
Sent: Friday, April 29, 2022 4:08 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Searching by Agents and Subjects Results 
in "something went wrong."

Greetings ArchivesSpace list-serve,

I'm hoping to get some advice or suggestions on a problem we're having when 
trying to migrate from 2.6.0 to 3.2.0.

When searching by /agents or /subjects, the return list is populated.  Drilling 
down on any of the results (e.g. attempting to access /subjects/253) results in 
the error screen "We're sorry, but something went wrong."

The ASpace logs look clean, only getting the request, even though I've put them 
into DEBUG mode.

The only thing that looks suspicious to me is in the solr logs:

2022-04-28 15:52:28.586 INFO  (qtp576020159-15) [   x:archivesspace] 
o.a.s.c.S.Request [archivesspace]  webapp=/solr path=/select 
params={mm=100%25=(uri:("\/subjects\/253"))=\=true=0="=-exclude_by_default:true=publish:true=types:pui=1=json=true}
 hits=1 status=0 QTime=1
2022-04-28 15:52:28.607 INFO  (qtp576020159-56) [   x:archivesspace] 
o.a.s.c.S.Request [archivesspace]  webapp=/solr path=/select 
params={mm=100%25=(id:("global"))=\=true=0="=-exclude_by_default:true=-types:pui_only=suppressed:false=500=json=true}
 hits=0 status=0 QTime=0
2022-04-28 15:52:28.802 INFO  (qtp576020159-95) [   x:archivesspace] 
o.a.s.c.S.Request [archivesspace]  webapp=/solr path=/select 
params={mm=100%25=primary_type=published_agents=used_within_published_repository=\=0=((types:("agent")+OR+(types:("digital_object")+OR+(types:("archival_object")+OR+(types:("accession")+OR+(types:("resource")+OR+(types:("repository"=-exclude_by_default:true=publish:true=types:pui=title_sort+asc=50=subjects:"Academic+freedom."+AND+types:pui=100=edismax=four_part_id^3+title^2+finding_aid_filing_title^2+fullrecord=four_part_id^4=true="=0=json=true}
 hits=1 status=0 QTime=1
2022-04-28 15:52:28.874 INFO  (qtp576020159-18) [   x:archivesspace] 
o.a.s.c.S.Request [archivesspace]  webapp=/solr path=/select 
params={mm=100%25=(id:("\/repositories\/2"))=\=true=0="=-exclude_by_default:true=-types:pui_only=suppressed:false=500=json=true}
 hits=1 status=0 QTime=0

Thank you for your time.


-

Eli Patterson

Systems Support Engineer Sr | Library IT

Georgia Institute of Technology

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

Re: [Archivesspace_Users_Group] Solr 8.11.1?

[Blake Carver]

Joshua Shaw reported ArchivesSpace  being bit by a bug in 8.11.0 back in 
November.
https://www.mail-archive.com/users@solr.apache.org/msg02012.html
That was fixed in 8.11.1

I think, so far, 8.11.0 is the only version to avoid.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Zhang, 
Bin 
Sent: Thursday, April 7, 2022 11:24 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Solr 8.11.1?


Hi Kyle,



I was able to install Solr 8.11.1 on the same ubuntu box where AS 3.2.0 is 
installed.  Everything seems to be working fine.





Bin Zhang (he/him)

Systems & Technologies Librarian

Library Systems and IT Services, University Library

California State University, Sacramento

bzh...@csus.edu | (916) 278-5664

Zoom: https://csus.zoom.us/my/bzhang



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Kyle 
Breneman
Sent: Thursday, April 7, 2022 7:58 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Solr 8.11.1?



And…I just found the 8.10 installer.



Kyle Breneman

Integrated Digital Services Librarian

The University of Baltimore

kbrene...@ubalt.edu

I believe in freedom of thought and

freedom of speech. Do you?



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Kyle Breneman
Sent: Thursday, April 7, 2022 10:55 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Solr 8.11.1?



[EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover 
over any links before clicking and use caution when opening attachments.]



Is anyone out there running ArchivesSpace 3.2.0 with Solr 8.11.1?  I see that 
the officially supported version of Solr is 8.10, but I cannot seem to find an 
installer for 8.10.



Kyle Breneman

Integrated Digital Services Librarian

The University of Baltimore

kbrene...@ubalt.edu

I believe in freedom of thought and

freedom of speech. Do you?


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

Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

[Blake Carver]

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2022-March/009092.html

You can probably just:
UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Though might need to:

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 10:55 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Little bit more information- running v.2.8.1 and MariaDB 5.5.68.

Time complained about is eg

Time: 2022-03-28 15:46:28 +0100



So basically any startup time + 0100 (I'm not sure which table it would be 
writing to there), which puts it into the future- no longer blaming users! I am 
guessing that a reindex won't solve this; my time_zone settings are unchanged.


MariaDB [(none)]> SELECT @@global.time_zone, @@session.time_zone;

++-+

| @@global.time_zone | @@session.time_zone |

++-+

| SYSTEM | SYSTEM  |

++-+

1 row in set (0.00 sec)


Cheers

Scott


Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

--- System

jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.322-b06 on 1.8.0_322-b06 +jit [linux-x86_64]

Time: 2022-03-28 15:46:28 +0100

Server: jetty/8.1.5.v20120716

jruby.home: uri:classloader://META-INF/jruby.home


--- Context Init Parameters:

jruby.max.runtimes = 1

jruby.min.runtimes = 1

public.root = /

rack.env = production


--- Backtrace

Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

   raise_error at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/misc.rb:419

 statement at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:677

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:239

  hold at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/connection_pool/threaded.rb:87

   synchronize at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/connecting.rb:270

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:238

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:1082

fetch_rows at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:726

 with_sql_each at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:934

with_sql_first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:944

single_record! at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:700

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:243

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/plugins.rb:33

[] at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb:214

create_system_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:

 create_hidden_system_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:21

create_search_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:306

   at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:330

 at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:1

   require at org/jruby/RubyKernel.java:974

  require_relative at org/jruby/RubyKernel.java:1002

  ArchivesSpaceService at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:195

  open at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:105

   transaction at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:69

  _transaction at 

Re: [Archivesspace_Users_Group] Generating a list of collections URLs

[Blake Carver]

 Hey Dan

Do you get access to the DB there? If so, it would be pretty easy to just do a 
direct MySQL query for that and build the URLS from the IDs.

I did look at the reports on test:
https://test.archivesspace.org/staff/custom_report_templates/new
And I don't see a way to do exactly what you want, though I could be missing 
something obvious there. I haven't worked through all the options.

That being said...

I'm not quite sure what you mean... "there is interest to ensure that all of 
our catalog finding aid records actually have ArchivesSpace URLs."

Do you mean you just want to be sure they're all PUBLISHED?

If that's it, then the 3.2 report DO have a limit for "Published" so you can 
build any Resources report on PUBLISHED and know what's there on the PUI. So 
that would get you close.

Anything that has the "Published" checkbox checked has a PUI URL.

The API would be another option. Not sure if you have access to that either.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Cornwall, Daniel D (EED) 
Sent: Tuesday, March 22, 2022 4:44 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Generating a list of collections URLs


Hi All,



My institution has cataloged our finding aids into our regular library catalog. 
With our recent-ish migration to ArchivesSpace, there is interest to ensure 
that all of our catalog finding aid records actually have ArchivesSpace URLs.



I know there is a resource list report in AS, but it doesn’t provide the URL. 
Ideally, I’d like a report that lists:



Collection Name

Collection Identifier

Collection URL



For example,



George L. Harrington Photograph Collection, ca. 1909-1917

Identifier: PCA 6

https://alaska.libraryhost.com/repositories/2/resources/458



We’re currently on v. 3.1.1 – Could such a report be run on this version, and 
if not, could something like this be run in the custom reports module in 3.2? 
I’m not sure we’d immediately upgrade if we couldn’t get such a report anyway.



Thanks for any thoughts, insight or experience. - Daniel









[cid:image001.png@01D83DEA.286A0CF0]



Daniel Cornwall

Pronouns: he/him/his

Continuing Resources Libarian

Information Services Staff, Alaska State Library



Andrew P. Kashevaroff Building

Phone: 907.465.2988

Mail: PO Box 110571, Juneau, AK 99811

Visit: 395 Whittier St., Juneau, AK 99801



email | web |  
sign up for event 
notifications






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

Re: [Archivesspace_Users_Group] Rights statements not showing up in the public interface

[Blake Carver]

Aha, yep! That's the one I was thinking of though.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Andrew 
Morrison 
Sent: Tuesday, March 22, 2022 4:41 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface


There is this issue:


https://archivesspace.atlassian.net/browse/ANW-1055


But that is only about fields in the "Finding Aid Data" section, not rights 
statements.


Andrew.



On 21/03/2022 18:52, Blake Carver wrote:
I think that might be one of the fields that isn't on the PUI?
I know there's a JIRA in there somewhere that covers this. Maybe not Rights 
Statements in particular, but various fileds that don't show up on the PUI.
JIRA hates me, and I can't seem to find it. Maybe someone else is better 
friends with JIRA and can find that one.
Something about fields that aren't on the PUI. I think there is a list of a few 
on that JIRA at least.

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 on behalf of Dean DeBolt <mailto:ddeb...@uwf.edu>
Sent: Monday, March 21, 2022 1:45 PM
To: Archivesspace Users Group 
<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface

Yes, I need to know how to add the language.  I can add it by editing the html 
but it does
not save to change the page.

Dean DeBolt, University Librarian (Professor)/University Archivist
UWF Archives and West Florida History Center
University of West Florida Library
11000 University Parkway
Pensacola, FL  32514-5750
ddeb...@uwf.edu<mailto:ddeb...@uwf.edu>;   850-474-2213

West Florida History Center is the largest and most comprehensive
history collection about Pensacola and the West Florida region.
http://libguides.uwf.edu/universityarchives

Digital collections can be found at:  http://uwf.lyrasistechnology.org 
<http://archives.uwf.edu/>
and http://uwf.digital.flvc.org

If we've been of service, please let us know or our administration,
Dean of Libraries mailto:scla...@uwf.edu>>




On Mon, Mar 21, 2022 at 12:44 PM Mary Weppler 
mailto:mwepp...@csustan.edu>> wrote:

Hello,



I have added rights statements and rights notes to our resources records, 
however this information does not appear in the public interface.  I am 
wondering if anyone else has encountered this issue?



Thank you!



Mary

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



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

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

Re: [Archivesspace_Users_Group] Rights statements not showing up in the public interface

[Blake Carver]

I think that might be one of the fields that isn't on the PUI?
I know there's a JIRA in there somewhere that covers this. Maybe not Rights 
Statements in particular, but various fileds that don't show up on the PUI.
JIRA hates me, and I can't seem to find it. Maybe someone else is better 
friends with JIRA and can find that one.
Something about fields that aren't on the PUI. I think there is a list of a few 
on that JIRA at least.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Dean 
DeBolt 
Sent: Monday, March 21, 2022 1:45 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface

Yes, I need to know how to add the language.  I can add it by editing the html 
but it does
not save to change the page.

Dean DeBolt, University Librarian (Professor)/University Archivist
UWF Archives and West Florida History Center
University of West Florida Library
11000 University Parkway
Pensacola, FL  32514-5750
ddeb...@uwf.edu;   850-474-2213

West Florida History Center is the largest and most comprehensive
history collection about Pensacola and the West Florida region.
http://libguides.uwf.edu/universityarchives

Digital collections can be found at:  http://uwf.lyrasistechnology.org 

and http://uwf.digital.flvc.org

If we've been of service, please let us know or our administration,
Dean of Libraries mailto:scla...@uwf.edu>>




On Mon, Mar 21, 2022 at 12:44 PM Mary Weppler 
mailto:mwepp...@csustan.edu>> wrote:

Hello,



I have added rights statements and rights notes to our resources records, 
however this information does not appear in the public interface.  I am 
wondering if anyone else has encountered this issue?



Thank you!



Mary

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

Re: [Archivesspace_Users_Group] 'Tis The Season For Ye Ol' "HOUR_OF_DAY: 2 -> 3" Error :-(

[Blake Carver]

I think it's just a spring thing? Though I can't remember, pretty sure at least.
This year it would seem to be a more widespread problem that previous years, 
though I don't know if that's something to do with the new version, or just bad 
luck.
It seems like in the past it was rather rare, and this year, maybe not so rare?

I haven't seen anyway to proactively mitigate the problem.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Monday, March 14, 2022 9:42 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] 'Tis The Season For Ye Ol' 
"HOUR_OF_DAY: 2 -> 3" Error :-(

Thanks, Blake. We actually got hit with this yesterday and I did not see your 
message. A quick Google search found the issue, however.

What do other sites do to mitigate this?  Does everyone just wait until after 
the DST change to see if things broke?  Or are they ways to proactively 
mitigate this?

Also, can I expect the same thing when we "Fall back"?  Or is this somehow just 
a Spring issue?

Thanks,
Tom

On Sun, Mar 13, 2022 at 2:34 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
Yet another reason to hate Daylight Savings Time...
Some of you may notice troubles this morning. There's a weird little bug that 
happens when the clocks change. It doesn't hit ALL sites, but we had some 
hosted sites hit this year for the first time, so I thought I'd put this at the 
top O' the list.

There's a JIRA here:
https://archivesspace.atlassian.net/browse/ANW-1229

It's PROBABLY the search_indexer user, and can be fixed by doing:
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='search_indexer';

You might need to restart after updating the user

If you're not quite so lucky, it could be hiding elsewhere, another user, or an 
AO or a Date.

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';


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


--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Help: Which version(s) of ASpace support MySQL 8.x?

[Blake Carver]

It should be fine to run the latest version (3.2) on MySQL 8. I think most 
likely anything above version 3 should be ok.
There were some reports issues on some older versions of ArchivesSpace

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jerry 
Boggio 
Sent: Monday, March 14, 2022 10:45 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Help: Which version(s) of ASpace support 
MySQL 8.x?


Resubmitting as it appears my original question was kicked back.



Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info 
Management | 781-271-2719



From: Jerry Boggio 
Sent: Monday, March 14, 2022 10:23 AM
To: archivesspace_users_group-requ...@lyralists.lyrasis.org
Subject: Help: Which version(s) of ASpace support MySQL 8.x?



Hi Everyone;



Could someone please tell me which version of ASpace first started support 
MySQL version 8? We are currently running version 5.7.1 of ASpace and wonder if 
that supports MySQL v8.



Thank you!

Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info 
Management | 781-271-2719


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

Re: [Archivesspace_Users_Group] Help: Does ASpace support Okta/SSO/SAML?

[Blake Carver]

 There's a plugin here:
https://github.com/lyrasis/aspace-oauth


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Peter 
Heiner 
Sent: Monday, March 14, 2022 11:40 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Help: Does ASpace support 
Okta/SSO/SAML?

Cambridge University Libraries use the aspace-oauth plugin with the SAML
provider.

We chose SAML over LDAP because our directory doesn't allow anonymous binds
and ArchivesSpace requires a separate bind DN which I was not too keen on
having. SAML was not particularly easy to set up, we've seen some quirks like
it not being able to use our IdP's metadata autoconfiguration and us having to
add config items that would be available from said metadata, but it can be
made to work with some trial and error.

The separate login link in the header that aspace-oauth creates felt pretty
clunky, so we have also modified the main app page in our local plugin to take
the user directly to the SSO login page unless a specific URL parameter is
set.

Sadly, only the database is supported for authorisation, none of those
fancy-schmancy SAML attributes or Oauth2 claim shenanigans from the early 21st
century.

p

Jerry Boggio wrote on 2022-03-14 14:45:01:
> Resubmitting as it appears my original question was kicked back.
>
> Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info 
> Management | 781-271-2719
>
> From: Jerry Boggio 
> Sent: Monday, March 14, 2022 10:28 AM
> To: archivesspace_users_group-requ...@lyralists.lyrasis.org
> Subject: Help: Does ASpace support Okta/SSO/SAML?
>
> Hi Everyone;
>
> Could someone please tell us if ArchivesSpace supports Okta, SSO (Single Sign 
> On), and/or SAML (Security Assertion Markup Language)? Are there other 
> security packages supported other than storing logon ID and password in the 
> MySQL database? If so, could you please pass on documentation?
>
> Thank you!
> Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info 
> Management | 781-271-2719
>

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

[Archivesspace_Users_Group] 'Tis The Season For Ye Ol' "HOUR_OF_DAY: 2 -> 3" Error :-(

[Blake Carver]

Yet another reason to hate Daylight Savings Time...
Some of you may notice troubles this morning. There's a weird little bug that 
happens when the clocks change. It doesn't hit ALL sites, but we had some 
hosted sites hit this year for the first time, so I thought I'd put this at the 
top O' the list.

There's a JIRA here:
https://archivesspace.atlassian.net/browse/ANW-1229

It's PROBABLY the search_indexer user, and can be fixed by doing:
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='search_indexer';

You might need to restart after updating the user

If you're not quite so lucky, it could be hiding elsewhere, another user, or an 
AO or a Date.

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';


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

Re: [Archivesspace_Users_Group] Spreadsheet error translation

[Blake Carver]

This was a bit of a error "Turducken"... it's an error bug hiding the error.
It was in older versions (maybe < 2.8?) and was fixed in a newer version (2.8.1 
maybe?).
If I'm remembering correctly an error is raised and that 'pretty_inspect' barfs 
on it and rather than showing the error, it just shows the pretty_inspect error.
If I'm remembering correctly, again, the real error shows up in the logs, so 
take a look there for the real problem.



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of James E. 
Cross 
Sent: Tuesday, February 22, 2022 11:49 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Spreadsheet error translation


Can anyone tell me what {"error":"undefined method `pretty_inspect' for #"} is 
indicating when I try and load a spreadsheet? Because of size limitations I had 
to divide up a subseries; I get this error when I try to add the next segment. 
Thank you.





James Edward Cross, C.A. CLEMSON UNIVERSITY

Manuscripts Archivist

Special Collections and Archives

Clemson University Libraries

Box 343001

Clemson, SC  29634-3001

Phone: (864) 656-5182

Website: http://library.clemson.edu/depts/specialcollections/

Pronouns: he/him/his

Traditional Cherokee Lands | Site of Fort Hill Plantation

Please do not feel obligated to respond to this message outside of your normal 
working hours.


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

Re: [Archivesspace_Users_Group] Reorder mode in 3.1.0

[Blake Carver]

That is a new bug, just found the other day.

It would be good if you could add that to the issue here:
https://archivesspace.atlassian.net/browse/ANW-1435

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Nic 
Stanton-Roark 
Sent: Tuesday, October 26, 2021 11:43 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Reorder mode in 3.1.0

Hi all,

Since upgrading to 3.1.0 I've noticed an issue with reorder mode. Records can 
be reordered and cut and paste, but when working with resources in a lower 
level of hierarchy, attempting to drag (or cut and paste) a resource kicks that 
resource up to the higher level. For example, moving the Dinners, Etc. file 
here to the General, 1945-1988 and selecting "Add items before" ends up with 
the record moved up to the series level.

[image.png]
[image.png]

[image.png]
The file can then be re-added to the series as a child as normal. Nothing is 
noted in the logs during this, and it has persisted through both soft and hard 
reindexing. Is this a known issue or is there an obvious type of cause to 
investigate?

Thanks for any advice.

[https://anderson.edu/uploads/au-email-logo.gif]
Nicholas Stanton-Roark  |  Archivist  | Robert A. Nicholson University Library
Anderson University  |  1100 E. Fifth St, Anderson, IN 46012
(765) 641-4285  |  
ndro...@anderson.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] File naming errors in PUI

[Blake Carver]

Looks like this is a bug in 3.1, there's a JIRA here now
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1431

From: Blake Carver 
Sent: Thursday, September 30, 2021 4:03 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] File naming errors in PUI

Might just be missing from the locales:
https://github.com/archivesspace/archivesspace/blob/master/public/config/locales/en.yml#L178-L179

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Nic 
Stanton-Roark 
Sent: Thursday, September 30, 2021 1:58 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] File naming errors in PUI

Hi all,

This week we upgraded from 2.7.1 to 3.1.0. Soft reindexing took care of most 
apparent issues, but one thing that newly appears is that files with dates but 
no utilized name field display with the description "translation missing: 
en.inherited" as so:

[image.png]

Is this either a known issue or is there a way to detect the issue in our logs? 
Thanks for any guidance you can provide

Best wishes,
Nic


[https://anderson.edu/uploads/au-email-logo.gif]
Nicholas Stanton-Roark  |  Archivist  | Robert A. Nicholson University Library
Anderson University  |  1100 E. Fifth St, Anderson, IN 46012
(765) 641-4285  |  
ndro...@anderson.edu<mailto:ndro...@anderson.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] LCNAF NoMethodError

[Blake Carver]

Double check and make sure you have the right version, maybe somehow it has the 
wrong one in place.
https://github.com/archivesspace-plugins/lcnaf

For ArchivesSpace versions 2.8.1 and earlier, use the 1.0.0 tag. For 
ArchivesSpace version 3.0.0 , use the 2.0.0 tag.

I've heard of places getting firewalled by the LoC servers, that "network is 
unreachable" error reminded me of that. Double check you can get to id.loc.gov 
from the server.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jared 
Hutchens 
Sent: Tuesday, October 19, 2021 11:17 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] LCNAF NoMethodError

Hi everyone,

Our LCNAF plugin has been returning the fatal error: NoMethodError (undefined 
method 'entries' for 10:Integer) whenever anything is searched on it. From what 
I can tell all of the plugin files are exactly as what came bundled in with the 
ArchivesSpace v3.1 build (which we upgraded to from 2.7.1 a few weeks ago, but 
our plugin wasn't working then either). I also cross-referenced the files with 
the LCNAF plugin's github directory and they matched as well.

This might not be related but just before this error the plugin was returning a 
different error: Enetunreach (network is unreachable), which seemed to be a 
result of the server's network not having IPv6 connectivity and disappeared 
after adding a 6to4 tunnel. I only add this info in the case it is the culprit 
because otherwise the plugin files have been left alone and the overall 
installation has been mostly untouched except for the fixing of a few locale 
files plus a reindex.

I've been absolutely stumped so any and all advice would be much appreciated.
Thanks,
Jared

[https://lh4.googleusercontent.com/2cqdpPanpPHRmQo0drMK5LKoNeS631xRPI1vOTtHcbn8d9ESe8UB7kSF2L-gp9vSpOrGADAfgyrcbVyGk_9S1X8uiCr3IEpvio7nu-2N-OtSYGMWWsZd-h1S5d-Sv3-j3KXXFWWb]


Jared Hutchens  | Library Technology Specialist  | Nicholson Library

Anderson University  |  1100 E. 5th St., Anderson, IN 46012

(765) 641-4270  | jmhutch...@anderson.edu  | 
library.anderson.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] File naming errors in PUI

[Blake Carver]

Might just be missing from the locales:
https://github.com/archivesspace/archivesspace/blob/master/public/config/locales/en.yml#L178-L179

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Nic 
Stanton-Roark 
Sent: Thursday, September 30, 2021 1:58 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] File naming errors in PUI

Hi all,

This week we upgraded from 2.7.1 to 3.1.0. Soft reindexing took care of most 
apparent issues, but one thing that newly appears is that files with dates but 
no utilized name field display with the description "translation missing: 
en.inherited" as so:

[image.png]

Is this either a known issue or is there a way to detect the issue in our logs? 
Thanks for any guidance you can provide

Best wishes,
Nic


[https://anderson.edu/uploads/au-email-logo.gif]
Nicholas Stanton-Roark  |  Archivist  | Robert A. Nicholson University Library
Anderson University  |  1100 E. Fifth St, Anderson, IN 46012
(765) 641-4285  |  
ndro...@anderson.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] Apache/httpd interfering with ASpace functionality

[Blake Carver]

Check your Apache logs for errors. Sounds like maybe it's some kind of issue 
there.
Also, check the browser devtools counsel for errors, they are likely to show up 
there too.
Also check the archivesspace.out log for errors, might be something in there.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Huebschen, Alan M 
Sent: Wednesday, September 29, 2021 1:06 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Apache/httpd interfering with ASpace 
functionality


Good morning,


I have recently been made aware of some issues with functionality in our 
ArchivesSpace instance. Users are unable to perform some tasks, such as use the 
"Delete" button to delete records. I have tested my dev and prod copies of 
ASpace against local and remote DBs. My dev instance works perfectly fine, it 
does not use Apache/httpd for SSL/TLS but our production instance does. When I 
bypass Apache/httpd on the production instance, all of the functionality issues 
vanish.


We are currently running ArchivesSpace v3.1.0 and just upgraded from v2.8.0. 
The issues began in v2.8.0 and remain after our upgrade to v3.1.0.


Has anyone else run into similar issues with Apache/httpd or Nginx interfering 
with ASpace functionality? How did you resolve it?


I'm happy to provide more details if needed.


Thank you,


-Alan Huebschen

Brookens Library Information Systems

University of Illinois Springfield
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] error - agent table is full

[Blake Carver]

Just for the record, the problem was indeed disc space.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Peter 
Heiner 
Sent: Friday, September 24, 2021 7:13 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] error - agent table is full

Hi Sean,

This is a MySQL error relating to either the database server running out of 
disk space or the database hitting the maximum autoextend size, see
https://stackoverflow.com/questions/730579/1114-hy000-the-table-is-full

p


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Parke, 
Sean 
Sent: 24 September 2021 11:58
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] error - agent table is full


Hello,



When I try to create a new agent record, I get the error message “translation 
missing: en.no key - translation missing: 
en.validation_errors.database_integrity_constraint_conflict__java__javasql__sqlexception__the_table__agent_person__is_full”



Anyone know how to address this? We are still on version 2.3.0



Thanks,



Sean Parke

University Archivist

University of Hartford

Archives & Special Collections

spa...@hartford.edu

(He/Him/His)


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

Re: [Archivesspace_Users_Group] Exporting to PDF errors

[Blake Carver]

Depending on your version it'll be a slightly different issue, but something 
somewhere in there has an ampersand that is causing the PDF generator to barf.
There's one report here:
https://archivesspace.atlassian.net/browse/ANW-1340

I've seen these most often in notes and usually on something like J or B, 
some kind of a note with an ampersand withOUT any spaces around it. Usually 
changing those to J & & or B & T will fix it. You can also change it to  
and that might do the trick. Older versions of ArchivesSpace have more of those 
bugs than newer versions.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Esh, 
John C. 
Sent: Wednesday, September 22, 2021 3:22 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Exporting to PDF errors


For several finding aids, when I try to export to PDF, I’m getting this error…



Generating PDF for Athletics Department records

org.xml.sax.SAXParseException; lineNumber: 88; columnNumber: 42; The entity 
name must immediately follow the '&' in the entity reference.

net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:379)

java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)

org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453)

org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314)

RUBY.parse(/as_server/current/gems/gems/saxon-xslt-0.8.2.2-java/lib/saxon/xml.rb:28)

RUBY.XML(/as_server/current/gems/gems/saxon-xslt-0.8.2.2-java/lib/saxon/processor.rb:58)

RUBY.XML(/as_server/current/gems/gems/saxon-xslt-0.8.2.2-java/lib/saxon/xml.rb:10)

RUBY.to_fo(/as_server/current/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:38)

RUBY.to_pdf(/as_server/current/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44)

RUBY.block in 
run(/as_server/current/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51)

If anyone has any thoughts as to what’s going on, I’d love to hear them. This 
isn’t the entirety of the error code, but it seems to repeat similar lines 
after this.



Thanks!



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

Re: [Archivesspace_Users_Group] Connection/login dropping

[Blake Carver]

"No route matches" is just a 404 error, so that's probably not it.

Try that loglevel on debug for a while.

Also, are there outofmemory java errors in the logs or is it just dead?


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Tuesday, September 7, 2021 11:27 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Connection/login dropping

Apologies, hit send when cutting and pasting.

​Prior to the SOLR logging, there is this FATAL, which I think is associated 
with either deleted records or the top/subcontainers issue. We see loads of 
these in the logs though, and it doesn't seem to stop it functioning. I will 
put debug on though and try to get some more info.

F, [2021-08-18T06:20:39.318509 #90658] FATAL -- : 
[71fbc902-de38-4056-8574-a9b803620eb3]
F, [2021-08-18T06:20:39.318716 #90658] FATAL -- : 
[71fbc902-de38-4056-8574-a9b803620eb3] ActionController::RoutingError (No route 
matches [GET] "/repositories/2/archival_objects/21727/request"):
F, [2021-08-18T06:20:39.318771 #90658] FATAL -- : 
[71fbc902-de38-4056-8574-a9b803620eb3]
F, [2021-08-18T06:20:39.318825 #90658] FATAL -- : 
[71fbc902-de38-4056-8574-a9b803620eb3] actionpack (5.2.4.4) 
lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] actionpack (5.2.4.4) 
lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] railties (5.2.4.4) 
lib/rails/rack/logger.rb:38:in `call_app'
[71fbc902-de38-4056-8574-a9b803620eb3] railties (5.2.4.4) 
lib/rails/rack/logger.rb:26:in `block in call'
[71fbc902-de38-4056-8574-a9b803620eb3] activesupport (5.2.4.4) 
lib/active_support/tagged_logging.rb:71:in `block in tagged'
[71fbc902-de38-4056-8574-a9b803620eb3] activesupport (5.2.4.4) 
lib/active_support/tagged_logging.rb:28:in `tagged'
[71fbc902-de38-4056-8574-a9b803620eb3] activesupport (5.2.4.4) 
lib/active_support/tagged_logging.rb:71:in `tagged'
[71fbc902-de38-4056-8574-a9b803620eb3] railties (5.2.4.4) 
lib/rails/rack/logger.rb:26:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] actionpack (5.2.4.4) 
lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] actionpack (5.2.4.4) 
lib/action_dispatch/middleware/request_id.rb:27:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] rack (2.2.3) 
lib/rack/method_override.rb:24:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] rack (2.2.3) lib/rack/runtime.rb:22:in 
`call'
[71fbc902-de38-4056-8574-a9b803620eb3] activesupport (5.2.4.4) 
lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] actionpack (5.2.4.4) 
lib/action_dispatch/middleware/executor.rb:14:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] actionpack (5.2.4.4) 
lib/action_dispatch/middleware/static.rb:127:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] rack (2.2.3) lib/rack/sendfile.rb:110:in 
`call'
[71fbc902-de38-4056-8574-a9b803620eb3] railties (5.2.4.4) 
lib/rails/engine.rb:524:in `call'
[71fbc902-de38-4056-8574-a9b803620eb3] 
uri:classloader:/rack/handler/servlet.rb:22:in `call'




==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: 07 September 2021 16:23
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Connection/login dropping

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email 
is genuine and the content is safe.
Any ERROR or FATAL?
If not, try bumping up the log_level to debug and see if that will catch 
something.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Tuesday, September 7, 2021 11:21 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Connection/login dropping

Thanks Blake.

A mass of solr logging (I am set to ERROR throughout, but still getting plenty 
of indexer INFO). Prior to that:




==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: 07 September 2021 15:37
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Connection/login dropping

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email 
is genuine and the content is safe.
What's happening in the logs just before that first "Unhanded exception" error?

From: archivesspace_users_group-boun...@lyral

Re: [Archivesspace_Users_Group] Connection/login dropping

[Blake Carver]

Any ERROR or FATAL?
If not, try bumping up the log_level to debug and see if that will catch 
something.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Tuesday, September 7, 2021 11:21 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Connection/login dropping

Thanks Blake.

A mass of solr logging (I am set to ERROR throughout, but still getting plenty 
of indexer INFO). Prior to that:




==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: 07 September 2021 15:37
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Connection/login dropping

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email 
is genuine and the content is safe.
What's happening in the logs just before that first "Unhanded exception" error?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, September 6, 2021 9:29 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Connection/login dropping

Hi all

Our uptime has been a bit flaky the last few weeks- what we're finding is that, 
after a certain amount of service, users are unable to login, and if that's not 
noticed or acted on, the site generally stops responding some time later. A 
restart of the application resolves it.

We're running 2.8.1 against MariaDB 5.5-65, and Java 8. I have tried different 
versions of the mysqlconnector, but this does not seem to make a difference 
(first noticed on 5.1.39). The MySQL has been tuned to an extent. The VM has 
16GB of memory, approximately 10GB of which is apportioned to AS. The MySQL 
process was restarted last week, and clearing that has still allowed the issue.

It's pretty hard to spot any particular action which causes this. The logging 
we see once it's happened looks like this:

E, [2021-08-18T06:21:01.548843 #90658] ERROR -- : Thread-28310: Unhandled 
exception!
E, [2021-08-18T06:21:01.552325 #90658] ERROR -- :

apps.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.model.base.RUBY$method$parent_id$0(/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb:783)
apps.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.model.base.RUBY$method$parent_id$0$__VARARGS__(/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb)
org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:82)
org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:70)

and will continue to spout "minus_​5_dot_9_dot_0" type errors until we reboot.

I have taken some statistics around the numbers of threads running pre and post 
bounce. I don't see anything obvious there, and I have left the config.rb value

AppConfig[:db_max_connections] = proc { 20 + (AppConfig[:indexer_thread_count] 
* 2) }


as it is.

I'm also aware that we have an issue some others have of a proliferation of 
FATAL errors since merging top/subcontainers (items cannot be found), but I do 
not know if it is related to this.

However, if anyone recognises this behaviour, and can advise, I'd be grateful 
to hear about it.

Cheers
Scott




==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland, with 
registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh 
Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Connection/login dropping

[Blake Carver]

What's happening in the logs just before that first "Unhanded exception" error?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, September 6, 2021 9:29 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Connection/login dropping

Hi all

Our uptime has been a bit flaky the last few weeks- what we're finding is that, 
after a certain amount of service, users are unable to login, and if that's not 
noticed or acted on, the site generally stops responding some time later. A 
restart of the application resolves it.

We're running 2.8.1 against MariaDB 5.5-65, and Java 8. I have tried different 
versions of the mysqlconnector, but this does not seem to make a difference 
(first noticed on 5.1.39). The MySQL has been tuned to an extent. The VM has 
16GB of memory, approximately 10GB of which is apportioned to AS. The MySQL 
process was restarted last week, and clearing that has still allowed the issue.

It's pretty hard to spot any particular action which causes this. The logging 
we see once it's happened looks like this:

E, [2021-08-18T06:21:01.548843 #90658] ERROR -- : Thread-28310: Unhandled 
exception!
E, [2021-08-18T06:21:01.552325 #90658] ERROR -- :

apps.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.model.base.RUBY$method$parent_id$0(/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb:783)
apps.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.model.base.RUBY$method$parent_id$0$__VARARGS__(/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb)
org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:82)
org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:70)

and will continue to spout "minus_​5_dot_9_dot_0" type errors until we reboot.

I have taken some statistics around the numbers of threads running pre and post 
bounce. I don't see anything obvious there, and I have left the config.rb value

AppConfig[:db_max_connections] = proc { 20 + (AppConfig[:indexer_thread_count] 
* 2) }


as it is.

I'm also aware that we have an issue some others have of a proliferation of 
FATAL errors since merging top/subcontainers (items cannot be found), but I do 
not know if it is related to this.

However, if anyone recognises this behaviour, and can advise, I'd be grateful 
to hear about it.

Cheers
Scott




==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland, with 
registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh 
Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Archivesspace Crashing

[Blake Carver]

You'll probably find some ERROR or FATAL lines that are NOT RoutingError. 
Usually RoutingError is just a 404.
If it's crashing you'll likely see OutOfMemoryError from java as well.
If you're not seeing those, reset the loglevel to debug and that should help 
log some better errors.
Sometimes it doesn't log the good errors until you have it on debug.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ludwig 
Possie 
Sent: Wednesday, September 1, 2021 5:37 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Archivesspace Crashing

We've recently upgraded to AS 3.01 about a month ago.  Recently AS has been 
crashing after several hours, I've looked through the logs and I'm noticing 
some fatal errors from the start.  I'm not familiar with the error message and 
was hoping perhaps someone more experienced has seen this before.

The first Fatal error message that pops up seems to indicate there is a null 
value somewhere?  The log then repeats a RoutingError error after that.  Any 
suggestions would be appreciated.  Thx.




   │
│ Welcome to ArchivesSpace! 


   │
│ You can now point your browser to http://localhost:8080   


   │
│   


   │
│   WARNING: An illegal reflective access operation has occurred


   │
│   WARNING: Illegal reflective access by org.jruby.ext.openssl.SecurityHelper 
(file:/archivesspace/data/tmp/jruby-62/jruby2087180818245229256jopenssl.jar) to 
field java.security.MessageDigest.provider  
│
│   WARNING: Please consider reporting this to the maintainers of 
org.jruby.ext.openssl.SecurityHelper

 │
│   WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

  │
│   WARNING: All illegal access operations will be denied in a future release   


   │
│   F, [2021-09-01T21:14:18.036770 #62] FATAL -- : 
[8c076d10-8e4e-4e54-8014-518d690684ec]  

│
│   F, [2021-09-01T21:14:18.037466 #62] FATAL -- : 
[8c076d10-8e4e-4e54-8014-518d690684ec] ActionView::Template::Error (undefined 
method `keys' for nil:NilClass):
  │
│   F, [2021-09-01T21:14:18.038123 #62] FATAL -- : 
[8c076d10-8e4e-4e54-8014-518d690684ec] 1:<% @result.notes.keys.each do 
|type|  
 │
│   [8c076d10-8e4e-4e54-8014-518d690684ec] 2:   note_struct  = 
@result.note(type) %>   

│
│   [8c076d10-8e4e-4e54-8014-518d690684ec] 3:   <%= render partial: 
'shared/single_note', locals: {:type => type, :note_struct => note_struct} %>   

   │
│   

Re: [Archivesspace_Users_Group] AS 3.0.1 Issue

[Blake Carver]

> When I examine the HTML created by AS, there are issues when an input value 
> contains a single apostrophe.

What value has the single apostrophe?

> The print button does not function either (see screenshot).

What does that error look like in the ArchivesSpace logs?



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tracy 
Farmer 
Sent: Tuesday, August 24, 2021 1:43 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Cc: Wendy Crist 
Subject: [Archivesspace_Users_Group] AS 3.0.1 Issue


We recently upgraded to AS 3.0.1. After the upgrade, our PUI displays a ‘/> 
between the Citation and Request buttons (see image) on the Collection pages. 
When I examine the HTML created by AS, there are issues when an input value 
contains a single apostrophe. The print button does not function either (see 
screenshot).



You can find our AS instance at https://as1.library.astate.edu.



Thanks in advance for your assistance,

Tracy











[http://area51.astate.edu/e-footer/astatelogo-email.jpg]

F. Tracy Farmer, MS, MLIS, CISSP, CCSP

Systems Librarian

Dean B. Ellis Library

Room 221A

P.O. Box 2040 | State University, AR 72467

p: (870) 680-4312 | c: (870) 483-3179 | f: (870) 972-3199

Arkansas State educates leaders, enhances intellectual growth, and enriches 
lives.




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

Re: [Archivesspace_Users_Group] Can't login to backend after v3.0.2 upgrade

[Blake Carver]

Can you also check your proxy for errors?
Was there any ERROR or FATAL lines in the ArchivesSpace logs?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Schanz, 
Megan 
Sent: Tuesday, August 24, 2021 1:04 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Can't login to backend after v3.0.2 upgrade

Hi all,

I recently tried upgrading from v2.8.1 to v3.0.2. The upgrade itself went 
smoothly (database migrations run and full Solr reindex), but users are not 
able to login to the staff side.

After a successful login we see the green message: "Login Successful. 
Redirecting", which then immediately shows this red message: "Your session 
expired due to inactivity"; never letting me get past the login page. I have 
tried with my user as well as the admin user with the same results. There are 
no errors in the log, but show these debug messages:

D, [2021-08-23T09:56:58.116731 #56] DEBUG -- : Thread-4056: POST 
/users/admin/login [session: nil]
D, [2021-08-23T09:56:58.122502 #56] DEBUG -- : Thread-4056: Post-processed 
params: {"password"=>"[FILTERED]", "username"=>"admin", "expiring"=>true}
D, [2021-08-23T09:56:58.260237 #56] DEBUG -- : Thread-4056: Responded with 
[200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, 
must-revalidate, max-age=0", "Content-Length"=>"2981"}, 
["{\"session\":\"70e1e356292a453b6e292a55e822287e41d53caedccf6bf7633735990cdec309\",\"user\":{\"lock_version\":53,\"username\":\"admin\",\"name\":\"Administrator\",\"is_system_user\":true,\"create_time\":\"2018-09-17T08:12:28Z\",\"system_mtime\":\"2021-08-23T13:56:58Z\",\"user_mtime\":\"2021-08-23T13:56:58Z\",\"jsonmodel_type\":\"user\",\"groups\":[],\"is_admin\":true,\"uri\":\"/users...
 in 143ms


I tried increasing the session_expire_after_seconds and 
session_nonexpirable_force_expire_after_seconds to see if that allowed me to 
login, but there was no change in the behavior.

Did anyone else experience this and find a resolution?

Thanks,
Megan

_

Megan Schanz
Application Developer & Systems Administrator
Michigan State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Unable to edit / delete accessions or resources after upgrade to MySQL database

[Blake Carver]

It's hard to know for sure what's going on with this.
You were running 1.3 with MySQL and everything was fine?
They did the upgrade, you login and see everything is gone and it's running on 
Apache Derby... EEK!
You let them know, they connect it to MySQL again and now it's in this state.
So they probably hooked you up with your old 1.3 DB that has been upgraded to 
2.8.1.
Or maybe it's set to talk to the wrong DB, and it's empty. If it's empty, maybe 
they have a backup of the old DB?
My guess is that they brought over the /data/ directory. That directory has all 
the solr stuff in it, and if they did bring that over, things are likely in 
this weird state.
I'd start by asking them a couple of questions

  1.  Did they indeed hook you back to the old db that is now upgraded? Are 
they sure the config is updated to talk to the right DB? They should be able to 
search the DB directly to see what's in there.
  2.  Did they copy over all the stuff in /data/ ? If so, you don't want all 
that stuff. Tell them to empty that directory and restart it.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Merryman, Ann 
Sent: Wednesday, July 14, 2021 4:02 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Unable to edit / delete accessions or 
resources after upgrade to MySQL database


Good afternoon hive mind…long time lurker, first time writer.  :)  I’m going to 
try to make this question concise:



·I have just been upgraded to v2.8.1 (from v1.3.0…don’t judge!  Lol) on 
a locally-hosted instance of AS, managed by my university’s IT department.

·When my instance was upgraded, I got the following warning message:

Database Warning: You are currently using the embedded database (Apache Derby). 
The embedded database is for testing/demo purposes only. You should use MySQL 
for any data intended for production, including data in a test instance that 
you intend to move over to a production instance.



·The vendor let us know that there were not any upgrade paths from the 
demo database to MySQL, and the information would have to be re-entered (this 
is fine, as I had backed up everything and could re-enter)

·Once IT built the MySQL database, however, all the accession and 
resource records  actually showed up.  ???



The problem is, while I can *see* the records on the back end, I can’t edit or 
delete them.  However, they are visible and searchable on the PUI.  I’ve 
attached a few images for reference.



I’m trying to determine what the best course of action might be before I go 
back to my IT department, as I’m going to have to explain what the issue is to 
them as best I can (they’re not really familiar with AS or archival processes, 
unfortunately).  I’m not clear on why the data pulled over if there wasn’t a 
path, and I’m not tech savvy enough to guess at what my IT department did.  I 
could also email AS tech support, but I thought I’d start here to see if anyone 
has seen this or has something to try first.



Any thoughts or suggestions from the group would be greatly appreciated, or 
even just sympathetic noises.  :)



Thanks so much,



Ann



“For the things we have to learn before we can do them, we learn by doing 
them.” ~ Aristotle



Ann E. Merryman, MLIS

Associate Librarian

Coordinator of Archives and Special Collections

[cid:image002.png@01D778C9.9E3A4EE0]

USC Upstate, Library 263

800 University Way

Spartanburg, SC 29303

Office:  864-503-5275

merry...@uscupstate.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] Trouble Loading Collection Organization Tab

[Blake Carver]

Is there anything in the logs that has ERROR or FATAL in it?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Bennett 
Poulin 
Sent: Tuesday, July 13, 2021 3:50 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Trouble Loading Collection Organization Tab


Hello Everyone,

We have come to a roadblock in debugging an issue we are having.

The problem:

We seem to be having trouble with some of our records not loading completely on 
the collection organization tab. The problem seems to only occur with certain 
resolutions and edge cases. The only way we can consistently reproduce the 
problem is to have the dev tools console open, but it does happen sometimes on 
regular page loads.

Steps to Reproduce:

  1.  Navigate to a known affected page: 
https://nmarchives.unm.edu/repositories/22/resources/2204/collection_organization
  2.  Open the console F12 (Firefox, Chrome, Edge)
  3.  Scroll down the Collection Organization until it stops loading further 
and errors are produced

Relevant Information:

  *   Edge and Chrome produce the following console errors
 *   
application-d931c7796d2a9940ff4967478207ddb3d3d86faa90b8163d2058ce9413ad0d27.js:2
 [Intervention] Unable to preventDefault inside passive event listener due to 
target being treated as passive. See 
https://www.chromestatus.com/features/6662647093133312
*   preventDefault @ 
application-d931c7796d2a9940ff4967478207ddb3d3d86faa90b8163d2058ce9413ad0d27.js:2
*   (anonymous) @ 
infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1
*   dispatch @ 
application-d931c7796d2a9940ff4967478207ddb3d3d86faa90b8163d2058ce9413ad0d27.js:2
*   g.handle @ 
application-d931c7796d2a9940ff4967478207ddb3d3d86faa90b8163d2058ce9413ad0d27.js:2
 *   GET 
https://nmarchives.unm.edu/repositories/22/resources/2204/tree/node?node=%2Frepositories%2F22%2Farchival_objects%2F259267
 404 (Not Found)
  *   ArchivesSpace Version: 2.8.1

Logs:

Jul 13, 2021 12:50:00 PM org.apache.solr.core.SolrCore execute

INFO: [collection1] webapp= path=/select 
params={mm=100%25=(uri:("\/repositories\/22\/resources\/2204\/tree\/node_\/repositories\/22\/archival_objects\/259261"))=\=true=0="=-exclude_by_default:true=publish:true=types:pui=1=json=true}
 hits=0 status=0 QTime=2

Jul 13, 2021 12:50:00 PM org.apache.solr.update.processor.LogUpdateProcessor 
finish

INFO: [collection1] webapp= path=/update params={} 
{deleteByQuery=parent_id:("/repositories/22/archival_objects/185733")} 0 1

Jul 13, 2021 12:50:00 PM org.apache.solr.update.processor.LogUpdateProcessor 
finish

INFO: [collection1] webapp= path=/update params={} 
{add=[/repositories/22/archival_objects/185733]} 0 1

Jul 13, 2021 12:50:00 PM org.apache.solr.update.DirectUpdateHandler2 commit

INFO: start 
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=true,prepareCommit=false}

Jul 13, 2021 12:50:00 PM org.apache.solr.search.SolrIndexSearcher 

INFO: Opening Searcher@1151478f[collection1] main

Jul 13, 2021 12:50:00 PM org.apache.solr.update.DirectUpdateHandler2 commit

INFO: end_commit_flush

Jul 13, 2021 12:50:00 PM org.apache.solr.core.SolrCore registerSearcher

INFO: [collection1] Registered new searcher Searcher@1151478f[collection1] 
main{StandardDirectoryReader(segments_24py:649922:nrt 
_nr(4.10.4):C219913/46272:delGen=474 _11f(4.10.4):C425538/52164:delGen=678 
_3ph(4.10.4):C359151/35922:delGen=550 _2o2(4.10.4):C85704/12221:delGen=96 
_jqw(4.10.4):C82274/20242:delGen=170 _3u8(4.10.4):C96489/15326:delGen=127 
_12w0(4.10.4):C121374/13239:delGen=109 _3898(4.10.4):C59987/20078:delGen=481 
_1n6j(4.10.4):C47632/3396:delGen=26 _3sgm(4.10.4):C23740/10497:delGen=98 
_4m19(4.10.4):C44854/4334:delGen=106 _4m2g(4.10.4):C2285/8:delGen=4 
_4mgz(4.10.4):C3706/570:delGen=30 _4mfy(4.10.4):C501/2:delGen=2 
_4mlp(4.10.4):C2214/438:delGen=3 _4mkp(4.10.4):C260 
_4mn1(4.10.4):C25/3:delGen=1 _4mnw(4.10.4):C16/2:delGen=1 
_4mnv(4.10.4):C3/1:delGen=1 _4mnz(4.10.4):C2/1:delGen=1 _4mo3(4.10.4):C21 
_4mo4(4.10.4):C1 _4mo5(4.10.4):C31 _4mo6(4.10.4):C21/1 _4mo7(4.10.4):C488 
_4mo8(4.10.4):C1)}

Jul 13, 2021 12:50:00 PM org.apache.solr.update.processor.LogUpdateProcessor 
finish

INFO: [collection1] webapp= path=/update params={} {commit=} 0 95

Jul 13, 2021 12:50:01 PM org.apache.solr.core.SolrCore execute

INFO: [collection1] webapp= path=/select 
params={mm=100%25=(uri:("\/repositories\/22\/resources\/2204\/tree\/node_\/repositories\/22\/archival_objects\/259262"))=\=true=0="=-exclude_by_default:true=publish:true=types:pui=1=json=true}
 hits=1 status=0 QTime=29

Specific Log-Entry:

Jul 13, 2021 1:08:50 PM org.apache.solr.core.SolrCore execute

INFO: [collection1] webapp= path=/select 

Re: [Archivesspace_Users_Group] Captions for digital objects in the PUI

[Blake Carver]

I put in a JIRA here

https://archivesspace.atlassian.net/browse/ANW-1338

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Friday, July 9, 2021 11:22 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Captions for digital objects in the PUI

Adding "white-space: pre-wrap;" to the ".record-type-badge" in the CSS seems to 
help, though I'm not sure it's the best way to go.
I'm not sure what that would do to all the other ones, so you'd want to test 
things, and there might be a better property to use that'll wrap things better.
Somone else with some awesome CSS skills might have a better idea, but I think 
that's the general area that can be changed up.


.record-type-badge {
font-family: "Gotham SSm A","Gotham SSm B",Arial,Helvetica,sans-serif;
white-space: pre-wrap;
}

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Pruitt, 
Adrienne 
Sent: Friday, July 9, 2021 10:50 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Captions for digital objects in the PUI

Hi, Blake,

https://archives.tufts.edu/repositories/2/archival_objects/268631 is one, and 
I've included a screenshot of what happens if your window is too small to 
accommodate the lengthy title. Thanks for taking a look!


Adrienne Pruitt | Collections Management Archivist

Digital Collections and Archives

Tufts University

adrienne.pru...@tufts.edu<https://exchange.tufts.edu/owa/redir.aspx?C=t5B1d8GNpPJJzaAAvUfcGAPuBinqgxXyoK8_O0ggQHCOYyG6Tc_XCA..=mailto%3aadrienne.pruitt%40tufts.edu>
 |617-627-0957


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Friday, July 9, 2021 8:24 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Captions for digital objects in the PUI

Can you point to an example?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Pruitt, 
Adrienne 
Sent: Tuesday, July 6, 2021 2:05 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Captions for digital objects in the PUI

Hello, all,

We've recently added thumbnails to our digital objects in the PUI (thanks to an 
ASpace Training Office Hour!) and are having an issue with the display of 
captions. This specifically affects pdfs and video. When a caption is 
particularly lengthy, the text isn't responsive in the same way that it is for 
other types of items, like images. Has anyone else noticed this or found a 
workaround?

Thanks very much for any advice,


Adrienne Pruitt | Collections Management Archivist

Digital Collections and Archives

Tufts University

adrienne.pru...@tufts.edu<https://exchange.tufts.edu/owa/redir.aspx?C=t5B1d8GNpPJJzaAAvUfcGAPuBinqgxXyoK8_O0ggQHCOYyG6Tc_XCA..=mailto%3aadrienne.pruitt%40tufts.edu>
 |617-627-0957
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Captions for digital objects in the PUI

[Blake Carver]

Can you point to an example?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Pruitt, 
Adrienne 
Sent: Tuesday, July 6, 2021 2:05 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Captions for digital objects in the PUI

Hello, all,

We've recently added thumbnails to our digital objects in the PUI (thanks to an 
ASpace Training Office Hour!) and are having an issue with the display of 
captions. This specifically affects pdfs and video. When a caption is 
particularly lengthy, the text isn't responsive in the same way that it is for 
other types of items, like images. Has anyone else noticed this or found a 
workaround?

Thanks very much for any advice,


Adrienne Pruitt | Collections Management Archivist

Digital Collections and Archives

Tufts University

adrienne.pru...@tufts.edu
 |617-627-0957
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] LCNAF in 2.8.1

[Blake Carver]

There should be an error in the logs, that should help explain what's happening.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Nic 
Stanton-Roark 
Sent: Tuesday, June 29, 2021 11:54 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] LCNAF in 2.8.1

Hi all,

I'm testing a fresh install of 2.8.1 and getting an error message on the LCNAF 
and LCSH plugin. This should be working in 2.8.1, right?

[image.png]

[https://anderson.edu/uploads/au-email-logo.gif]
Nicholas Stanton-Roark  |  Archivist  | Robert A. Nicholson University Library
Anderson University  |  1100 E. Fifth St, Anderson, IN 46012
(765) 641-4285  |  
ndro...@anderson.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] Generate PDF Background job error

[Blake Carver]

"Open quote is expected for attribute "href" associated with an  element type  
"a"."

There's some bad HTML in there. I usually export it to EAD and then just search 
for "href" and look for the bad tags, hopefully it's not a record with 1000 
hrefs in there

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Zachary 
L Pelli 
Sent: Thursday, June 17, 2021 4:45 PM
To: ArchivesSpace List (archivesspace_users_group@lyralists.lyrasis.org) 

Subject: [Archivesspace_Users_Group] Generate PDF Background job error

Hello all,

We encountered the error below when running the "Generate PDF" job on a 
particular resource. Short of looking through every single record in the 
resource for the missing ", is there a way to quickly track down the error?

Generating PDF for x
--
Warning: this resource has not been published
--
org.xml.sax.SAXParseException; lineNumber: 189; columnNumber: 110330; Open 
quote is expected for attribute "href" associated with an  element type  "a".
net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:360)
java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456)
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317)
RUBY.build(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/document_builder.rb:225)
RUBY.to_fo(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:42)
RUBY.to_pdf(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58)
RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:51)
var.local.archivesspace.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24)
RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:14)
var.local.archivesspace.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(var/local/archivesspace/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126)
var.local.archivesspace.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126)
RUBY.start_background_thread(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169)
org.jruby.RubyProc.call(org/jruby/RubyProc.java:318)
java.lang.Thread.run(java/lang/Thread.java:748)


Regards,

Zach Pelli
Seton Hall University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] logrotate and "binary" logs

[Blake Carver]

archivesspace.out should for sure be "ASCII text, with very long lines"
If it's something else, there's something wrong somewhere.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Dyson-Smith, Bridger 
Sent: Monday, June 14, 2021 3:00 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] logrotate and "binary" logs

Hi all -

I recently setup logrotate according to the helpful blurb in the tech-
docs[1], which has been great for our disk usage but seems to have
introduced a change in the log file's `file` type.

Before logrotate, we had


$ file archivesspace.out
aspace-log.out: ASCII text, with very long lines

and now with logrotate in play, we have

$ file as-log.out
as-log.out: data

which causes all sorts of trouble if I want to do anything other than
tail a log :).

I guess I was hoping someone may a suggestion or two about how to
approach this, either from the logrotate side or perhaps using another
utility to either modify the `file` metadata or parse the binary format
to something greppable?

Thanks for any advice you can share. My searching hasn't panned out.
Best,
Bridger

[1]
https://archivesspace.github.io/tech-docs/administration/logrotate.html

[2] my config:
archivesspace/logs/archivesspace.out {
daily
rotate 7
compress
notifempty
missingok
copytruncate
}

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

Re: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

[Blake Carver]

> In order to be sure, is there a way to migrate data manually to ensure that 
> schema matches and all the data gets migrated?

I'd say, probably not.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ludwig 
Possie 
Sent: Friday, May 14, 2021 2:10 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

Thank you for your recommendations.  I've imported the database from our 
production to  dev and changed the schema version as Megan had suggested, 
fortunately in this case it resolved the issue and allowed archivesspace to run 
as expected.  Our production environment is running on docker, but I doubt that 
would impact the schema version.  I completely understand what you're saying 
Blake and normally I would not want to mess with the schema version, however in 
this instance since the schema version seems to be completely off and not match 
any other version, it may be needed in order to get the DB in sync with the 
current version it should be on.  I'm crossing my fingers that moving forward 
it won't mess with things.  In order to be sure, is there a way to migrate data 
manually to ensure that schema matches and all the data gets migrated?

On Fri, May 14, 2021 at 10:50 AM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
I wouldn't recommend changing the schema_info, this can put you in a really bad 
place.

Your error:
""The schema info version should be 120 for ArchivesSpace version v2.6.0.  
However, your schema info version is set at 122"

Every release of ArchivesSpace has a  schema number . All recent releases have 
the  schema number  listed on the release notes. So the latest version 3.0 is  
147, and the previous release 2.8.1 is 138 and so on down the line. Those 
numbers are important and are set by the code. That's what the ArchivesSpace 
code looks at to know that the MySQL Database lines up with what it expects. 
Each version expects certain tables/rows/columns to be there and in a certain 
format. As ArchivesSpace starts each time it checks that shema_info number, and 
if it's wrong, it fails. So ArchivesSpace 3.0 starts up and says "Hey MySQL 
what ya got there?" and MySQL says "147" and ArchivesSpace says "Groovy, that's 
what I need to run" and then they high five and start getting down to business. 
If ArchivesSpace starts up and says "Hey MySQL, what ya got there?" and it says 
"122" and ArchivesSpace was expecting 120, ArchivesSpace says "That ain't 
right, I can't work with that" and starts telling you all about it in 
archivesspace.out.

So your version of ArchivesSpace is expecting schema_info to be 120 but it's 
actually 122, which is larger number and therefore a newer release.

Looking back at the old releases, schema_info on 2.7 is 126 and the release 
before that is 120 is 2.6.0, which means 122 is... I don't know what.

I'm not sure what to recommend here. From what I can see there is not any 
release that should have a schema version of 122, so I don't know how that got 
set like that.


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Schanz, Megan mailto:schan...@msu.edu>>
Sent: Thursday, May 13, 2021 9:35 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

That should only happen when the setup-database script was run for a later 
version of ArchivesSpace. But if that isn't the case, you could try manually 
reverting the schema number in the database to see if that resolves your issue.

update schema_info set version = 120;

I've had to do that at one point in the past, but I can't recall what 
circumstances led to me having to do that.

- Megan

_

Megan Schanz
Application Developer & Systems Administrator
Michigan State University Libraries

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Ludwig Possie 
mailto:ludwigpos...@weber.edu>>
Sent: Wednesday, May 12, 2021 7:56 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

I'm in the process of moving our current version of Archivesspace 2.6.0 to a 
new server running Ubuntu 20.04.  I've installed Java 1.8, MySQL 8.0.25 and 
mysql connector 8.0.25 on the new server.

I successfully got Archivesspace 2.6.0 running o

Re: [Archivesspace_Users_Group] 'Sign In' swap with SSO login

[Blake Carver]

You can probably just override that here:

https://github.com/archivesspace/archivesspace/blob/82c4603fe22bf0fd06043974478d4caf26e1c646/frontend/app/views/welcome/index.html.erb



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ben 
Fisher 
Sent: Friday, May 14, 2021 11:15 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] 'Sign In' swap with SSO login

Hello,

I'm in the process of implementing the Oauth plugin to comply with a recent 
security audit. The plugin itself is now configured and working correctly, but 
I would like to close the door to local sign-in, at least during normal 
circumstances.

Ideally, I would like to swap the 'Sign In' button target from local sign-in to 
the SSO link. Does anyone know how we could accomplish this? An acceptable 
alternative could be removing the Sign In button entirely, leaving only the SSO 
link. All suggestions are welcome.

Thank you,

--

Ben Fisher | IT Coordinator

University of Arkansas at Little Rock | Information Technology Services
501.916.3011 | 
btfish...@ualr.edu | 
ualr.edu/itservices

 
[https://docs.google.com/uc?export=download=0Bz9cuMeqg1TDZ3FCTmp0SGtoWHM=0Bz9cuMeqg1TDTC82aDhXejYvWStpc2VrZWdwaWNsTmlheUQwPQ]

Reminder:  IT Services will never ask for your password over the phone or in an 
email. Always be suspicious of requests for personal information that comes via 
email, even from known contacts.  For more information or to report suspicious 
email, visit http://ualr.edu/itservices/security/

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

Re: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

[Blake Carver]

I wouldn't recommend changing the schema_info, this can put you in a really bad 
place.

Your error:
""The schema info version should be 120 for ArchivesSpace version v2.6.0.  
However, your schema info version is set at 122"

Every release of ArchivesSpace has a  schema number . All recent releases have 
the  schema number  listed on the release notes. So the latest version 3.0 is  
147, and the previous release 2.8.1 is 138 and so on down the line. Those 
numbers are important and are set by the code. That's what the ArchivesSpace 
code looks at to know that the MySQL Database lines up with what it expects. 
Each version expects certain tables/rows/columns to be there and in a certain 
format. As ArchivesSpace starts each time it checks that shema_info number, and 
if it's wrong, it fails. So ArchivesSpace 3.0 starts up and says "Hey MySQL 
what ya got there?" and MySQL says "147" and ArchivesSpace says "Groovy, that's 
what I need to run" and then they high five and start getting down to business. 
If ArchivesSpace starts up and says "Hey MySQL, what ya got there?" and it says 
"122" and ArchivesSpace was expecting 120, ArchivesSpace says "That ain't 
right, I can't work with that" and starts telling you all about it in 
archivesspace.out.

So your version of ArchivesSpace is expecting schema_info to be 120 but it's 
actually 122, which is larger number and therefore a newer release.

Looking back at the old releases, schema_info on 2.7 is 126 and the release 
before that is 120 is 2.6.0, which means 122 is... I don't know what.

I'm not sure what to recommend here. From what I can see there is not any 
release that should have a schema version of 122, so I don't know how that got 
set like that.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Schanz, 
Megan 
Sent: Thursday, May 13, 2021 9:35 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

That should only happen when the setup-database script was run for a later 
version of ArchivesSpace. But if that isn't the case, you could try manually 
reverting the schema number in the database to see if that resolves your issue.

update schema_info set version = 120;

I've had to do that at one point in the past, but I can't recall what 
circumstances led to me having to do that.

- Megan

_

Megan Schanz
Application Developer & Systems Administrator
Michigan State University Libraries

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ludwig 
Possie 
Sent: Wednesday, May 12, 2021 7:56 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Database Migration Error on AS 2.6.0

I'm in the process of moving our current version of Archivesspace 2.6.0 to a 
new server running Ubuntu 20.04.  I've installed Java 1.8, MySQL 8.0.25 and 
mysql connector 8.0.25 on the new server.

I successfully got Archivesspace 2.6.0 running on MySQL (New blank database) on 
the new server.  When I import our current production database and run the 
setup-database.sh script I get no error and an 'All Done' message at the end.  
However when I attempt to run archivesspace.sh I get a Database Migration 
Error, with the following recommendation, "The schema info version should be 
120 for ArchivesSpace version v2.6.0.  However, your schema info version is set 
at 122
Please ensure your migrations have been run and completed by using the 
setup-database script."
I've ran the script various times but I keep getting the same results.  Has 
anyone experienced an issue like this?  Please advise.  Thank you.

--
Ludwig Possié
Systems Admin
Stewart Library
Weber State University
801-626-8093
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

[Blake Carver]

What's the JAVA version on there?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Cory 
Nimer 
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella ; Archivesspace Users 
Group (archivesspace_users_group@lyralists.lyrasis.org) 

Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2


Christine,



Here are the basic specs for our testing server according to our IT staff:



RHEL 8.3

4 procs

5GB RAM



For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.



If you need other information about the server, please let me know.



Best,



Cory



From: Christine Di Bella 
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer ; Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org) 

Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Hello Cory,



We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?



There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.



Thanks for your help,

Christine





From: Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>;
 Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2



Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in ' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `' from 

Re: [Archivesspace_Users_Group] Error Fetching Tree

[Blake Carver]

Sometimes just restarting ArchivesSpace can make that go away. If that doesn't 
do the trick, have a look at the logs, look for ERROR or FATAL.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Catie 
Heitz 
Sent: Wednesday, April 7, 2021 4:57 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Error Fetching Tree

Hi all,

I've recently run into a strange error and I'm not sure exactly what prompted 
it. I was editing existing Archival Objects to change their top containers - 
something I've been doing a lot lately with no issues. Suddenly the records 
stopped loading and I received the following error message:
"Oops! We're having trouble fetching this tree. Please try refreshing the page."
Refreshing the page does nothing and I get the same error whenever I try to 
open the tree. Fortunately, only one small subseries was affected.
Obviously I want to understand what happened so that I can fix it, but also so 
I can avoid this issue in the future. Again, all I thought I was doing was 
changing the top container, which is something I've done hundreds of times with 
no problem. If any one has any insight, it would be most appreciated.

Best,
Catie
--
Catie Heitz
Archivist
American Academy in Rome
7 East 60th St.
New York, NY 10022
212-751-7200 x347
212-751-7220 (fax)
archi...@aarome.org
www.aarome.org


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

Re: [Archivesspace_Users_Group] Issues with MySQL v8

[Blake Carver]

You can send them to me or attach them to that JIRA.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Wendy 
Scheir 
Sent: Wednesday, March 31, 2021 2:49 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Issues with MySQL v8

Hi Blake,

Thanks so much for following up. So far, we've gotten report errors for the 
following 3 accessions reports:

  *   Accession Report
  *   Accession Receipt Report
  *   Accessions and Linked Subjects, Names and Classifications

I'm not sure if we've tested all of them, but definitely these 3 are erroring 
out. If you'd like to look at the error logs, I'd be glad to send them to you.

All best,
Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu<mailto:sche...@newschool.edu>

T 212.229.5942 x2888

Explore the Archives<http://library.newschool.edu/archives> | Digital 
Collections from the Archives<http://digitalarchives.library.newschool.edu/> | 
New School Histories<http://newschoolhistories.org/> | 
@tnsarchives<https://twitter.com/tnsarchives>


On Wed, Mar 31, 2021 at 2:33 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
There are others running on 8, so far the only trouble seems to be reports. 
Here's a JIRA
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200
You're seeing it fail on two reports?




From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Wendy Scheir mailto:sche...@newschool.edu>>
Sent: Tuesday, March 30, 2021 4:15 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Issues with MySQL v8

Hi,

When we installed ArchivesSpace last summer, we used MySQL v8 for our database. 
The documentation has instructions that read, "if using for MySQL 8+..." 
leading us to believe that MySQL 8 was a supported version. However, we've been 
having issues running Accession and Shelflist reports that the Lyrasis team has 
told us is caused by running MySQL 8 instead of MySQL 5. In the interim, 
Lyrasis has updated the documentation to say that "ArchivesSpace is currently 
able to run on MySQL version 5.x."

Has anyone else installed ArchivesSpace with MySQL 8? We are concerned about 
downgrading to 5 versus waiting for a future version that works with 8, but in 
the meantime we are unable to run a number of desired reports.

Many thanks,
Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu<mailto:sche...@newschool.edu>

T 212.229.5942 x2888

Explore the Archives<http://library.newschool.edu/archives> | Digital 
Collections from the Archives<http://digitalarchives.library.newschool.edu/> | 
New School Histories<http://newschoolhistories.org/> | 
@tnsarchives<https://twitter.com/tnsarchives>

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

Re: [Archivesspace_Users_Group] Issues with MySQL v8

[Blake Carver]

There are others running on 8, so far the only trouble seems to be reports. 
Here's a JIRA
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200
You're seeing it fail on two reports?




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Wendy 
Scheir 
Sent: Tuesday, March 30, 2021 4:15 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Issues with MySQL v8

Hi,

When we installed ArchivesSpace last summer, we used MySQL v8 for our database. 
The documentation has instructions that read, "if using for MySQL 8+..." 
leading us to believe that MySQL 8 was a supported version. However, we've been 
having issues running Accession and Shelflist reports that the Lyrasis team has 
told us is caused by running MySQL 8 instead of MySQL 5. In the interim, 
Lyrasis has updated the documentation to say that "ArchivesSpace is currently 
able to run on MySQL version 5.x."

Has anyone else installed ArchivesSpace with MySQL 8? We are concerned about 
downgrading to 5 versus waiting for a future version that works with 8, but in 
the meantime we are unable to run a number of desired reports.

Many thanks,
Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu

T 212.229.5942 x2888

Explore the Archives | Digital 
Collections from the Archives | 
New School Histories | 
@tnsarchives
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Bug in PUI search filtering?

[Blake Carver]

> Blake, any insight?

Nope, it does look like a bug to me, but I'm not sure on that. I'll look into 
it, and get a JIRA in if that's the case.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Anna 
Robinson-Sweet 
Sent: Wednesday, March 24, 2021 4:03 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Bug in PUI search filtering?

That is indeed what seems to be happening. For us it's not only with the date 
filter, but also the free text filter.

Search for fashion designers (113 results): 
https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93%5B%5D=%5B%5D=fashion+designers=%5B%5D=_year%5B%5D=_year%5B%5D==Search

When I type critics into the filter search bar, 136 results: 
https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93%5B%5D=%5B%5D=fashion+designers=%5B%5D=_year%5B%5D=_year%5B%5D==search=_q%5B%5D=critics_from_year=_to_year==Search



On Wed, Mar 24, 2021 at 4:00 PM Michelle Paquette 
mailto:mpaque...@smith.edu>> wrote:
Ha, and actually now I've tested it in my own system and this seems to be the 
case that when adding the date filter it switches to OR. Doesn't seem to be 
happening with any other filters though. Blake, any insight?

On Wed, Mar 24, 2021 at 3:56 PM Michelle Paquette 
mailto:mpaque...@smith.edu>> wrote:
Hi Anna,

I'm wondering if something is happening to the default AND boolean - if you 
search fashion OR designers in the first place you're getting 5998 results, so 
it seems when you remove the date filter it switches from an AND to an OR 
search.

Michelle

On Wed, Mar 24, 2021 at 3:41 PM Anna Robinson-Sweet 
mailto:robin...@newschool.edu>> wrote:
Hello,

We just noticed what appears to be a bug in applying filters to search results 
in the PUI. When we run a search on a phrase that is more than one word, and 
then apply a filter to those results, we get more results in the "filtered" 
search than in the initial one. When we remove the filter, there are even more 
results than either the initial or filtered search.This only happens when the 
initial search phrase is more than one word and is not in quotes, suggesting 
that the filter turns the initial search from an "and" query to an "or" query, 
or something along these lines.

Here is an example of the problem:
First search for the phrase fashion designers (without quotes) returns 113 
results: 
https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93%5B%5D=%5B%5D=fashion+designers=%5B%5D=_year%5B%5D=_year%5B%5D==Search

When I add a date filer 1950-1960 I get 393 results: 
https://findingaids.archives.newschool.edu/search?utf8=%E2%9C%93%5B%5D=%5B%5D=fashion+designers=%5B%5D=_year%5B%5D=_year%5B%5D==search=_q%5B%5D=_from_year=1950_to_year=1960=Search

And when I remove the filter I get 5,998 results: 
https://findingaids.archives.newschool.edu/search?q[]=fashion+designers[]=[]=keyword_year[]=_year[]=_q[]==

Has anyone else encountered this or have any ideas what may be causing the 
problem?

Thanks,
Anna

--

ANNA ROBINSON-SWEET (she/her)

ASSOCIATE ARCHIVIST
THE NEW SCHOOL
ARCHIVES & SPECIAL COLLECTIONS

66 FIFTH AVENUE, NEW YORK, NY 10011
robin...@newschool.edu
T 212-229-2942 3375

archives.newschool.edu

[THE NEW SCHOOL]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Michelle Paquette
(she/her)
Metadata & Technical Services Archivist
Special Collections
Smith College
413-585-7029
mpaque...@smith.edu


Please note: In light of COVID-19, the Libraries are offering contactless 
pickup, and all other services will continue to be offered remotely. Visit 
bit.ly/SCLcovid-19 for full details.

Please send any questions you may have to 
libraryh...@smith.edu and they will be answered 
as soon as possible. Special Collections reference 
service is active, but limited. For 
information about Smith College’s response to Covid-19, please visit the 
college’s official 
website.


--
Michelle Paquette
(she/her)
Metadata & Technical Services Archivist
Special Collections
Smith College
413-585-7029
mpaque...@smith.edu


Please note: In light of COVID-19, the Libraries are offering contactless 
pickup, and all other services will continue to be offered remotely. Visit 
bit.ly/SCLcovid-19 for full details.

Please send any questions you may have to 
libraryh...@smith.edu and they will be answered 

Re: [Archivesspace_Users_Group] PUI indexing issues

[Blake Carver]

I did some experimenting this weekend, messing around with indexer speeds, and 
found I could get it to succeed with the right indexer settings. I think the 
answer is going to be "it depends" and you'll need to experiment with what 
works on your set up with your data. I started with the defaults, then dropped 
it to realy slow (1 thread 1 per), then just tried to dial it up and down. 
The last one I tried worked fine, it was fast enough to finish in a reasonable 
amount of time and didn't slow down or crash. Your settings may not look like 
this, but here's something to try.

AppConfig[:pui_indexer_records_per_thread] = 50
AppConfig[:pui_indexer_thread_count] = 1


So some extra detail for the mailing list archives... if your site keeps 
crashing before the indexers finish and you're not seeing any particular errors 
in the logs that make you think you have a problem with your data, try turning 
the knobs on your indexer speed and see if that helps.

It looks like maybe the indexer just eats up too much memory on BIG records and 
having too many (too many being 15ish) threads running causes it to crash. I 
know BIG is pretty subjective, if you have a bunch of resources (maybe a few 
thousand) AND those resources all have ALLOTA (maybe a few thousand) children 
with ALLOTA subjects/agents/notes/stuff, then you might hit this problem. Seems 
like it's not the total number of resources, it's probably because those 
resources are big/complex/deep.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Thursday, March 18, 2021 11:24 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] PUI indexing issues

Dave,

Thanks for the suggestion, but unless there is some direct limitation within 
Solr, that should not be an issue. My disk is at only about 50% of capacity and 
Solr should be able to expand as needed. In my case, I don't think there has 
been much addition to Solr because I'm reindexing records which have been 
indexed already. So the deleted records are growing, but not the overall number 
of records. My index is currently at about 6GB.

Any other thoughts out there?

Thanks,
Tom

On Thu, Mar 18, 2021 at 10:51 AM Mayo, Dave 
mailto:dave_m...@harvard.edu>> wrote:

This is a little bit of a shot in the dark, but have you looked at disk space 
on whatever host Solr is resident on? (the ASpace server if you’re not running 
an external one)?

A thing we’ve hit a couple times is that Solr, at least in some configurations, 
needs substantial headroom on disk to perform well – I think it’s related to 
how it builds and maintains the index?  So it might be worth looking to see if 
Solr is filling up the disk enough that it can’t efficiently handle itself.



--

Dave Mayo (he/him)

Senior Digital Library Software Engineer
Harvard University > HUIT > LTS



From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Tom Hanstra mailto:hans...@nd.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Wednesday, March 17, 2021 at 11:43 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] PUI indexing issues







- What really bothers me is the slowdown. That indicates to me that some 
resource is being lost along the way. Anyone have thoughts on what that might 
be?





Just to follow up on my earlier post, I did get even lower numbers from Blake 
to try based upon what he used for our hosted account. But I'm seeing the same 
pattern in terms of slowdowns regarding the number of records that get 
processed/hour. Is this typical?  Is it just hitting records that have more 
work to be done? Or do I still have a resource issue.



I note that the number of docs in Solr has not changed at all throughout the 
last couple of attempts, which again leads me to believe it has already handled 
these records (at least once) before and thus there is no more indexing to 
really be done with the records which it is running through the PUI indexer 
again. Which leads back to the "why does PUI indexing restart each time from 0" 
question. How does one add an enhancement request to have this reviewed and 
(perhaps) changed?



Thanks,

Tom



--

Tom Hanstra

Sr. Systems Administrator

hans...@nd.edu



[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]

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


--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu

Re: [Archivesspace_Users_Group] PUI indexing issues

[Blake Carver]

I can only answer some of those.

- Staff indexing is done and has its files written. So does the number of 
threads given to that make a difference? Is it still taking up resources?

Not so much if it's not doing anything.

- Does there happen to be any way to stop the staff indexing and just let PUI 
have full access to the server for indexing?

You can disable either indexer, but that requires a restart. There's a setting 
in the config. The PUI is just slower than the Staff.

- Should our repositories be broken up into smaller groupings?  I'm beginning 
to wonder if we have things set up incorrectly, since it sounds like we have a 
very large data set compared to others.

It's probably not the total number of resources in a repo, just that the 
resources are quite large.



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Tuesday, March 16, 2021 1:52 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] PUI indexing issues

Thanks for the suggestion, Blake. A couple additional questions:

- Staff indexing is done and has its files written. So does the number of 
threads given to that make a difference? Is it still taking up resources?

- Does there happen to be any way to stop the staff indexing and just let PUI 
have full access to the server for indexing?

- What really bothers me is the slowdown. That indicates to me that some 
resource is being lost along the way. Anyone have thoughts on what that might 
be?

- Should our repositories be broken up into smaller groupings?  I'm beginning 
to wonder if we have things set up incorrectly, since it sounds like we have a 
very large data set compared to others.


And a comment

It is really frustrating to have to start over on the indexing each time. It 
seems that there should be some way to document progress along the way so that 
the indexing can pick up where it left off. Is that something that might also 
be looked at?

Thanks all. Appreciate your help.

Tom


On Tue, Mar 16, 2021 at 1:15 PM Blake Carver 
mailto:blake.car...@lyrasis.org>> wrote:
> I've now left my PUI indexing threads and count at the default (which I 
> believe is 1 thread and 25 records/thread).

Try dropping both indexer_records_per_thread and indexer_thread_count for both 
PUI and Staff indexers. Maybe in half or so. Sometimes with larger records it 
just needs to be slowed down.

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto: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: Tuesday, March 16, 2021 12:51 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] PUI indexing issues

Hello again.

I'm still trying to understand some indexing issues. I've now left my PUI 
indexing threads and count at the default (which I believe is 1 thread and 25 
records/thread). And I have given 4GB to Java processes. I've tried other 
values as well, but with similar results.

No matter what values I use, I cannot seem to fully index PUI. Each time, it 
will start well but continuously slow down. I've kept a spreadsheet of the 
number of records/hr I'm indexing and have several attempts which start in the 
50-60K/hr range and then continuously slow down to the 1800-1500/hr speed until 
finally dying with a Java Heap error. I think I'm headed to that again this 
round.

Why might this be happening?  Could my data have been corrupted during the 
transfer from Lyrasis? (I'm working with a database export of our production 
data). Is the database too far away (our database is in an AWS RDS being 
accessed from our AWS EC2).

I do have one log which gave this error:

E, [2021-03-12T18:14:53.886243 #2919] ERROR -- : Thread-9472: Failed fetching 
archival_object id=1484623: too many connection resets (due to Net::ReadTimeout 
- Net::ReadTimeout) after 0 requests on 3150, last used 1615590893.870297 
seconds
ago

prior to the Java Heap error. In that log, there were a number of connections 
for the staff indexer after the PUI indexer stopped reporting, then an 88 
minute gap prior to the above connection error and then finally a Java Heap 
error in the archivesspace.out log.

Does the indexer reauthenticate each time it connects to get more information?  
The earlier question about authentication has me wondering if my database 
server might be balking at the number of reconnections or something. I'm trying 
to index 760K records.

Bottom line is that I'm still not getting my PUI index creation to complete. 
Each run can take several days before it finally fails and I have to start all 
over again.  I'm looking for any help to track down why this slowdown is 
occurring and what I can do to address it.

Th

Re: [Archivesspace_Users_Group] PUI indexing issues

[Blake Carver]

> I've now left my PUI indexing threads and count at the default (which I 
> believe is 1 thread and 25 records/thread).

Try dropping both indexer_records_per_thread and indexer_thread_count for both 
PUI and Staff indexers. Maybe in half or so. Sometimes with larger records it 
just needs to be slowed down.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Tuesday, March 16, 2021 12:51 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] PUI indexing issues

Hello again.

I'm still trying to understand some indexing issues. I've now left my PUI 
indexing threads and count at the default (which I believe is 1 thread and 25 
records/thread). And I have given 4GB to Java processes. I've tried other 
values as well, but with similar results.

No matter what values I use, I cannot seem to fully index PUI. Each time, it 
will start well but continuously slow down. I've kept a spreadsheet of the 
number of records/hr I'm indexing and have several attempts which start in the 
50-60K/hr range and then continuously slow down to the 1800-1500/hr speed until 
finally dying with a Java Heap error. I think I'm headed to that again this 
round.

Why might this be happening?  Could my data have been corrupted during the 
transfer from Lyrasis? (I'm working with a database export of our production 
data). Is the database too far away (our database is in an AWS RDS being 
accessed from our AWS EC2).

I do have one log which gave this error:

E, [2021-03-12T18:14:53.886243 #2919] ERROR -- : Thread-9472: Failed fetching 
archival_object id=1484623: too many connection resets (due to Net::ReadTimeout 
- Net::ReadTimeout) after 0 requests on 3150, last used 1615590893.870297 
seconds
ago

prior to the Java Heap error. In that log, there were a number of connections 
for the staff indexer after the PUI indexer stopped reporting, then an 88 
minute gap prior to the above connection error and then finally a Java Heap 
error in the archivesspace.out log.

Does the indexer reauthenticate each time it connects to get more information?  
The earlier question about authentication has me wondering if my database 
server might be balking at the number of reconnections or something. I'm trying 
to index 760K records.

Bottom line is that I'm still not getting my PUI index creation to complete. 
Each run can take several days before it finally fails and I have to start all 
over again.  I'm looking for any help to track down why this slowdown is 
occurring and what I can do to address it.

Thanks,
Tom
--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

[Blake Carver]

https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05

You'll want to find the date more like '2021-03-14 02:00%' or would it be 
03-13? Whatever the date was this year.
Find any date with a time between 2-3am and just change it to any real hour.
ArchivesSpace did "something" (probably restarted?) at a bad time on Sunday 
morning and wrote a time that never happened.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of James 
Bullen 
Sent: Sunday, March 14, 2021 11:04 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Java error - 
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3


Oh gee, I’ve seen that horror. And, yes, it is caused by records having times 
in that non-existent hour. From memory the only fix I could find was to delete 
the offending rows, or update their times.


Cheers,
James



On Mar 15, 2021, at 1:59 PM, Tom Hanstra 
mailto:hans...@nd.edu>> wrote:

I don't seem to be able to win with ArchivesSpace.

After having indexing again finally give up because of another Java heap error, 
I restarted archivesspace again with some different java settings. I believe it 
actually got through the indexing, at least of the first repository.

But tonight, looking at the logs, there is another error that seems to have 
something to do with, perhaps, daylight savings time?  I'm seeing this Java 
error in the logs, even after a restart:


INFO: An exception happened during JRuby-Rack startup
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
--- System
jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64]
Time: 2021-03-14 22:46:48 -0400
Server: jetty/8.1.5.v20120716
jruby.home: uri:classloader://META-INF/jruby.home

--- Context Init Parameters:
jruby.max.runtimes = 1
jruby.min.runtimes = 1
public.root = /
rack.env = production

--- Backtrace
Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3



Did something get corrupted in the database?  What might be happening to result 
in this error?
How do I fix it?

Thanks,
Tom

--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

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

Re: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts in AS title field

[Blake Carver]

There is a JIRA here about providing better support for right-to-left (RTL) 
scripts, ideally bi-directional text

https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1144

And another about Hebrew characters printed left-to-right in staff-side PDFs

https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1195

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Bradley 
Bauer 
Sent: Monday, March 8, 2021 12:41 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Using Arabic or right-to-left scripts 
in AS title field

Hello all,

I am interested in this as well, as I have wanted to enter Arabic titles of 
documents or printed items (such as ephemera or printed material) in their own 
script, and not just as transliterated text, where possible.

Over the months, I have experienced a couple of things when doing so, either in 
the title field, or in notes.

On one level, having both the Arabic and Latin script in the same field won't 
work, left-to-right and right-to-left texts don't share fields very well.  That 
led me to start using the "notes" field at the file level, so I could put an 
alternate form of the title below, and see whether it displays.  I tried this 
initially using English in the title field, and Arabic in the note (although 
one could do the reverse as well).  The first time I tried that, when I created 
a preview copy, it gave me just hash-tag symbols instead of Arabic text.  
Recently when I tried again, I got Arabic letters, but separated, and only in 
their initial form, not the medial or final forms of the letters (using the 
correct form is critical in Arabic text, which has three forms based on the 
placement of a given letter within a word).  So the display in Arabic would 
read something like this:  A-R-A-B-I-C_T-E-X-T.

If there are some well-proven work-arounds for that, it would be really helpful 
to know.

Best regards,

Brad Bauer
NYU Abu Dhabi Library


On Sun, Mar 7, 2021 at 2:23 AM Jasmine Soliman 
mailto:jasmine.soli...@nyu.edu>> wrote:
Hello,

I'd like to connect with anyone who is currently using, or experimenting with, 
Arabic or r-t-l script in the title field of AS. We've had mixed results with 
punctuation/typographical symbols when trying to include both English and 
Arabic in the title, so I'd like to connect with anyone working on this.

Best regards,
Jasmine
jasmine.soli...@nyu.edu




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


--
Brad Bauer
Librarian for Archives and Special Collections
New York University Abu Dhabi
PO Box 129188
Saadiyat Island
Abu Dhabi, UAE
e-mail:  b...@nyu.edu
phone:  +971 2 628 7335

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

Re: [Archivesspace_Users_Group] Containers not being associated with their resources

[Blake Carver]

Those MySQL errors look like the ones already reported and are probably not 
causing any problems.

https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9

Turn the mysql error logging thing off and set the other loglevel errors to 
debug and look for any FATAL or ERROR in the logs.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Mark 
Cyzyk 
Sent: Wednesday, March 3, 2021 10:20 AM
To: Rachel Aileen Searcy ; Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] Containers not being associated with 
their resources


More:

In our development environment, I configured full error logging.  I then ran 
one of our queries that is failing, stopped ASpace, then began scrutiny of 
archivesspace.out.

Here are my disturbing findings:

E, [2021-03-03T09:47:29.950934 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: 
DESCRIBE `agent_relationship_associative`
E, [2021-03-03T09:47:29.960346 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT 
* FROM `agent_relationship_associative` LIMIT 1
E, [2021-03-03T09:47:29.968749 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_associative' doesn't exist: SELECT 
* FROM `agent_relationship_associative` LIMIT 1
E, [2021-03-03T09:47:29.984480 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: 
DESCRIBE `agent_relationship_earlierlater`
E, [2021-03-03T09:47:29.987451 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: 
SELECT * FROM `agent_relationship_earlierlater` LIMIT 1
E, [2021-03-03T09:47:29.990034 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_earlierlater' doesn't exist: 
SELECT * FROM `agent_relationship_earlierlater` LIMIT 1
E, [2021-03-03T09:47:30.84 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: 
DESCRIBE `agent_relationship_parentchild`
E, [2021-03-03T09:47:30.007362 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT 
* FROM `agent_relationship_parentchild` LIMIT 1
E, [2021-03-03T09:47:30.011525 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_parentchild' doesn't exist: SELECT 
* FROM `agent_relationship_parentchild` LIMIT 1
E, [2021-03-03T09:47:30.021769 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't 
exist: DESCRIBE `agent_relationship_subordinatesuperior`
E, [2021-03-03T09:47:30.024655 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't 
exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT 1
E, [2021-03-03T09:47:30.028291 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.agent_relationship_subordinatesuperior' doesn't 
exist: SELECT * FROM `agent_relationship_subordinatesuperior` LIMIT 1



E, [2021-03-03T09:47:30.166299 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.container_location' doesn't exist: DESCRIBE 
`container_location`
E, [2021-03-03T09:47:30.179378 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM 
`container_location` LIMIT 1
E, [2021-03-03T09:47:30.181948 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.container_location' doesn't exist: SELECT * FROM 
`container_location` LIMIT 1



E, [2021-03-03T09:47:30.575599 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.note_bibliography' doesn't exist: DESCRIBE 
`note_bibliography`
E, [2021-03-03T09:47:30.579327 #27625] ERROR -- : 
Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 
'archivesspaceDevelopment.note_bibliography' doesn't exist: SELECT * FROM 
`note_bibliography` LIMIT 1
E, 

Re: [Archivesspace_Users_Group] Containers not being associated with their resources

[Blake Carver]

Are there any errors in your logs? Look for ERROR and/or FATAL

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Mark 
Cyzyk 
Sent: Monday, March 1, 2021 5:18 PM
To: Rachel Aileen Searcy ; Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] Containers not being associated with 
their resources


Thanks, Rachel!

I've now completely reindexed everything (a "hard reindex") and still no joy.

I am noticing there is no "location.dat" file in our /indexer_pui_state/:

-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
3_archival_object.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 3_classification.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
3_classification_term.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
3_digital_object_component.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 3_digital_object.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 3_resource.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
4_archival_object.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 4_classification.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
4_classification_term.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
4_digital_object_component.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 4_digital_object.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 4_resource.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
5_archival_object.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 5_classification.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
5_classification_term.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
5_digital_object_component.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 5_digital_object.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 5_resource.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 _deletes_deletes.dat
-rw-r--r--. 1 archivesspace archivesspace   11 Mar  1 17:13 
repositories_repositories.dat

Should there be?

Our two problem repositories here are 4 and 5.  The Staff interface reports "0" 
Resources for both.  Yet when I run the Resources List Report I do indeed get 
back a report with Resources.  Puzzling.

It's like something in the backend DB has become disconnected, but just for 
these two repositories.  Not sure how.

If anyone has any suggestions, I would greatly appreciate hearing them!

Mark


<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.


On 2/24/21 11:11 AM, Rachel Aileen Searcy wrote:
Hi Mark

We ran into a similar issue recently, where newly created containers were not 
being properly associated with the resource record, and updates to locations or 
barcodes were not showing up in searches or the Manage Top Containers view. We 
looked at the timestamp files for the indexer, and noticed that there was no 
location.dat file. We performed a soft 
re-index,
 after which our containers, barcodes, and locations resumed behaving as 
expected. We also have recurring monthly system restarts (which will now 
include a soft re-index going forward) built into our schedule, which seems to 
help with maintaining overall performance.

I'm not sure if this is exactly what you're experiencing, but I hope it's 
helpful. Take care,
Rachel

On Mon, Feb 22, 2021 at 5:45 PM Mark Cyzyk 
mailto:mcy...@jhu.edu>> wrote:

Dear ASpace list,

 From one of our Archivists:

> When I create a new container, either manually or by spreadsheet
> ingest, the container appears properly in the Instance field of the
> record. From the resource, I can open the container record and it
> appears to be associated with the resource correctly. However, in the
> container management module, when I search for all containers
> associated with the collection, the recently created container is not
> listed. If I search for the new container's barcode, the container
> appears in the search results but with no associated resource. I can
> also locate the new containers by searching for unassociated containers.

It seems like some linkage is not happening here.

More, this is only happening in his Repository, not our other, larger
Repository.

Has anyone else run into this?

Mark

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.

___

Re: [Archivesspace_Users_Group] System upgrade from v1.5.2 to v2.5.2 and finally to v2.8.0

[Blake Carver]

For this one I'd do a full reindex.
Shut down ArchivesSpace
Delete everything in /data/
Yes, every single thing in the /data/ directory, but not the directory, you 
need it, just empty.
Start ArchivesSpace
It'll take a while to get all indexed.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Corey 
Schmidt 
Sent: Wednesday, February 10, 2021 8:27 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] System upgrade from v1.5.2 to v2.5.2 
and finally to v2.8.0

Jimmy,

After the upgrade, did you run a re-index? I know after we upgraded from 2.6 to 
2.8 we had data that was all in the wrong places in the Staff Interface, due to 
the Solr index being out of sync with the database.

Corey

Corey Schmidt
ArchivesSpace Project Manager
University of Georgia Special Collections Libraries
Email: corey.schm...@uga.edu

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jimmy 
SUNG 
Sent: Wednesday, February 10, 2021 3:44 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] System upgrade from v1.5.2 to v2.5.2 and 
finally to v2.8.0

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]


Hi,



I encountered an issue after system upgrade. The information on  the “Dates” 
field of Accession has messed up with other data and the create_time is not 
correct. For below record, it should be created on 2015-01-21. Grateful if you 
can give some advice!



Before upgrade (version v.1.5.2), the “Dates” field: -

Created by ccsung

2015-01-21 15:33:35 +0800

Last Modified by ccsung

2015-06-05 13:28:34 +0800



After upgrade (version v2.8.0), the “Dates” field: -

{"lock_version"=>0, "begin"=>"2007-03-02", "end"=>"2009-06-05", 
"created_by"=>"ccsung", "last_modified_by"=>"ccsung", 
"create_time"=>"2015-06-05T05:28:34Z", "system_mtime"=>"2015-06-05T05:28:34Z", 
"user_mtime"=>"2015-06-05T05:28:34Z", "date_type"=>"inclusive", 
"label"=>"creation", "jsonmodel_type"=>"date"}



Best Regards,

Jimmy SUNG

Technology Support Services

The University of Hong Kong Libraries


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

Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)

[Blake Carver]

Yep, that's it. ArchivesSpace is unhappy with 11.
Java 8 only:
https://archivesspace.github.io/tech-docs/administration/getting_started.html

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Philip 
Webster 
Sent: Monday, January 18, 2021 11:57 AM
To: 'Archivesspace Users Group' 

Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)


Hi,

Java –version on the affected server gives the following:

openjdk version "11.0.9.1" 2020-11-04

OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04)

OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, mixed mode, 
sharing)



Regards,



Phil



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: 15 January 2021 14:51
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1)



Which version of Java are you running?

See 
http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-February/007388.html

Andrew.



On 13/01/2021 12:56, 
philip.webs...@sheffield.ac.uk wrote:

Hi,

We're currently in the process of deploying ArchivesSpace 2.8.1 to our 
production server following a lengthy period of testing and development on some 
other servers. Strangely, the public user interface is failing to load due to a 
Ruby dependency not being pulled in when the service starts up. The dependency 
is SASSC, which is present in the gems folder within the ArchivesSpace 2.8.1 
installation.



An error message appears in the logs suggesting that SASSC isn't being imported 
due to it not having native extensions built, and in turn that causes a 500 
error to be visible in the browser together with a stack trace showing the root 
cause to be the missing library. I tried building the extension using the 
native Ruby tools in our Linux distribution and found that had no effect. After 
some lengthy investigation it turned out that the development and test servers 
do not even have the native Ruby packages installed, and that everything runs 
entirely through jRuby. That being the case, I have no idea how to solve the 
issue with this dependency.



None of this is mentioned in the documentation, so I’m at a loss as to what to 
do next.



Does anyone have any suggestions?



Thanks,



Philip Webster

The University of Sheffield





___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

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

Re: [Archivesspace_Users_Group] Issues Upgrading

[Blake Carver]

That part of the log isn't super helpful. I'd guess the real error is above 
that someplace.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Preston 
Howell 
Sent: Friday, January 8, 2021 2:37 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Issues Upgrading

Good afternoon all

I have spent some time over the last couple of days updating software on our 
server running our instance of ArchivesSpace, including updating from 2.7.1 to 
2.8.1. The server is currently running Ubuntu 20.04. I didn't realize that this 
update would mean Java 11 would be installed as default. I've now changed it to 
Java 8, but am unable to get ASpace to start. Attached is a screenshot of my 
log file. I'm kinda stumped at this point. Any help would be appreciated.

Thanks in advance.

[Screen Shot 2021-01-08 at 2.33.30 PM.png]

--

[https://lh6.googleusercontent.com/gy91ZxMadyMT9F5z4RB8Jq9gwC66YtvxoxTTXMHZvO5v5Y3cEFgymICQ-xTQCrF3oG2m-DS3Fy6CClg-IuPeMYnffW5KaWy-d59DPcuN-UvmhprdIzBte6aS6nD8PJH3gI_w38AD]

Preston Howell  |  Library Technology Specialist  |  Nicholson Library
Anderson University  |  1100 E. 5th St., Anderson, IN 46012
(765) 641-4270  |  anderson.edu

Confidentiality Notice: Because email is not a secure medium, confidentiality 
of email cannot be guaranteed.  This message is for the sole use of the 
intended recipient(s) and may contain confidential and privileged information.  
Any unauthorized review, use, disclosure, distribution, or copying is 
prohibited.  If you are not the intended recipient, please contact the sender 
by replying to this email and destroy/delete all copies of this email message.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Collection Organization not populating on v2.8.1

[Blake Carver]

Just to correct the record here ... Sorry, that wasn't  PR 1822, it's 1882 that 
holds the change.
Somehow I confused my numbers.

https://github.com/archivesspace/archivesspace/pull/1882

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Schanz, 
Megan 
Sent: Tuesday, December 15, 2020 8:50 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Collection Organization not populating 
on v2.8.1

In case it helps anyone else, our issue was with the change to the default Solr 
query parameter in v2.8.0 (we were going to 2.8.1 from 2.7.1).

The new default value:
AppConfig[:solr_params] = { 'mm' => '100%' }

Original value in 2.7.1:
AppConfig[:solr_params] = { "q.op" => "AND" }

The 'mm:100%' meant that when we had a query that OR'd a bunch of resources 
there would never be a record that had a 100% match on all of the criteria (one 
record couldn't have multiple IDs).

Our understanding from PR 
1882<https://urldefense.com/v3/__https://github.com/archivesspace/archivesspace/pull/1822__;!!HXCxUKc!ldN3U6NtcOocueWM76liwl7ZSJIP6agHL1Cj5kW74PFp4rEEl3iIERyAzn9mVVo$>
 (thanks for this link Blake), is that it is only for custom reporting. Since 
we're not doing anything with this we are just changing solr_params back to 
what worked for us in 2.7.1 and the collection organization is now populating 
as expected.

- Megan


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Schanz, 
Megan 
Sent: Thursday, December 3, 2020 10:00 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Collection Organization not populating 
on v2.8.1

Thanks Blake. Unfortunately that doesn't seem to be our problem. We've tried a 
full re-index twice and they both completed without errors. I went into Solr 
and queried a sample resource and one of its archival objects; and both 
returned completed records.

- Megan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, December 2, 2020 3:53 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Collection Organization not populating 
on v2.8.1

I'm not sure what to make of that JavaScript stuff, it might be related, though 
hopefully that's not the real problem.

When you upgraded to 2.8, did you start over with a totally empty /data/ 
directory? If not, I'd suggest doing a full reindex. I know that indexing 
troubles can make those tabs empty when they should have stuff. Maybe it's 
looping or just not done yet, or something is wrong somehow.
So...
stop archivesspace
rm -rf /data/*
start archivesspace

Let it run until the indexing is totally finished up, watch the logs for a loop 
and/or errors.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Schanz, 
Megan 
Sent: Wednesday, December 2, 2020 8:24 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Collection Organization not populating on 
v2.8.1

Hi all,

We've recently started testing v2.8.1 and are stuck on an issue on the public 
interface side. On the Collection Organization tab of a resource (i.e. 
repositories/4/resources/6423/collection_organization), the left-side pane is 
empty; whereas with v2.7.2 it contained the collection objects as you would 
expect. The data is identical between our test instance and our production 
instance so we are able to compare both versions side-by-side.

When inspecting the page on the browser, we can see the top level object still 
populates with the correct data-urls, but there are no child objects underneath 
it:


Furthermore, the console is reporting errors coming from the Javascript code:
Uncaught TypeError: Cannot read property 'replace' of undefined
at Object.r.uri_to_parts 
(largetree-6541a51b3fceaac15ebc7b1a7f5155d473ee5cc35f3b337cb0ac844dd66f0666.js:1)
at Object.r.uri_to_tree_id 
(largetree-6541a51b3fceaac15ebc7b1a7f5155d473ee5cc35f3b337cb0ac844dd66f0666.js:1)
at e 
(treesync-0bcad7c81eb2991851e7ba2552a688032d6a805079546b7cb3cec080e69ed223.js:1)
at 
treesync-0bcad7c81eb2991851e7ba2552a688032d6a805079546b7cb3cec080e69ed223.js:1
Uncaught TypeError: Cannot read property 'getBoundingClientRect' of undefined
at n 
(infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1)
at o.scrollToRecord 
(infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1)
at 
infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1

No errors or warnings are being recorded in the logs on the server though.

Has anyone else run into this issue or have ideas to further debug this?

Thanks!

Megan Schanz
Developer and System Administrator
Mic

Re: [Archivesspace_Users_Group] spreadsheet importer max number of rows in v2.8?

[Blake Carver]

Nope, just 2.8.0. Before that it was a plugin.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Solek, 
VivianLea 
Sent: Monday, December 7, 2020 3:17 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] spreadsheet importer max number of 
rows in v2.8?


Hi Blake,



Can the config settings be tweaked in 2.7.1?



Many thanks.

VivianLea



VivianLea Solek

Archivist

Knights of Columbus Supreme Council Archives

1 State Street
New Haven, CT 06511-6702

Phone 203 752-4578
Fax 203 865-0351



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Monday, December 7, 2020 3:14 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] spreadsheet importer max number of 
rows in v2.8?



You might want to upgrade to 2.8.1 first, it runs as a background job now, and 
that will help with larger imports:

https://github.com/archivesspace/archivesspace/pull/1980<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fpull%2F1980=04%7C01%7Cvivianlea.solek%40kofc.org%7Cab6dc0743b0c49dbf5dd08d89aec9904%7C8a4b69f88bb74be59eda6c40a157248c%7C0%7C0%7C637429688257589785%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=HacWW3lMqlT879sn5F4R0MYfW3CqB8xW%2BhGqyxMIh3Q%3D=0>



2.8.0 does have it in the config settings:

AppConfig[:bulk_import_rows] = 1000
AppConfig[:bulk_import_size] = 256



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Benn Joseph 
mailto:benn.jos...@northwestern.edu>>
Sent: Monday, December 7, 2020 2:33 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] spreadsheet importer max number of rows in 
v2.8?



Hi everyone,

We’re planning to do some test ingests of big collections using the spreadsheet 
importer (aspace-import-excel) on our ASpace sandbox, which is currently on 
version 2.8. I don’t know if this was the case in the past, but I’m hearing 
from some folks that there is an upper-limit to the number of rows the ingest 
spreadsheet can have, which for us appears to be set to a max of 2000. Does 
anyone know if this is something that can be increased, like in a setting 
somewhere?



Thanks,

--Benn



Benn Joseph

Head, Collections Services

McCormick Library of Special Collections & University Archives

Northwestern University Libraries

Northwestern University

www.library.northwestern.edu<https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.library.northwestern.edu%2F=04%7C01%7Cvivianlea.solek%40kofc.org%7Cab6dc0743b0c49dbf5dd08d89aec9904%7C8a4b69f88bb74be59eda6c40a157248c%7C0%7C0%7C637429688257599736%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=smXVVAkXtxF38PHxPrhX5R6P7uHNc%2BtYGtUY2NMpZ2E%3D=0>

benn.jos...@northwestern.edu<mailto:benn.jos...@northwestern.edu%0d>

847.467.6581



CONFIDENTIALITY NOTICE: This message and any attachments may contain 
confidential, proprietary or legally privileged information and is intended 
only for the use of the addressee or addressees named above for its intended 
purpose. If you are not the intended recipient of this message, this message 
constitutes notice that any review, retransmission, distribution, copying or 
other use or taking any action in reliance on the information in this message 
and its attachments, is prohibited. If you receive this communication in error, 
please immediately advise the sender by reply e-mail and delete this message 
and its attachments from your system without keeping a copy. Unless expressly 
stated in this e-mail, nothing in this message may be construed as a digital or 
electronic signature. Thank you.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group