[Archivesspace_Users_Group] Digital Object Identifiers garbled

[Cowing [he], Jared]

Hi all,

We're currently testing v.3.1.1 (currently on 2.7.1) and have encountered
two issues we can't seem to resolve which may or may not be related. I'm
hoping that someone here is familiar with one or both and knows what may be
the root cause.

1. The identifiers for some (but not all) of our digital objects now appear
encrypted or otherwise garbled. Has anyone ever encountered this before?
Example: what was digital object identifier  *DC2019_049_0574* is now
*7e0baf32-263b-431a-9699-b480b3d789ed*
While there may be a pattern to which identifiers got garbled and which
didn't, I have yet to detect that pattern.

2. We're frequently encountering "We're sorry, but something went wrong"
errors in our testing environment. They usually only affect the staff-side,
while the public interface remains available. I got a copy of the error log
from our IT department, but I'm still trying to decipher what's in there.
They look similar to the errors reported in another thread earlier this
month:

E, [2022-01-24T14:42:56.114007 #25643] ERROR -- : Thread-2950:
uri:classloader:/jsonmodel_client.rb:490:in `all'
/opt/archivesspace/prod/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'
/opt/archivesspace/prod/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'
/opt/archivesspace/prod/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'


The second issue may not be unique to 3.1.1 for us since we're trying out a
new hosting environment for this version. The first issue was present I
believe even before we set up that new hosting environment.

Any suggestions for someone relatively new to ArchivesSpace to help isolate
the cause would be much appreciated.

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

[Archivesspace_Users_Group] Performance tuning

[Cowing [he], Jared]

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