ArchivesSpace (or ASpace for short) is a server whose main purpose is to host a software program also named… ArchivesSpace. The program is “an open source archives information management application for managing and providing web access to archives, manuscripts and digital objects”. The server also hosts a few auxiliary programs who take the output from ArchivesSpace and convert it into various other formats, which are then made available via an Apache webserver on the same machine.
...
The current production version of Aspace is 2.7.1 .
Terminal access: ssh -i /path/to/production/pem_file.pem ubuntu@50.16.132.240
The ubuntu user owns all the admin scripts.
The relevant Ansible role is: /roles/archivesspace/ in the ansible-inventory codebase.
...
We restart the ArchivesSpace program (not the server) using a cronjob that runs /opt/archivesspace/archivesspace.sh restart every night at 2 am. This prevents a chronic memory leak from eating up all the CPU credits for the machine.
When the server is restarted, Jetty creates a set of temporary files in /tmp
that look like this:
hsperfdata_ubuntujetty-0.0.0.0-8089-backend.war-_-any-3200460420275417425jetty-0.0.0.0-8090-solr.war--any-_1669707332158985985jetty-0.0.0.0-8091-indexer.war-_aspace-indexer-any-3026688914663148716jetty-0.0.0.0-8080-frontend.war--any-3028692540497613460jetty-0.0.0.0-8081-public.war--any-268053434795494538jetty-0.0.0.0-8082-oai.war--any-_243630232179303838
Only the most recent set are used by Jetty, but the old ones accumulate rapidly if the server is restarted nightly.
A system to clean these up will be needed – some variation on find /tmp -maxdepth 1 -type d -mtime +20 | grep jetty.*war .
Export
The ArchivesSpace EADs are harvested by:
...