[Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error?

[Lyman Ross]

We had a similar problem a month ago which was caused by mixed protocols (http/https). We resolved it by forcing all traffic to use https.

-Lyman

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Kyle Breneman
Sent: Wednesday, January 05, 2022 12:29 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error?

Our archives staff have noticed that AS tends to get hung up when users click the Print button on some of our largest collections.  Campus IT tested this today.  The server did not hang for them, but the print action also did not complete.  They got a very, very generic error message (attached).

I have access to the ArchivesSpace files on the server, including the /logs directory, but I'm not sure how to parse the logs for clues.  Does anyone have advice for how I can sift through the logs?

Kyle Breneman
Integrated Digital Services Librarian
The University of Baltimore
kbreneman at ubalt.edu<mailto:kbreneman at ubalt.edu>
I believe in freedom of thought and
freedom of speech. Do you?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220105/85886aad/attachment.html>