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
