Thanks, Blake, and apologies -- I meant to say config.rb (not config-defaults.rb). Even with the suggested debug settings in place in config.rb, our Archivesspace instance doesn't produce error logging.
We are running an Archivesspace v3.2.0 release we built + local changes in locales and plugins. It was built on RHEL 7.9 with OpenJDK 11.0.14.1. All of our AppConfig[:XXXX_log_level] are set to "debug" in our config.rb. All of the log destinations are set to "default". There is an archivesspace.out file in the /logs directory, but it only contains startup info and a few warnings and is not modified as frequently as we would expect. As the archivesspace.out file does have some things written to it, there does not seem to be a write permissions error. We would expect there to be additional logging because we are encountering errors in the PUI. Thanks again for any help, Wendy ________________________________ From: [email protected] <[email protected]> on behalf of Blake Carver <[email protected]> Sent: Wednesday, June 8, 2022 1:25 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode Running in production mode means downloading and running the release, not the source code https://github.com/archivesspace/archivesspace/releases/download/v3.2.0/archivesspace-v3.2.0.zip Changing configuration variables would then be done in config.rb not config-defaults.rb. Your archivesspace.out log file should then end up in the /logs/ directory. ________________________________ From: [email protected] <[email protected]> on behalf of Hagenmaier, Wendy L <[email protected]> Sent: Wednesday, June 8, 2022 12:26 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode Thanks, Blake. We checked our config-defaults.rb, and those lines match what you linked to. So it seems like we've set the log levels to DEBUG, but we're still not seeing any error messages being logged. Is there something else we should check that might be getting in the way of the logs? Here's what we have for those lines in config-defaults.rb : 57 AppConfig[:frontend_log] = "default" 59 AppConfig[:frontend_log_level] = "debug" 61 AppConfig[:backend_log] = "default" 62 AppConfig[:backend_log_level] = "debug" 64 AppConfig[:pui_log] = "default" 65 AppConfig[:pui_log_level] = "debug" 67 AppConfig[:indexer_log] = "default" 68 AppConfig[:indexer_log_level] = "debug" ________________________________ From: [email protected] <[email protected]> on behalf of Blake Carver <[email protected]> Sent: Tuesday, June 7, 2022 1:20 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode You can set the log levels to DEBUG here https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L49-L64 Keep in mind that on version 3.2 you'll have Solr stuff being written into the sperate Solr server logs. ________________________________ From: [email protected] <[email protected]> on behalf of Hagenmaier, Wendy L <[email protected]> Sent: Tuesday, June 7, 2022 12:59 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode Hi Blake, When running ASpace (3.2.0) in production mode (as opposed to development mode), should we be seeing information in our error logs? We are preparing to go live with 3.2.0. After testing 3.2.0 in development mode, we want to test our stage instance of ASpace 3.2.0 in production mode to mimic what our production instance will look like. We aren't getting any info from the logs in production mode, making it difficult to troubleshoot. Is there a way we can enable logs in production mode? Thank you, Wendy Wendy Hagenmaier Digital Curation Archivist Service Owner, University Archives & Special Collections Repository and retroTECH<https://www.library.gatech.edu/retrotech> Archives, Records Management, and Digital Curation Georgia Tech Library Atlanta, GA 30332 [email protected] Pronouns: she/her ________________________________ From: [email protected] <[email protected]> on behalf of Blake Carver <[email protected]> Sent: Wednesday, June 1, 2022 5:02 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode https://archivesspace.github.io/tech-docs/development/dev.html That explains the development mode. ________________________________ From: [email protected] <[email protected]> on behalf of Duckett, Brian (NIH/NLM) [C] <[email protected]> Sent: Wednesday, June 1, 2022 4:45 PM To: [email protected] <[email protected]> Cc: Liu, Steve (NIH/NLM) [C] <[email protected]>; Whitaker, John (NIH/NLM) [C] <[email protected]>; Kalyanasundaram, Sriram (NIH/NLM) [C] <[email protected]> Subject: [Archivesspace_Users_Group] Requesting Clarification of development vs production mode Hello, A few weeks ago, we were attempting to resolve an issue with the Mizuno dependency being flagged during an internal security scan. During research efforts we came across the following post. https://archivesspace.org/archives/7226?utm_source=rss&utm_medium=rss&utm_campaign=archivesspace-update-december-2021 This post references two different modes ArchivesSpace can run in, development and production. We are seeking clarification of what the differences are between the two modes, how to implement one versus the other as well as verify which mode we are currently running in. Unfortunately, I have not found this information in the tech docs, so I do apologize in advance if the information is there and has been overlooked. Thank You, Brian
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
