Thank you for that reminder, Blake! Another question: the print action was being run from the following pages. Wouldn't clicking the AS print button itself register in the logs? If so, how could I efficiently find those lines?
https://archivesspace.ubalt.edu/repositories/2/resources/92 https://archivesspace.ubalt.edu/repositories/2/resources/126 https://archivesspace.ubalt.edu/repositories/2/resources/21 Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbrene...@ubalt.edu<mailto:kbrene...@ubalt.edu> I believe in freedom of thought and freedom of speech. Do you? From: archivesspace_users_group-boun...@lyralists.lyrasis.org <archivesspace_users_group-boun...@lyralists.lyrasis.org> On Behalf Of Blake Carver Sent: Wednesday, January 5, 2022 12:31 PM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] Advice on what to look for in AS logs after printing error? [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover over any links before clicking and use caution when opening attachments.] grep the logs for ERROR or FATAL ________________________________ From: archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> <archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> on behalf of Kyle Breneman <kbrene...@ubalt.edu<mailto:kbrene...@ubalt.edu>> Sent: Wednesday, January 5, 2022 12:28 PM To: archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org> <archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@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 kbrene...@ubalt.edu<mailto:kbrene...@ubalt.edu> I believe in freedom of thought and freedom of speech. Do you?
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
