Page Comparison

We store descriptions of our archival collections in the following places:

...

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.

...

Startup

• To start Archivesspace: sudo systemctl start archivesspace. You may need to run this several times (just wait 30 seconds between attempts.)

  • /opt/archivesspace/archivesspace.sh start (as user ubuntu)

• You can troubleshoot startup by looking at the start script (invoked by the above): /opt/archivesspace/archivesspace.sh start

• There may be a short delay as the server re-indexes data.

...

Note: as of August 2020, the below procedure has been rendered obsolete. We are now simply restarting the server with /opt/archivesspace/archivesspace.sh restart every Sunday at 2 am, which appears to solve the problem before it occurs.

...

• Contact all the main users listed above (especially Kent), and make sure they’re not actively working on the server.

• Once given the go-ahead:

  • Log in to the server.

  • Throughout the process, keep in mind you can run sudo systemctl status archivesspace for the daemon status at any point. If it’s running, you’ll see a variation on: [...]
Active: active (running) since Tue [...]

  • Run top in a separate window to monitor the CPU usage. The goal is to see a dramatic reduction in usage after this process.

  • sudo systemctl stop archivesspace

  • sudo systemctl start archivesspace (You may have to run this two or three times – the start script is finicky)

  • /opt/archivesspace/archivesspace.sh restart

  • If all else fails, you can also go into the AWS console and reboot the EC2 instance.

  • Once everything is properly restarted:

    • the https://archives.sciencehistory.org/ front-end is available again

    • After a few minutes, you should see the CPU use go down dramatically in top.

    • The AWS monitoring graph for CPU Utilization graph should drop. (see figure below.)

  • Once you’re done, notify all involved that the server is available again.

    

...