[Archivesspace_Users_Group] Intermittent Outages

[carrie.daniels at louisville.edu]

We’ve been experiencing something similar, and yet different… We randomly get proxy errors when working in the staff interface. ASpace seems to restart itself after a while. This happens when we are making edits to Accession records. We are running 1.4.2.

Carrie

Carrie Daniels
University Archivist and Director,
Archives and Special Collections
University of Louisville


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Trevor Thornton
Sent: Tuesday, February 28, 2017 1:14 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Intermittent Outages

I have some tasks that make multiple API calls and recently I've noticed that the session will sometimes get dropped (API returns 412 response with a message saying that the token is invalid) after only a few minutes (should remain valid for 60 minutes). I think it started happening when we upgraded from 1.4.x to 1.5.1, and it doesn't happen all the time, but I don't know why it happens when it does.

We've also had cases where AS becomes unresponsive. When this has happened I would usually just restart it, so I don't know if it would have come back online if I waited long enough.

On Tue, Feb 28, 2017 at 12:27 PM, Alexander Duryee <alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>> wrote:
Our production instance of ASpace has been suffering from intermittent outages for the past few weeks.  Roughly once or twice a day, the application will go down for 1-5 minutes, then bring itself back up.  Perplexingly, this doesn't seem to impact the backend - for example, the application went down during a reindex, but the reindex continued (and was logged) during the outage.  However, API requests are dropped and the frontend is inaccessible during the outage.
We haven't identified a cause for the outages (e.g. heavy traffic, lots of database calls), as there's no consistent pattern.  There's nothing in archivesspace.out to indicate any troubles.
Has anyone else experienced similar issues?  Is there another log that we could refer to (e.g. ASpace's Apache instance) to diagnose the outages?

Thanks!
--Alex

--
Alexander Duryee
Metadata Archivist
New York Public Library
(917)-229-9590<tel:(917)%20229-9590>
alexanderduryee at nypl.org<mailto:alexanderduryee at nypl.org>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwMFaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=5Q0_NDfXIo1GAZnkNLoezH8GMwO1xdN0wOFI5K943YY&m=kGT602CWzyOrwnHRaTbTZlx8mypGi3RnMGlORqnEbl0&s=ntesVvh31kp4I80k4af8yJYpCXDDNq6eQ_-xQaGzLY4&e=>



--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170228/a4942b64/attachment.html>