From davidtriebwasser at berkeley.edu Mon Jul 3 13:13:06 2023 From: davidtriebwasser at berkeley.edu (David J Triebwasser) Date: Mon, 3 Jul 2023 10:13:06 -0700 Subject: [Archivesspace_Users_Group] V3.3.1 displaying unicode character Message-ID: We have upgraded from 2.7 to 3.3 and found a display issue in the table of contents view where a unicode character is displayed in a text field. instead of PIC-box: 1, Folder: 1 we are seeing PIC<200b>-<200b>box: 1, Folder: 1 it only shows up in the collection toc display, nowhere else in records. [image: image.png] -- David Triebwasser Technical Project Manager Library IT Department University of California, Berkeley 94720 510.982.1640 | 289 Doe Annex | lib.berkeley.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 58229 bytes Desc: not available URL: From suzanna.calev at wilkes.edu Thu Jul 6 15:28:15 2023 From: suzanna.calev at wilkes.edu (Calev, Suzanna) Date: Thu, 6 Jul 2023 15:28:15 -0400 Subject: [Archivesspace_Users_Group] Fwd: Capacity problems error in Aspace--suggestions? In-Reply-To: References: Message-ID: Any Aspace experts, We keep encountering a "capacity problems" error issue where archivesspace goes down until our network admin Mark reboots the system. This happened a while ago and it went away for a while but has come up again so I'm wondering if there's something we're missing or not thinking of with this? Should we upgrade to a newer version? Would that potentially fix this issue? If anyone has any suggestions or if you know someone who might be able to help us, we'd greatly appreciate it. Thank you, Suzanna ---------- Forwarded message --------- From: Kazokas, Mark Date: Thu, Jul 6, 2023 at 3:18?PM Subject: Re: To: Calev, Suzanna Suzanna, ASpace is back up I know when I was troubleshooting a while back, the person I was dealing with, had me change a few settings within the software and that seemed to be better for a little while, but it seems to be getting problematic again. The server has remained up and all of the reliant services seem to be OK _MySQL, Apache, etc.) I think it is most likely a software issue. Perhaps there is an update we could do. It might be worth reaching out to them FYI -- the server is running in AWS and we have several other servers running within the same region (including the main wilkes.edu website), that have not had any of these issues. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: capacityproblems.png Type: image/png Size: 33793 bytes Desc: not available URL: From smquimby at upenn.edu Thu Jul 6 17:57:33 2023 From: smquimby at upenn.edu (Quimby, Sean) Date: Thu, 6 Jul 2023 21:57:33 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace election results and new appointments Message-ID: Dear ArchivesSpace community members: On behalf of the Governance Board I am pleased to announce the following new members to for our governance groups. Large level: Kate Crowe, University of Denver Medium level: Maggie Hughes, The Huntington Very Small level: Linda Hocking, Litchfield Historical Society The Very Small race was a tie, and, as per ArchivesSpace custom, was decided by a coin flip. The newly elected members will serve terms from July 1, 2023 to June 30, 2026. I want to thank everyone who ran and/or voted. The Nominating Committee also worked to recruit new members for the Technical Advisory Council (TAC) and User Advisory Council (UAC). Please join me in welcoming: TAC Diane Biunno, Rutgers University Jacqueline Devereaux Asaro, Vanderbilt University Alexander Duryee, New York Public Library Bonnie Gordon, Columbia University Brianna Mclaughlin, Indiana University Michelle Paquette, Smith College UAC Susannah Broyles, Texas State University Mattie Clear, Washington and Lee University Will Clements, Princeton University Kelly Francis Matthew Gorham, Yale University Ryan Lee, Brigham Young University Jaime Margalotti, University of Delaware Dillon Thomas, Virginia Commonwealth University Ashley Williams, Hagley Museum and Library The new appointees to TAC and UAC will serve terms from July 1, 2023 to June 30, 2026. As I sign off as a member of the Governance Board, I would like to thank my fellow members (I learned so much from you!) and the amazing program staff, who provided extraordinary insight and guidance. It has been a pleasure to serve the AS community these past few years. Thank you! Sean Quimby Associate University Librarian for Special Collections Kislak Center for Special Collections, Rare Books & Manuscripts University of Pennsylvania Libraries 3420 Walnut Street Philadelphia, PA 19104-6206 e. smquimby at upenn.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Fri Jul 7 09:19:27 2023 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 7 Jul 2023 13:19:27 +0000 Subject: [Archivesspace_Users_Group] Registration and session proposals now open for the 9th annual ArchivesSpace member forum (Session proposals due July 10) In-Reply-To: References: Message-ID: [A picture containing text, screenshot, graphic design, fireworks Description automatically generated] Dear ArchivesSpace members, Registration is still available for our 9th Annual ArchivesSpace Member Forum in person in the Georgetown room of the Washington Hilton on July 26, 2023, from 9:00 AM - 12:30 PM. In addition to this in-person opportunity to meet, we will also be holding a virtual learning opportunity about new ArchivesSpace functionality on July 18, 2023. Registration is now open for both the in-person meeting and the pre-forum virtual workshop, though the schedule for the in-person meeting is still being developed. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. We encourage everyone planning to attend to consider submitting a session proposal. Proposals are due by next Monday, July 10. Brief 15-20 minute sessions showing off your organization?s implementation of ArchivesSpace, a tool or plug-in you?ve developed, a project your organization has undertaken or a new workflow you?ve developed are highly encouraged. There is a short Google form for proposals available at https://forms.gle/D8rpFY5PrVzp9cmW9. We are particularly excited to have as much community participation as possible in this forum since this year also marks the 10th year of ArchivesSpace! We hope that this year?s forum will be an opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about how they?ve been using ArchivesSpace, whether they?ve been using it for 10 years or 10 months. Please feel free to contact ArchivesSpace Community Engagement Lead Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing you in person or virtually and celebrating 10 years of ArchivesSpace. Jessica Dowd Crouch Community Engagement Lead for ArchivesSpace jessica.crouch at lyrasis.org [A picture containing text Description automatically generated] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 90654 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 357125 bytes Desc: image002.jpg URL: From davidtriebwasser at berkeley.edu Fri Jul 7 10:42:40 2023 From: davidtriebwasser at berkeley.edu (David J Triebwasser) Date: Fri, 7 Jul 2023 07:42:40 -0700 Subject: [Archivesspace_Users_Group] Missing Record Links in Events CSV download Message-ID: We have events with Record Links that show up in the "Browse->Events" listings and in the Event Detail pages. However when we use the "Download CSV" button at top right of listing, no record links are in the CSV. Any ideas? We see this in both version 2.8 and 3.3 [image: image.png] -- David Triebwasser Technical Project Manager Library IT Department University of California, Berkeley 94720 510.982.1640 | 289 Doe Annex | lib.berkeley.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 780665 bytes Desc: not available URL: From mcyzyk at gmail.com Fri Jul 7 12:06:00 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Fri, 7 Jul 2023 12:06:00 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string Message-ID: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> All, I'm hoping to get some advice/another set of eyes on this: I am trying to stage an upgrade of Aspace here on my workstation using Vagrant/Virtualbox and am running into an issue with the DB connect string I'm using in my config.rb file. * Preliminaries:* * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest Additions installed * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar (owned by ?archivesspace" user) * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) mysql> show databases; -------------- show databases -------------- +--------------------+ | Database?????????? | +--------------------+ | archivesspace????? | | information_schema | | mysql????????????? | | performance_schema | | sys??????????????? | +--------------------+ 5 rows in set (0.02 sec) * Solr 8.10.0 Core ??? startTime: ??????? 6 minutes ago ??? instanceDir: ??????? /var/solr/data/archivesspace ??? dataDir: ??????? /var/solr/data/archivesspace/data/ *The Problem:* Loading ArchivesSpace configuration file from path: /usr/share/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/share/archivesspace/thread_dump_backend.txt' to trigger a thread dump I, [2023-07-07T15:32:08.607923 #52254]? INFO -- : Thread-2002: Connecting to database: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&**useSSL=false*. Max connections: 24 *E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed* ======================================================================== ????? A trace file has been written to the following location: /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt ????? This file contains information that will assist developers in diagnosing ????? problems with your ArchivesSpace installation.? Please review the file's ????? contents for sensitive information (such as passwords) that you might not ????? want to share. ======================================================================== Jul 07, 2023 3:32:08 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.362-b09 on 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 +jit [linux-x86_64] Time: 2023-07-07 15:32:08 +0000 Server: jetty/9.4.44.v20210927 jruby.home: uri:classloader://META-INF/jruby.home *Notes:* Regarding my DB connect string: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false I appended ?useSSL=false? thinking the following error would go away: ?E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed No joy! Not sure how to remedy.? Advice GREATLY appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Jul 7 12:23:56 2023 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 7 Jul 2023 16:23:56 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string In-Reply-To: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> References: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> Message-ID: Haven't seen that one before but it looks like a common error, adding "AllowPublicKeyRetrieval=True " to the connection string looks like the answer ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Friday, July 7, 2023 12:06 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string All, I'm hoping to get some advice/another set of eyes on this: I am trying to stage an upgrade of Aspace here on my workstation using Vagrant/Virtualbox and am running into an issue with the DB connect string I'm using in my config.rb file. Preliminaries: * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest Additions installed * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar (owned by ?archivesspace" user) * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) mysql> show databases; -------------- show databases -------------- +--------------------+ | Database | +--------------------+ | archivesspace | | information_schema | | mysql | | performance_schema | | sys | +--------------------+ 5 rows in set (0.02 sec) * Solr 8.10.0 Core startTime: 6 minutes ago instanceDir: /var/solr/data/archivesspace dataDir: /var/solr/data/archivesspace/data/ The Problem: Loading ArchivesSpace configuration file from path: /usr/share/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/share/archivesspace/thread_dump_backend.txt' to trigger a thread dump I, [2023-07-07T15:32:08.607923 #52254] INFO -- : Thread-2002: Connecting to database: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false. Max connections: 24 E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed ======================================================================== A trace file has been written to the following location: /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt This file contains information that will assist developers in diagnosing problems with your ArchivesSpace installation. Please review the file's contents for sensitive information (such as passwords) that you might not want to share. ======================================================================== Jul 07, 2023 3:32:08 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.362-b09 on 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 +jit [linux-x86_64] Time: 2023-07-07 15:32:08 +0000 Server: jetty/9.4.44.v20210927 jruby.home: uri:classloader://META-INF/jruby.home Notes: Regarding my DB connect string: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false I appended ?useSSL=false? thinking the following error would go away: E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed No joy! Not sure how to remedy. Advice GREATLY appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Jul 7 12:25:07 2023 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 7 Jul 2023 16:25:07 +0000 Subject: [Archivesspace_Users_Group] Missing Record Links in Events CSV download In-Reply-To: References: Message-ID: Maybe this setting? https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L689-L690 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of David J Triebwasser Sent: Friday, July 7, 2023 10:42 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Missing Record Links in Events CSV download We have events with Record Links that show up in the "Browse->Events" listings and in the Event Detail pages. However when we use the "Download CSV" button at top right of listing, no record links are in the CSV. Any ideas? We see this in both version 2.8 and 3.3 [image.png] -- David Triebwasser Technical Project Manager Library IT Department University of California, Berkeley 94720 510.982.1640 | 289 Doe Annex | lib.berkeley.edu [https://ci3.googleusercontent.com/mail-sig/AIorK4xntxIgauWV7u_oXak4YUQaBg2yOL_7oIhujcbBKyrSyKx--aC0pm6NIAZonF4nfYDik4Jw1ZY] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 780665 bytes Desc: image.png URL: From blake.carver at lyrasis.org Fri Jul 7 12:26:07 2023 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 7 Jul 2023 16:26:07 +0000 Subject: [Archivesspace_Users_Group] Fwd: Capacity problems error in Aspace--suggestions? In-Reply-To: References: Message-ID: That's not an ArchivesSpace error message, looks like something from the proxy maybe? If you can get the errors from the ArchivesSpace log, that'll tell us what's going on in ArchivesSpace at the time. Look for FATAL or ERROR in archivesspace.out ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Calev, Suzanna Sent: Thursday, July 6, 2023 3:28 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Fwd: Capacity problems error in Aspace--suggestions? Any Aspace experts, We keep encountering a "capacity problems" error issue where archivesspace goes down until our network admin Mark reboots the system. This happened a while ago and it went away for a while but has come up again so I'm wondering if there's something we're missing or not thinking of with this? Should we upgrade to a newer version? Would that potentially fix this issue? If anyone has any suggestions or if you know someone who might be able to help us, we'd greatly appreciate it. Thank you, Suzanna ---------- Forwarded message --------- From: Kazokas, Mark > Date: Thu, Jul 6, 2023 at 3:18?PM Subject: Re: To: Calev, Suzanna > Suzanna, ASpace is back up I know when I was troubleshooting a while back, the person I was dealing with, had me change a few settings within the software and that seemed to be better for a little while, but it seems to be getting problematic again. The server has remained up and all of the reliant services seem to be OK _MySQL, Apache, etc.) I think it is most likely a software issue. Perhaps there is an update we could do. It might be worth reaching out to them FYI -- the server is running in AWS and we have several other servers running within the same region (including the main wilkes.edu website), that have not had any of these issues. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Fri Jul 7 14:08:40 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Fri, 7 Jul 2023 14:08:40 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string In-Reply-To: References: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> Message-ID: Thanks, Blake! But did not work: > I, [2023-07-07T18:05:19.796951 #48893]? INFO -- : Thread-2002: > Connecting to database: > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&useSSL=false&AllowPublicKeyRetrieval=True*. > Max connections: 24 > E, [2023-07-07T18:05:20.542986 #48893] ERROR -- : Thread-2002: DB > connection failed: > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > *Public Key Retrieval is not allowed* Researching... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 12:23 PM, Blake Carver wrote: > Haven't seen that one before but it looks like a common error, adding > "AllowPublicKeyRetrieval=True?" to the connection string looks like > the answer > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Mark Cyzyk > *Sent:* Friday, July 7, 2023 12:06 PM > *To:* Archivesspace Users Group > > *Subject:* [Archivesspace_Users_Group] Staging upgrade using > Vagrant/Virtualbox, issue with DB connect string > All, > > I'm hoping to get some advice/another set of eyes on this: > > I am trying to stage an upgrade of Aspace here on my workstation using > Vagrant/Virtualbox and am running into an issue with the DB connect > string I'm using in my config.rb file. > > * > Preliminaries:* > > * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest > Additions installed > * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) > * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar > (owned by ?archivesspace" user) > * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) > > mysql> show databases; > -------------- > show databases > -------------- > > +--------------------+ > | Database?????????? | > +--------------------+ > | archivesspace????? | > | information_schema | > | mysql????????????? | > | performance_schema | > | sys??????????????? | > +--------------------+ > 5 rows in set (0.02 sec) > > > * Solr 8.10.0 > > Core > ??? startTime: > ??????? 6 minutes ago > ??? instanceDir: > ??????? /var/solr/data/archivesspace > ??? dataDir: > ??????? /var/solr/data/archivesspace/data/ > > > > > *The Problem:* > > Loading ArchivesSpace configuration file from path: > /usr/share/archivesspace/config/config.rb > > ArchivesSpaceThreadDump: Touch the file > '/usr/share/archivesspace/thread_dump_backend.txt' to trigger a > thread dump > I, [2023-07-07T15:32:08.607923 #52254]? INFO -- : Thread-2002: > Connecting to database: > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&**useSSL=false*. > Max connections: 24 > *E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB > connection failed: > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > Public Key Retrieval is not allowed* > ======================================================================== > ????? A trace file has been written to the following location: > /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt > > ????? This file contains information that will assist developers > in diagnosing > ????? problems with your ArchivesSpace installation.? Please > review the file's > ????? contents for sensitive information (such as passwords) that > you might not > ????? want to share. > ======================================================================== > Jul 07, 2023 3:32:08 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > INFO: An exception happened during JRuby-Rack startup > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > Public Key Retrieval is not allowed > --- System > jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server > VM 25.362-b09 on 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 +jit > [linux-x86_64] > Time: 2023-07-07 15:32:08 +0000 > Server: jetty/9.4.44.v20210927 > jruby.home: uri:classloader://META-INF/jruby.home > > > > *Notes:* > > Regarding my DB connect string: > > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false > > > I appended ?useSSL=false? thinking the following error would go away: > > ?E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB > connection failed: > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > Public Key Retrieval is not allowed > > > No joy! > > Not sure how to remedy.? Advice GREATLY appreciated, > > Mark > -- > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Fri Jul 7 15:27:03 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Fri, 7 Jul 2023 15:27:03 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string In-Reply-To: References: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> Message-ID: <0a9d37d5-4f98-c600-a66e-64df7ce4a347@gmail.com> FYI, here is the connect string that worked: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&allowPublicKeyRetrieval=true Now, though, I'm getting an error regarding Solr: RuntimeError: Solr checksum verification failed (schema): expected [4d4849771a91d677f255b638cbefa8b8d67a236c56c645bb13c2842480614d78] got [f066f17556bbe49b0526ff70ae885bdc9655666b503227667ef0c4315e4e5b0b] And this, despite the fact that I've placed the following in my config.rb: AppConfig[:solr_verify_checksums] = "false" Researching this... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 2:08 PM, Mark Cyzyk wrote: > Thanks, Blake! > > But did not work: > >> I, [2023-07-07T18:05:19.796951 #48893] INFO -- : Thread-2002: >> Connecting to database: >> jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&useSSL=false&AllowPublicKeyRetrieval=True*. >> Max connections: 24 >> E, [2023-07-07T18:05:20.542986 #48893] ERROR -- : Thread-2002: DB >> connection failed: >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: >> *Public Key Retrieval is not allowed* > > Researching... > > Mark > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > > On 7/7/23 12:23 PM, Blake Carver wrote: >> Haven't seen that one before but it looks like a common error, adding >> "AllowPublicKeyRetrieval=True?" to the connection string looks like >> the answer >> ------------------------------------------------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >> on behalf >> of Mark Cyzyk >> *Sent:* Friday, July 7, 2023 12:06 PM >> *To:* Archivesspace Users Group >> >> *Subject:* [Archivesspace_Users_Group] Staging upgrade using >> Vagrant/Virtualbox, issue with DB connect string >> All, >> >> I'm hoping to get some advice/another set of eyes on this: >> >> I am trying to stage an upgrade of Aspace here on my workstation >> using Vagrant/Virtualbox and am running into an issue with the DB >> connect string I'm using in my config.rb file. >> >> * >> Preliminaries:* >> >> * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest >> Additions installed >> * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) >> * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar >> (owned by ?archivesspace" user) >> * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) >> >> mysql> show databases; >> -------------- >> show databases >> -------------- >> >> +--------------------+ >> | Database?????????? | >> +--------------------+ >> | archivesspace????? | >> | information_schema | >> | mysql????????????? | >> | performance_schema | >> | sys??????????????? | >> +--------------------+ >> 5 rows in set (0.02 sec) >> >> >> * Solr 8.10.0 >> >> Core >> ??? startTime: >> ??????? 6 minutes ago >> ??? instanceDir: >> ??????? /var/solr/data/archivesspace >> ??? dataDir: >> ??????? /var/solr/data/archivesspace/data/ >> >> >> >> >> *The Problem:* >> >> Loading ArchivesSpace configuration file from path: >> /usr/share/archivesspace/config/config.rb >> >> ArchivesSpaceThreadDump: Touch the file >> '/usr/share/archivesspace/thread_dump_backend.txt' to trigger a >> thread dump >> I, [2023-07-07T15:32:08.607923 #52254]? INFO -- : Thread-2002: >> Connecting to database: >> jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&**useSSL=false*. >> Max connections: 24 >> *E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: >> DB connection failed: >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: >> Public Key Retrieval is not allowed* >> ======================================================================== >> ????? A trace file has been written to the following location: >> /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt >> >> ????? This file contains information that will assist developers >> in diagnosing >> ????? problems with your ArchivesSpace installation.? Please >> review the file's >> ????? contents for sensitive information (such as passwords) that >> you might not >> ????? want to share. >> ======================================================================== >> Jul 07, 2023 3:32:08 PM >> org.eclipse.jetty.server.handler.ContextHandler$Context log >> INFO: An exception happened during JRuby-Rack startup >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: >> Public Key Retrieval is not allowed >> --- System >> jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit >> Server VM 25.362-b09 on 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 >> +jit [linux-x86_64] >> Time: 2023-07-07 15:32:08 +0000 >> Server: jetty/9.4.44.v20210927 >> jruby.home: uri:classloader://META-INF/jruby.home >> >> >> >> *Notes:* >> >> Regarding my DB connect string: >> >> jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false >> >> >> I appended ?useSSL=false? thinking the following error would go away: >> >> ?E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: >> DB connection failed: >> Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: >> Public Key Retrieval is not allowed >> >> >> No joy! >> >> Not sure how to remedy.? Advice GREATLY appreciated, >> >> Mark >> -- >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.hoffman at lyrasis.org Fri Jul 7 15:48:32 2023 From: brian.hoffman at lyrasis.org (Brian Hoffman) Date: Fri, 7 Jul 2023 19:48:32 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string In-Reply-To: <0a9d37d5-4f98-c600-a66e-64df7ce4a347@gmail.com> References: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> <0a9d37d5-4f98-c600-a66e-64df7ce4a347@gmail.com> Message-ID: Hi Mark, Try removing the quotes around ?false?: AppConfig[:solr_verify_checksums] = false However, for production use you probably want to set this to true and work out the issue ? otherwise you will have runtime errors when the application tries to index a record with fields that don?t line up with Solr?s expectations. From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Date: Friday, July 7, 2023 at 3:27 PM To: Blake Carver , mcyzyk at jhu.edu , Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string FYI, here is the connect string that worked: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&allowPublicKeyRetrieval=true Now, though, I'm getting an error regarding Solr: RuntimeError: Solr checksum verification failed (schema): expected [4d4849771a91d677f255b638cbefa8b8d67a236c56c645bb13c2842480614d78] got [f066f17556bbe49b0526ff70ae885bdc9655666b503227667ef0c4315e4e5b0b] And this, despite the fact that I've placed the following in my config.rb: AppConfig[:solr_verify_checksums] = "false" Researching this... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 2:08 PM, Mark Cyzyk wrote: Thanks, Blake! But did not work: I, [2023-07-07T18:05:19.796951 #48893] INFO -- : Thread-2002: Connecting to database: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&AllowPublicKeyRetrieval=True. Max connections: 24 E, [2023-07-07T18:05:20.542986 #48893] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed Researching... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 12:23 PM, Blake Carver wrote: Haven't seen that one before but it looks like a common error, adding "AllowPublicKeyRetrieval=True " to the connection string looks like the answer ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Friday, July 7, 2023 12:06 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string All, I'm hoping to get some advice/another set of eyes on this: I am trying to stage an upgrade of Aspace here on my workstation using Vagrant/Virtualbox and am running into an issue with the DB connect string I'm using in my config.rb file. Preliminaries: * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest Additions installed * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar (owned by ?archivesspace" user) * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) mysql> show databases; -------------- show databases -------------- +--------------------+ | Database | +--------------------+ | archivesspace | | information_schema | | mysql | | performance_schema | | sys | +--------------------+ 5 rows in set (0.02 sec) * Solr 8.10.0 Core startTime: 6 minutes ago instanceDir: /var/solr/data/archivesspace dataDir: /var/solr/data/archivesspace/data/ The Problem: Loading ArchivesSpace configuration file from path: /usr/share/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/share/archivesspace/thread_dump_backend.txt' to trigger a thread dump I, [2023-07-07T15:32:08.607923 #52254] INFO -- : Thread-2002: Connecting to database: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false. Max connections: 24 E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed ======================================================================== A trace file has been written to the following location: /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt This file contains information that will assist developers in diagnosing problems with your ArchivesSpace installation. Please review the file's contents for sensitive information (such as passwords) that you might not want to share. ======================================================================== Jul 07, 2023 3:32:08 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.362-b09 on 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 +jit [linux-x86_64] Time: 2023-07-07 15:32:08 +0000 Server: jetty/9.4.44.v20210927 jruby.home: uri:classloader://META-INF/jruby.home Notes: Regarding my DB connect string: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false I appended ?useSSL=false? thinking the following error would go away: E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed No joy! Not sure how to remedy. Advice GREATLY appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddonizio at atlas-sys.com Fri Jul 7 15:49:57 2023 From: vaddonizio at atlas-sys.com (Valerie Addonizio) Date: Fri, 7 Jul 2023 19:49:57 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string In-Reply-To: <0a9d37d5-4f98-c600-a66e-64df7ce4a347@gmail.com> References: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> <0a9d37d5-4f98-c600-a66e-64df7ce4a347@gmail.com> Message-ID: Mark, I just tackled that issue this morning but am not sure my solution would work for you. I was trying to update 2.8.1 data in a 3.4.0 docker install. I was getting that same error with this order of events: launch db, restore data into db, launch ASpace I did not get that error if I switched the order of events: launch db, launch ASpace, take ASpace down, restore data into db, launch Aspace From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Mark Cyzyk Sent: Friday, July 7, 2023 3:27 PM To: Blake Carver ; mcyzyk at jhu.edu; Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string FYI, here is the connect string that worked: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&allowPublicKeyRetrieval=true Now, though, I'm getting an error regarding Solr: RuntimeError: Solr checksum verification failed (schema): expected [4d4849771a91d677f255b638cbefa8b8d67a236c56c645bb13c2842480614d78] got [f066f17556bbe49b0526ff70ae885bdc9655666b503227667ef0c4315e4e5b0b] And this, despite the fact that I've placed the following in my config.rb: AppConfig[:solr_verify_checksums] = "false" Researching this... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 2:08 PM, Mark Cyzyk wrote: Thanks, Blake! But did not work: I, [2023-07-07T18:05:19.796951 #48893] INFO -- : Thread-2002: Connecting to database: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&AllowPublicKeyRetrieval=True. Max connections: 24 E, [2023-07-07T18:05:20.542986 #48893] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed Researching... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 12:23 PM, Blake Carver wrote: Haven't seen that one before but it looks like a common error, adding "AllowPublicKeyRetrieval=True " to the connection string looks like the answer ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Friday, July 7, 2023 12:06 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string All, I'm hoping to get some advice/another set of eyes on this: I am trying to stage an upgrade of Aspace here on my workstation using Vagrant/Virtualbox and am running into an issue with the DB connect string I'm using in my config.rb file. Preliminaries: * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest Additions installed * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar (owned by ?archivesspace" user) * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) mysql> show databases; -------------- show databases -------------- +--------------------+ | Database | +--------------------+ | archivesspace | | information_schema | | mysql | | performance_schema | | sys | +--------------------+ 5 rows in set (0.02 sec) * Solr 8.10.0 Core startTime: 6 minutes ago instanceDir: /var/solr/data/archivesspace dataDir: /var/solr/data/archivesspace/data/ The Problem: Loading ArchivesSpace configuration file from path: /usr/share/archivesspace/config/config.rb ArchivesSpaceThreadDump: Touch the file '/usr/share/archivesspace/thread_dump_backend.txt' to trigger a thread dump I, [2023-07-07T15:32:08.607923 #52254] INFO -- : Thread-2002: Connecting to database: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false. Max connections: 24 E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed ======================================================================== A trace file has been written to the following location: /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt This file contains information that will assist developers in diagnosing problems with your ArchivesSpace installation. Please review the file's contents for sensitive information (such as passwords) that you might not want to share. ======================================================================== Jul 07, 2023 3:32:08 PM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed --- System jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.362-b09 on 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 +jit [linux-x86_64] Time: 2023-07-07 15:32:08 +0000 Server: jetty/9.4.44.v20210927 jruby.home: uri:classloader://META-INF/jruby.home Notes: Regarding my DB connect string: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false I appended ?useSSL=false? thinking the following error would go away: E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : Thread-2002: DB connection failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: Public Key Retrieval is not allowed No joy! Not sure how to remedy. Advice GREATLY appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Fri Jul 7 16:19:24 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Fri, 7 Jul 2023 16:19:24 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, issue with DB connect string In-Reply-To: References: <53fb8bc5-f62e-2398-25a3-aef2813b781b@gmail.com> <0a9d37d5-4f98-c600-a66e-64df7ce4a347@gmail.com> Message-ID: <634b352d-8e34-cb67-022c-75b3a0a75131@gmail.com> Thanks, Blake, Brian, Valerie, The connect string that worked: jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&allowPublicKeyRetrieval=true And the setting in my config.rb that did the trick, overriding Solr checksum checking: AppConfig[:solr_verify_checksums] = false ASpace running in Vagrant on my workstation now. Spinning in chair! Appreciatively, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu On 7/7/23 3:49 PM, Valerie Addonizio wrote: > > Mark, > > I just tackled that issue this morning but am not sure my solution > would work for you. > > I was trying to update 2.8.1 data in a 3.4.0 docker install. > > I was getting that same error with this order of events: launch db, > restore data into db, launch ASpace > > I did not get that error if I switched the order of events: launch db, > launch ASpace, take ASpace down, restore data into db, launch Aspace > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > *On Behalf > Of *Mark Cyzyk > *Sent:* Friday, July 7, 2023 3:27 PM > *To:* Blake Carver ; mcyzyk at jhu.edu; > Archivesspace Users Group > > *Subject:* Re: [Archivesspace_Users_Group] Staging upgrade using > Vagrant/Virtualbox, issue with DB connect string > > > FYI, here is the connect string that worked: > > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false&allowPublicKeyRetrieval=true > > > Now, though, I'm getting an error regarding Solr: > > RuntimeError: Solr checksum verification failed (schema): expected > [4d4849771a91d677f255b638cbefa8b8d67a236c56c645bb13c2842480614d78] > got [f066f17556bbe49b0526ff70ae885bdc9655666b503227667ef0c4315e4e5b0b] > > > And this, despite the fact that I've placed the following in my config.rb: > > AppConfig[:solr_verify_checksums] = "false" > > > Researching this... > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > On 7/7/23 2:08 PM, Mark Cyzyk wrote: > > Thanks, Blake! > > But did not work: > > > I, [2023-07-07T18:05:19.796951 #48893] INFO -- : Thread-2002: > Connecting to database: > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&useSSL=false&AllowPublicKeyRetrieval=True*. > Max connections: 24 > E, [2023-07-07T18:05:20.542986 #48893] ERROR -- : Thread-2002: > DB connection failed: > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > *Public Key Retrieval is not allowed* > > > Researching... > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > > Mark Cyzyk, M.A., M.L.S. > > Library Applications Group > > The Sheridan Libraries > > The Johns Hopkins University > > mcyzyk at jhu.edu > > On 7/7/23 12:23 PM, Blake Carver wrote: > > Haven't seen that one before but it looks like a common error, > adding "AllowPublicKeyRetrieval=True?" to the connection > string looks like the answer > > ------------------------------------------------------------------------ > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > on > behalf of Mark Cyzyk > *Sent:* Friday, July 7, 2023 12:06 PM > *To:* Archivesspace Users Group > > > *Subject:* [Archivesspace_Users_Group] Staging upgrade using > Vagrant/Virtualbox, issue with DB connect string > > All, > > I'm hoping to get some advice/another set of eyes on this: > > I am trying to stage an upgrade of Aspace here on my > workstation using Vagrant/Virtualbox and am running into an > issue with the DB connect string I'm using in my config.rb file. > > * > Preliminaries:* > > * Ubuntu 20.04 Jammy on Vagrant/Oracle Virtualbox with Guest > Additions installed > * Archivesspace 3.2.0 (preparing to upgrade to 3.4.0) > * /usr/share/archivesspace/lib/mysql-connector-java-5.1.49.jar > (owned by ?archivesspace" user) > * MySQL 8.0.33-0ubuntu0.20.04.2 (Ubuntu) > > mysql> show databases; > -------------- > show databases > -------------- > > +--------------------+ > | Database?????????? | > +--------------------+ > | archivesspace????? | > | information_schema | > | mysql????????????? | > | performance_schema | > | sys??????????????? | > +--------------------+ > 5 rows in set (0.02 sec) > > * Solr 8.10.0 > > Core > ??? startTime: > ??????? 6 minutes ago > ??? instanceDir: > ??????? /var/solr/data/archivesspace > ??? dataDir: > ??????? /var/solr/data/archivesspace/data/ > > > > > *The Problem:* > > Loading ArchivesSpace configuration file from path: > /usr/share/archivesspace/config/config.rb > > ArchivesSpaceThreadDump: Touch the file > '/usr/share/archivesspace/thread_dump_backend.txt' to > trigger a thread dump > I, [2023-07-07T15:32:08.607923 #52254]? INFO -- : > Thread-2002: Connecting to database: > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8*&useSSL=false*. > Max connections: 24 > *E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : > Thread-2002: DB connection failed: > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > Public Key Retrieval is not allowed* > ======================================================================== > ????? A trace file has been written to the following > location: > /usr/share/archivesspace/data/tmp/aspace_diagnostic_1688743928.txt > > ????? This file contains information that will assist > developers in diagnosing > ????? problems with your ArchivesSpace installation. > Please review the file's > ????? contents for sensitive information (such as > passwords) that you might not > ????? want to share. > ======================================================================== > Jul 07, 2023 3:32:08 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > INFO: An exception happened during JRuby-Rack startup > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > Public Key Retrieval is not allowed > --- System > jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK > 64-Bit Server VM 25.362-b09 on > 1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09 +jit [linux-x86_64] > Time: 2023-07-07 15:32:08 +0000 > Server: jetty/9.4.44.v20210927 > jruby.home: uri:classloader://META-INF/jruby.home > > > > *Notes:* > > Regarding my DB connect string: > > jdbc:mysql://localhost:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&useSSL=false > > > I appended ?useSSL=false? thinking the following error would > go away: > > ?E, [2023-07-07T15:32:08.914823 #52254] ERROR -- : > Thread-2002: DB connection failed: > Java::ComMysqlJdbcExceptionsJdbc4::MySQLNonTransientConnectionException: > Public Key Retrieval is not allowed > > > No joy! > > Not sure how to remedy.? Advice GREATLY appreciated, > > Mark > > -- > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > > Mark Cyzyk, M.A., M.L.S. > > Library Applications Group > > The Sheridan Libraries > > The Johns Hopkins University > > mcyzyk at jhu.edu > > Verba volant, scripta manent. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Sun Jul 9 11:04:38 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Sun, 9 Jul 2023 11:04:38 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application Message-ID: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> All, Another puzzler: As I continue to build a staging version of ASpace in Vagrant/Virtualbox, in the end I am seeing data in the MySQL tables, a Solr core present, I've reindexed overnight -- and yet there are No Records Found in the ASpace Web interface itself. I feel like I'm missing a step here, but it seems like with codebase present, and a Restore of my SQL dump into MySQL, and a Solr core present to take indexing data, and with the ASpace Web app up and running without error, I should have a fully functioning ASpace. Functioning, but no data! Researching....? But advice appreciated! Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. From andrew.morrison at bodleian.ox.ac.uk Mon Jul 10 05:52:22 2023 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 10 Jul 2023 10:52:22 +0100 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> Message-ID: Is the Solr core's name the same as the one inside the AppConfig[:solr_url] value? And have you reloaded the Solr core? You can script the latter by sending a GET request to: http://___solr_server___:8983/solr/admin/cores?action=RELOAD&core=___name_of_core___ Or you can do it manually via the Solr management interface. Andrew. On 09/07/2023 16:04, Mark Cyzyk wrote: > > All, > > Another puzzler: > > As I continue to build a staging version of ASpace in > Vagrant/Virtualbox, in the end I am seeing data in the MySQL tables, a > Solr core present, I've reindexed overnight -- and yet there are No > Records Found in the ASpace Web interface itself. > > I feel like I'm missing a step here, but it seems like with codebase > present, and a Restore of my SQL dump into MySQL, and a Solr core > present to take indexing data, and with the ASpace Web app up and > running without error, I should have a fully functioning ASpace. > > Functioning, but no data! > > Researching....? But advice appreciated! > > Mark > From Corey.Schmidt at uga.edu Tue Jul 11 09:18:51 2023 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Tue, 11 Jul 2023 13:18:51 +0000 Subject: [Archivesspace_Users_Group] Group Level Permissions for Bulk Edit Plugin Message-ID: Dear all, For those who made/run the ASpace Spreadsheet Bulk Updater plugin made for The New School, what group level is required to run the bulk updater? We're considering installing this plugin but we're not sure what group level in ArchivesSpace is minimally required. I'm thinking it's editing a resource record, perhaps found here: https://github.com/hudmol/as_spreadsheet_bulk_updater/blob/8b772e7598b5ef6a14b32a52852c0db44b8d6399/backend/model/spreadsheet_bulk_update_job.rb#L4 Would that mean any group with "create/update resources in this repository" and "create and run a background job" permissions can run the plugin? Are there other permissions required? Any help/info is appreciated, thanks! Sincerely, Corey Corey Schmidt Special Collections Libraries | Project Management Librarian/Archivist 300 S Hull St | Athens, GA 30605 Corey.Schmidt at uga.edu [University of Georgia] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8920 bytes Desc: image001.png URL: From mcyzyk at gmail.com Tue Jul 11 11:47:12 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Tue, 11 Jul 2023 11:47:12 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> Message-ID: <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> A Clue! Solr with Archivesspace Core present, Aspace indexing going going going. But I look at the Solr config and see this: > > Core > > * > > startTime: > about 3 hours ago > > * > > instanceDir: > /var/solr/data/archivesspace > > * > > dataDir: > /var/solr/data/archivesspace/data/ > > > Index > > * > > lastModified: > - > > * > > version: > 2 > > * > > numDocs: > 0 > > * > > maxDoc: > 0 > > * > > deletedDocs: > 0 > > * > > current: > > * > > directory: > org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/archivesspace/data/index > lockFactory=org.apache.lucene.store.NativeFSLockFactory at 782702f4; > maxCacheMB=48.0 maxMergeSizeMB=4.0) > Zero documents! Wondering where all this indexing is going...? No errors. Researching.... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/9/23 11:04, Mark Cyzyk wrote: > > All, > > Another puzzler: > > As I continue to build a staging version of ASpace in > Vagrant/Virtualbox, in the end I am seeing data in the MySQL tables, a > Solr core present, I've reindexed overnight -- and yet there are No > Records Found in the ASpace Web interface itself. > > I feel like I'm missing a step here, but it seems like with codebase > present, and a Restore of my SQL dump into MySQL, and a Solr core > present to take indexing data, and with the ASpace Web app up and > running without error, I should have a fully functioning ASpace. > > Functioning, but no data! > > Researching....? But advice appreciated! > > Mark > -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Tue Jul 11 20:23:03 2023 From: james at hudmol.com (James Bullen) Date: Wed, 12 Jul 2023 10:23:03 +1000 Subject: [Archivesspace_Users_Group] Group Level Permissions for Bulk Edit Plugin In-Reply-To: References: Message-ID: Hi Corey, Yes, you need to be in a group with update_resource_record (create/update resources in this repository) and create_job (create and run a background job) to run the job. You can download the spreadsheet with just view_repository (view the records in this repository). Cheers, James ? James Bullen Director/Developer Hudson Molonglo ? > On Jul 11, 2023, at 11:18 PM, Corey Schmidt wrote: > > Dear all, > > For those who made/run the ASpace Spreadsheet Bulk Updater plugin made for The New School, what group level is required to run the bulk updater? > > We're considering installing this plugin but we're not sure what group level in ArchivesSpace is minimally required. I'm thinking it's editing a resource record, perhaps found here:https://github.com/hudmol/as_spreadsheet_bulk_updater/blob/8b772e7598b5ef6a14b32a52852c0db44b8d6399/backend/model/spreadsheet_bulk_update_job.rb#L4 > > Would that mean any group with "create/update resources in this repository" and ?create and run a background job? permissions can run the plugin? Are there other permissions required? > > Any help/info is appreciated, thanks! > > Sincerely, > > Corey > Corey Schmidt > Special Collections Libraries | Project Management Librarian/Archivist > > 300 S Hull St | Athens, GA 30605 > Corey.Schmidt at uga.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Jul 12 07:53:14 2023 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 12 Jul 2023 11:53:14 +0000 Subject: [Archivesspace_Users_Group] Group Level Permissions for Bulk Edit Plugin In-Reply-To: References: Message-ID: Hey James, Awesome, thanks so much! Corey From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of James Bullen Sent: Tuesday, July 11, 2023 8:23 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Group Level Permissions for Bulk Edit Plugin [EXTERNAL SENDER - PROCEED CAUTIOUSLY] Hi Corey, Yes, you need to be in a group with update_resource_record (create/update resources in this repository) and create_job (create and run a background job) to run the job. You can download the spreadsheet with just view_repository (view the records in this repository). Cheers, James ? James Bullen Director/Developer Hudson Molonglo ? On Jul 11, 2023, at 11:18 PM, Corey Schmidt > wrote: Dear all, For those who made/run the ASpace Spreadsheet Bulk Updater plugin made for The New School, what group level is required to run the bulk updater? We're considering installing this plugin but we're not sure what group level in ArchivesSpace is minimally required. I'm thinking it's editing a resource record, perhaps found here:https://github.com/hudmol/as_spreadsheet_bulk_updater/blob/8b772e7598b5ef6a14b32a52852c0db44b8d6399/backend/model/spreadsheet_bulk_update_job.rb#L4 Would that mean any group with "create/update resources in this repository" and ?create and run a background job? permissions can run the plugin? Are there other permissions required? Any help/info is appreciated, thanks! Sincerely, Corey Corey Schmidt Special Collections Libraries | Project Management Librarian/Archivist 300 S Hull St | Athens, GA 30605 Corey.Schmidt at uga.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Wed Jul 12 09:28:05 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Wed, 12 Jul 2023 09:28:05 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: More, from the log: I, [2023-07-12T13:22:30.618347 #4611]? INFO -- : Thread-2956: Staff Indexer [2023-07-12 13:22:30 +0000] Running index round I, [2023-07-12T13:22:32.215842 #4611]? INFO -- : Thread-2956: Staff Indexer [2023-07-12 13:22:32 +0000] Index round complete I, [2023-07-12T13:22:56.046694 #4611]? INFO -- : Thread-3306: PUI Indexer [2023-07-12 13:22:56 +0000] Running index round I, [2023-07-12T13:22:57.479284 #4611]? INFO -- : Thread-3306: PUI Indexer [2023-07-12 13:22:57 +0000] Index round complete I'm sensing that those "+0000" should be actual numbers of records indexed. Not sure why it successfully starts an indexing round, and successfully completes an indexing round, if 0 records are added to Solr. Searching, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/11/23 11:47, Mark Cyzyk wrote: > A Clue! > > Solr with Archivesspace Core present, Aspace indexing going going going. > > But I look at the Solr config and see this: > >> >> Core >> >> * >> >> startTime: >> about 3 hours ago >> >> * >> >> instanceDir: >> /var/solr/data/archivesspace >> >> * >> >> dataDir: >> /var/solr/data/archivesspace/data/ >> >> >> Index >> >> * >> >> lastModified: >> - >> >> * >> >> version: >> 2 >> >> * >> >> numDocs: >> 0 >> >> * >> >> maxDoc: >> 0 >> >> * >> >> deletedDocs: >> 0 >> >> * >> >> current: >> >> * >> >> directory: >> org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/archivesspace/data/index >> lockFactory=org.apache.lucene.store.NativeFSLockFactory at 782702f4; >> maxCacheMB=48.0 maxMergeSizeMB=4.0) >> > > Zero documents! > > Wondering where all this indexing is going...? No errors. Researching.... > > Mark > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 7/9/23 11:04, Mark Cyzyk wrote: >> >> All, >> >> Another puzzler: >> >> As I continue to build a staging version of ASpace in >> Vagrant/Virtualbox, in the end I am seeing data in the MySQL tables, >> a Solr core present, I've reindexed overnight -- and yet there are No >> Records Found in the ASpace Web interface itself. >> >> I feel like I'm missing a step here, but it seems like with codebase >> present, and a Restore of my SQL dump into MySQL, and a Solr core >> present to take indexing data, and with the ASpace Web app up and >> running without error, I should have a fully functioning ASpace. >> >> Functioning, but no data! >> >> Researching....? But advice appreciated! >> >> Mark >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Jul 12 09:39:58 2023 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 12 Jul 2023 13:39:58 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Do you have the solr_url set correctly? https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L38-L40 You don't have "enable_solr" in your config file do you? You're tried restarting both Solr and ArchivesSpace ? What's in the Solr server logs? /var/solr/server/solr/configsets/archivesspace/conf You have the correct files in there? (I think that's the right path, maybe wrong on that) /var/solr/data/archivesspace/data/ That directory is just empty? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Wednesday, July 12, 2023 9:28 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application More, from the log: I, [2023-07-12T13:22:30.618347 #4611] INFO -- : Thread-2956: Staff Indexer [2023-07-12 13:22:30 +0000] Running index round I, [2023-07-12T13:22:32.215842 #4611] INFO -- : Thread-2956: Staff Indexer [2023-07-12 13:22:32 +0000] Index round complete I, [2023-07-12T13:22:56.046694 #4611] INFO -- : Thread-3306: PUI Indexer [2023-07-12 13:22:56 +0000] Running index round I, [2023-07-12T13:22:57.479284 #4611] INFO -- : Thread-3306: PUI Indexer [2023-07-12 13:22:57 +0000] Index round complete I'm sensing that those "+0000" should be actual numbers of records indexed. Not sure why it successfully starts an indexing round, and successfully completes an indexing round, if 0 records are added to Solr. Searching, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/11/23 11:47, Mark Cyzyk wrote: A Clue! Solr with Archivesspace Core present, Aspace indexing going going going. But I look at the Solr config and see this: Core * startTime: about 3 hours ago * instanceDir: /var/solr/data/archivesspace * dataDir: /var/solr/data/archivesspace/data/ Index * lastModified: - * version: 2 * numDocs: 0 * maxDoc: 0 * deletedDocs: 0 * current: * directory: org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/archivesspace/data/index lockFactory=org.apache.lucene.store.NativeFSLockFactory at 782702f4; maxCacheMB=48.0 maxMergeSizeMB=4.0) Zero documents! Wondering where all this indexing is going... No errors. Researching.... Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/9/23 11:04, Mark Cyzyk wrote: All, Another puzzler: As I continue to build a staging version of ASpace in Vagrant/Virtualbox, in the end I am seeing data in the MySQL tables, a Solr core present, I've reindexed overnight -- and yet there are No Records Found in the ASpace Web interface itself. I feel like I'm missing a step here, but it seems like with codebase present, and a Restore of my SQL dump into MySQL, and a Solr core present to take indexing data, and with the ASpace Web app up and running without error, I should have a fully functioning ASpace. Functioning, but no data! Researching.... But advice appreciated! Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse.martinez at bc.edu Wed Jul 12 09:52:51 2023 From: jesse.martinez at bc.edu (Jesse Martinez) Date: Wed, 12 Jul 2023 09:52:51 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Hi Mark, Can you share the output of this command? This will give some clues on how your solr instance is configured. ps aux | grep solr | grep -v grep Jesse On Wed, Jul 12, 2023 at 9:40?AM Blake Carver wrote: > Do you have the solr_url set correctly? > > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L38-L40 > > You don't have "enable_solr" in your config file do you? > > You're tried restarting both Solr and ArchivesSpace ? > > What's in the Solr server logs? > > /var/solr/server/solr/configsets/archivesspace/conf > You have the correct files in there? (I think that's the right path, maybe > wrong on that) > > /var/solr/data/archivesspace/data/ > That directory is just empty? > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Mark Cyzyk > *Sent:* Wednesday, July 12, 2023 9:28 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Staging upgrade using > Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet > no data displayed in ASpace application > > > More, from the log: > > I, [2023-07-12T13:22:30.618347 #4611] INFO -- : Thread-2956: Staff > Indexer [2023-07-12 13:22:30 +0000] Running index round > I, [2023-07-12T13:22:32.215842 #4611] INFO -- : Thread-2956: Staff > Indexer [2023-07-12 13:22:32 +0000] Index round complete > I, [2023-07-12T13:22:56.046694 #4611] INFO -- : Thread-3306: PUI Indexer > [2023-07-12 13:22:56 +0000] Running index round > I, [2023-07-12T13:22:57.479284 #4611] INFO -- : Thread-3306: PUI Indexer > [2023-07-12 13:22:57 +0000] Index round complete > > > I'm sensing that those "+0000" should be actual numbers of records > indexed. > > Not sure why it successfully starts an indexing round, and successfully > completes an indexing round, if 0 records are added to Solr. > > Searching, > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins Universitymcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/11/23 11:47, Mark Cyzyk wrote: > > A Clue! > > Solr with Archivesspace Core present, Aspace indexing going going going. > > But I look at the Solr config and see this: > > Core > > - startTime: about 3 hours ago > - instanceDir: /var/solr/data/archivesspace > - dataDir: /var/solr/data/archivesspace/data/ > > Index > > - lastModified: - > - version: 2 > - numDocs: 0 > - maxDoc: 0 > - deletedDocs: 0 > - current: > - directory: > org.apache.lucene.store.NRTCachingDirectory:NRTCachingDirectory(MMapDirectory@/var/solr/data/archivesspace/data/index > lockFactory=org.apache.lucene.store.NativeFSLockFactory at 782702f4; > maxCacheMB=48.0 maxMergeSizeMB=4.0) > > > Zero documents! > > Wondering where all this indexing is going... No errors. Researching.... > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins Universitymcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/9/23 11:04, Mark Cyzyk wrote: > > > All, > > Another puzzler: > > As I continue to build a staging version of ASpace in Vagrant/Virtualbox, > in the end I am seeing data in the MySQL tables, a Solr core present, I've > reindexed overnight -- and yet there are No Records Found in the ASpace Web > interface itself. > > I feel like I'm missing a step here, but it seems like with codebase > present, and a Restore of my SQL dump into MySQL, and a Solr core present > to take indexing data, and with the ASpace Web app up and running without > error, I should have a fully functioning ASpace. > > Functioning, but no data! > > Researching.... But advice appreciated! > > Mark > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Wed Jul 12 10:01:05 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Wed, 12 Jul 2023 10:01:05 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: <2b088dd1-62cb-c35f-fada-db89d254695c@gmail.com> Thanks, Blake, > Do you have the solr_url set correctly? > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L38-L40 Yes, http://localhost:8983/solr/#/~cores/archivesspace > > You don't have "enable_solr" in your config file do you? I /do/ have that: # Setting any of the keys below to false will prevent the associated # applications from starting. Temporarily disabling the frontend and public # UIs and/or the indexer may help users who are running into memory-related # issues during migration. AppConfig[:enable_backend] = true AppConfig[:enable_frontend] = true AppConfig[:enable_public] = true AppConfig[:enable_solr] = true AppConfig[:enable_indexer] = true AppConfig[:enable_docs] = true AppConfig[:enable_oai] = true > > You're tried restarting both Solr and ArchivesSpace ? Yes, I have done that. > > What's in the Solr server logs? I do not see any Solr log in /var/log: vagrant at vagrant:/var/log$ ls alternatives.log?????? dmesg.0???????? kern.log.1?? syslog.4.gz apt??????????????????? dmesg.1.gz????? landscape ubuntu-advantage.log auth.log?????????????? dmesg.2.gz????? lastlog ubuntu-advantage-timer.log auth.log.1???????????? dpkg.log??????? mysql vboxadd-setup.log bootstrap.log????????? faillog???????? private vboxadd-setup.log.1 btmp?????????????????? fontconfig.log? syslog vboxadd-setup.log.2 cloud-init.log???????? installer?????? syslog.1???? wtmp cloud-init-output.log? journal???????? syslog.2.gz dmesg????????????????? kern.log??????? syslog.3.gz > > /var/solr/server/solr/configsets/archivesspace/conf > You have the correct files in there? (I think that's the right path, > maybe wrong on that) ls -la /var/solr/data/archivesspace/conf total 32 drwxrwxr-x 2 solr solr? 4096 Jul? 8 15:05 . drwxrwxr-x 4 solr solr? 4096 Jul? 8 15:05 .. -rw-r--r-- 1 solr solr 18747 Jul? 8 15:05 schema.xml -rw-r--r-- 1 solr solr? 3046 Jul? 8 15:05 solrconfig.xml -rw-r--r-- 1 solr solr???? 0 Jul? 8 15:05 stopwords.txt -rw-r--r-- 1 solr solr???? 0 Jul? 8 15:05 synonyms.txt > > /var/solr/data/archivesspace/data/ > That directory is just empty? ls -la /var/solr/data/archivesspace/data/index total 12 drwxrwxr-x 2 solr solr 4096 Jul? 8 15:05 . drwxrwxr-x 4 solr solr 4096 Jul? 8 15:05 .. -rw-rw-r-- 1 solr solr?? 69 Jul? 8 15:05 segments_1 -rw-rw-r-- 1 solr solr??? 0 Jul? 8 15:05 write.lock Ah ha!? Should that "write.lock" file be there? Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 09:39, Blake Carver wrote: > Do you have the solr_url set correctly? > https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L38-L40 > > You don't have "enable_solr" in your config file do you? > > You're tried restarting both Solr and ArchivesSpace ? > > What's in the Solr server logs? > > /var/solr/server/solr/configsets/archivesspace/conf > You have the correct files in there? (I think that's the right path, > maybe wrong on that) > > /var/solr/data/archivesspace/data/ > That directory is just empty? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Wed Jul 12 10:05:51 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Wed, 12 Jul 2023 10:05:51 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Thanks, Jesse, Here is the output of those commands: ps aux | grep solr | grep -v grep solr???????? 898? 0.0? 0.1? 19096? 9812 ???????? Ss?? Jul11?? 0:00 /lib/systemd/systemd --user solr???????? 910? 0.0? 0.0 169492? 3368 ???????? S??? Jul11?? 0:00 (sd-pam) solr??????? 1223? 0.5 12.5 4018692 742508 ?????? Sl?? Jul11?? 7:41 java -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= -Dsolr.install.dir=/opt/solr -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip Puzzling! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 09:52, Jesse Martinez wrote: > ps aux | grep solr | grep -v grep -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesse.martinez at bc.edu Wed Jul 12 10:09:08 2023 From: jesse.martinez at bc.edu (Jesse Martinez) Date: Wed, 12 Jul 2023 10:09:08 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Thanks for sharing that, Mark! I have another quick follow up question. What do you see when you run a solr search like this one: http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true You should see all your indexed records. But if you don't see any results then it may indicate that your archivesspace configuration directory is not correct. Jesse On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk wrote: > > Thanks, Jesse, > > Here is the output of those commands: > > ps aux | grep solr | grep -v grep > solr 898 0.0 0.1 19096 9812 ? Ss Jul11 0:00 > /lib/systemd/systemd --user > solr 910 0.0 0.0 169492 3368 ? S Jul11 0:00 (sd-pam) > solr 1223 0.5 12.5 4018692 742508 ? Sl Jul11 7:41 java > -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem > -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages > -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -verbose:gc > -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps > -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution > -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log > -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M > -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= > -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 > -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow > -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs > -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data > -Dsolr.data.home= -Dsolr.install.dir=/opt/solr > -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf > -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k > -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip > > Puzzling! > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins Universitymcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/12/23 09:52, Jesse Martinez wrote: > > ps aux | grep solr | grep -v grep > > > -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Jul 12 10:15:14 2023 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 12 Jul 2023 14:15:14 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: That's probably the problem, get rid of that: AppConfig[:enable_solr] = true ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Jesse Martinez Sent: Wednesday, July 12, 2023 10:09 AM To: mcyzyk at jhu.edu Cc: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application Thanks for sharing that, Mark! I have another quick follow up question. What do you see when you run a solr search like this one: http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true You should see all your indexed records. But if you don't see any results then it may indicate that your archivesspace configuration directory is not correct. Jesse On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk > wrote: Thanks, Jesse, Here is the output of those commands: ps aux | grep solr | grep -v grep solr 898 0.0 0.1 19096 9812 ? Ss Jul11 0:00 /lib/systemd/systemd --user solr 910 0.0 0.0 169492 3368 ? S Jul11 0:00 (sd-pam) solr 1223 0.5 12.5 4018692 742508 ? Sl Jul11 7:41 java -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= -Dsolr.install.dir=/opt/solr -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip Puzzling! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 09:52, Jesse Martinez wrote: ps aux | grep solr | grep -v grep -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Wed Jul 12 10:19:40 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Wed, 12 Jul 2023 10:19:40 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Darn: > |{ "responseHeader":{ "status":0, "QTime":187, "params":{ "q":"*:*", > "indent":"true", "q.op":"OR", "_":"1689171084647"}}, > "response":{"numFound":0,"start":0,"numFoundExact":true,"docs":[] }}| I will look more carefully at my Solr Aspace config (and yet the steps in my Vagrant file for setting this up are the same as last summer when I did this!). Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 10:09, Jesse Martinez wrote: > Thanks for sharing that, Mark! > > I have another quick follow up question. > > What do you see when you run a solr search like this one: > > http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true > > > You should?see all your indexed records. But if you don't see any > results then it may indicate that your archivesspace configuration > directory is not correct. > > Jesse > > On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk wrote: > > > Thanks, Jesse, > > Here is the output of those commands: > > ps aux | grep solr | grep -v grep > solr???????? 898? 0.0? 0.1? 19096? 9812 ???????? Ss Jul11?? > 0:00 /lib/systemd/systemd --user > solr???????? 910? 0.0? 0.0 169492? 3368 ???????? S Jul11?? > 0:00 (sd-pam) > solr??????? 1223? 0.5 12.5 4018692 742508 ?????? Sl Jul11?? > 7:41 java -server -Xms512m -Xmx512m -XX:+UseG1GC > -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled > -XX:MaxGCPauseMillis=250 -XX:+UseLargePages > -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent > -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails > -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -XX:+PrintTenuringDistribution > -XX:+PrintGCApplicationStoppedTime > -Xloggc:/var/solr/logs/solr_gc.log -XX:+UseGCLogFileRotation > -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M > -Dsolr.jetty.inetaccess.includes= > -Dsolr.jetty.inetaccess.excludes= > -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 > -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC > -XX:-OmitStackTraceInFastThrow > -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 > /var/solr/logs -Djetty.home=/opt/solr/server > -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= > -Dsolr.install.dir=/opt/solr > -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf > -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k > -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip > > Puzzling! > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/12/23 09:52, Jesse Martinez wrote: >> ps aux | grep solr | grep -v grep > > > > -- > Jesse Martinez > Senior Library Applications Developer > O'Neill Library, Boston College > jesse.martinez at bc.edu > 617-552-2509 > he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.hoffman at lyrasis.org Wed Jul 12 10:24:47 2023 From: brian.hoffman at lyrasis.org (Brian Hoffman) Date: Wed, 12 Jul 2023 14:24:47 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Hi Mark, I believe you have incorrectly set the solr url to a screen on the control panel. Try replacing: http://localhost:8983/solr/#/~cores/archivesspace with http://localhost:8983/solr/archivesspace From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Date: Wednesday, July 12, 2023 at 10:19 AM To: jesse.martinez at bc.edu , mcyzyk at jhu.edu Cc: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application Darn: { "responseHeader":{ "status":0, "QTime":187, "params":{ "q":"*:*", "indent":"true", "q.op":"OR", "_":"1689171084647"}}, "response":{"numFound":0,"start":0,"numFoundExact":true,"docs":[] }} I will look more carefully at my Solr Aspace config (and yet the steps in my Vagrant file for setting this up are the same as last summer when I did this!). Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 10:09, Jesse Martinez wrote: Thanks for sharing that, Mark! I have another quick follow up question. What do you see when you run a solr search like this one: http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true You should see all your indexed records. But if you don't see any results then it may indicate that your archivesspace configuration directory is not correct. Jesse On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk > wrote: Thanks, Jesse, Here is the output of those commands: ps aux | grep solr | grep -v grep solr 898 0.0 0.1 19096 9812 ? Ss Jul11 0:00 /lib/systemd/systemd --user solr 910 0.0 0.0 169492 3368 ? S Jul11 0:00 (sd-pam) solr 1223 0.5 12.5 4018692 742508 ? Sl Jul11 7:41 java -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= -Dsolr.install.dir=/opt/solr -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip Puzzling! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 09:52, Jesse Martinez wrote: ps aux | grep solr | grep -v grep -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Wed Jul 12 10:32:10 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Wed, 12 Jul 2023 10:32:10 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: <72843f74-da58-0bbf-950d-655c819f95cb@gmail.com> Thanks, Brian, Here is what I see on screen: <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 10:24, Brian Hoffman wrote: > > Hi Mark, > > I believe you have incorrectly set the solr url to a screen on the > control panel. > > Try replacing: > > http://localhost:8983/solr/#/~cores/archivesspace > > > with > > http://localhost:8983/solr/archivesspace > > > *From: *archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Mark Cyzyk > *Date: *Wednesday, July 12, 2023 at 10:19 AM > *To: *jesse.martinez at bc.edu , mcyzyk at jhu.edu > > *Cc: *Archivesspace Users Group > > *Subject: *Re: [Archivesspace_Users_Group] Staging upgrade using > Vagrant/Virtualbox, data in MySQL tables, Solr core present, > reindexed, yet no data displayed in ASpace application > > Darn: > > > |{| > > |? "|responseHeader|":|{ > > ??? "status":0, > > ??? "QTime":187, > > ??? "params":{ > > ????? "q":"*:*", > > ????? "indent":"true", > > ????? "q.op":"OR", > > ????? "_":"1689171084647"}}|,| > > |? "|response|":|{"numFound":0,"start":0,"numFoundExact":true,"docs":[] > > ? }} > > > I will look more carefully at my Solr Aspace config (and yet the steps > in my Vagrant file for setting this up are the same as last summer > when I did this!). > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > Verba volant, scripta manent. > > On 7/12/23 10:09, Jesse Martinez wrote: > > Thanks for sharing that, Mark! > > I have another quick follow up question. > > What do you see when you run a solr search like this one: > > http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true > > > You should?see all your indexed records. But if you don't see any > results then it may indicate that your archivesspace configuration > directory is not correct. > > Jesse > > On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk wrote: > > > Thanks, Jesse, > > Here is the output of those commands: > > ps aux | grep solr | grep -v grep > solr???????? 898? 0.0? 0.1? 19096? 9812 ? Ss?? Jul11?? > 0:00 /lib/systemd/systemd --user > solr???????? 910? 0.0? 0.0 169492? 3368 ? S??? Jul11?? > 0:00 (sd-pam) > solr??????? 1223? 0.5 12.5 4018692 742508 ? Sl?? Jul11?? > 7:41 java -server -Xms512m -Xmx512m -XX:+UseG1GC > -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled > -XX:MaxGCPauseMillis=250 -XX:+UseLargePages > -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent > -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails > -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -XX:+PrintTenuringDistribution > -XX:+PrintGCApplicationStoppedTime > -Xloggc:/var/solr/logs/solr_gc.log > -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 > -XX:GCLogFileSize=20M -Dsolr.jetty.inetaccess.includes= > -Dsolr.jetty.inetaccess.excludes= > -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 > -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC > -XX:-OmitStackTraceInFastThrow > -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 > /var/solr/logs -Djetty.home=/opt/solr/server > -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= > -Dsolr.install.dir=/opt/solr > -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf > -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k > -Dsolr.log.muteconsole -jar start.jar --module=http > --module=gzip > > Puzzling! > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > > Mark Cyzyk, M.A., M.L.S. > > Library Applications Group > > The Sheridan Libraries > > The Johns Hopkins University > > mcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/12/23 09:52, Jesse Martinez wrote: > > ps aux | grep solr | grep -v grep > > > -- > > Jesse Martinez > > Senior Library Applications Developer > > O'Neill Library, Boston College > > jesse.martinez at bc.edu > > 617-552-2509 > > he/him/his > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot1.png Type: image/png Size: 98031 bytes Desc: not available URL: From brian.hoffman at lyrasis.org Wed Jul 12 10:34:46 2023 From: brian.hoffman at lyrasis.org (Brian Hoffman) Date: Wed, 12 Jul 2023 14:34:46 +0000 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: <72843f74-da58-0bbf-950d-655c819f95cb@gmail.com> References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> <72843f74-da58-0bbf-950d-655c819f95cb@gmail.com> Message-ID: Hi Mark, I am referring to the value for :solr_url in the file ?config/config.rb? Brian From: Mark Cyzyk Date: Wednesday, July 12, 2023 at 10:32 AM To: Brian Hoffman , mcyzyk at jhu.edu , Archivesspace Users Group , jesse.martinez at bc.edu Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application Thanks, Brian, Here is what I see on screen: [cid:part1.4LNebPEH.oo0puGr2 at gmail.com] <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 10:24, Brian Hoffman wrote: Hi Mark, I believe you have incorrectly set the solr url to a screen on the control panel. Try replacing: http://localhost:8983/solr/#/~cores/archivesspace with http://localhost:8983/solr/archivesspace From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Date: Wednesday, July 12, 2023 at 10:19 AM To: jesse.martinez at bc.edu , mcyzyk at jhu.edu Cc: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application Darn: { "responseHeader":{ "status":0, "QTime":187, "params":{ "q":"*:*", "indent":"true", "q.op":"OR", "_":"1689171084647"}}, "response":{"numFound":0,"start":0,"numFoundExact":true,"docs":[] }} I will look more carefully at my Solr Aspace config (and yet the steps in my Vagrant file for setting this up are the same as last summer when I did this!). Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 10:09, Jesse Martinez wrote: Thanks for sharing that, Mark! I have another quick follow up question. What do you see when you run a solr search like this one: http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true You should see all your indexed records. But if you don't see any results then it may indicate that your archivesspace configuration directory is not correct. Jesse On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk > wrote: Thanks, Jesse, Here is the output of those commands: ps aux | grep solr | grep -v grep solr 898 0.0 0.1 19096 9812 ? Ss Jul11 0:00 /lib/systemd/systemd --user solr 910 0.0 0.0 169492 3368 ? S Jul11 0:00 (sd-pam) solr 1223 0.5 12.5 4018692 742508 ? Sl Jul11 7:41 java -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data -Dsolr.data.home= -Dsolr.install.dir=/opt/solr -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip Puzzling! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/12/23 09:52, Jesse Martinez wrote: ps aux | grep solr | grep -v grep -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot1.png Type: image/png Size: 98031 bytes Desc: snapshot1.png URL: From jesse.martinez at bc.edu Wed Jul 12 10:36:16 2023 From: jesse.martinez at bc.edu (Jesse Martinez) Date: Wed, 12 Jul 2023 10:36:16 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: I've experienced this same error before, so I can share what I did to remedy this. (You can see the basic steps in this gist .) First, you'll need to delete the existing archivesspace core from your solr instance: solr delete -c archivesspace Next, create the following conf directory: mkdir -p /opt/solr/server/solr/configsets/archivesspace/conf Copy over the ASpace solr conf files to this new directory. This next step is crucial. Create a new archivesspace core with the following command: solr create -c archivesspace -d archivesspace Lastly, restart solr and kick off a new reindex. The -d archivesspace flag in the solr create command will tell solr to use the configuration files in the archivesspace configset. Without that flag you'll get an archivesspace core that doesn't know how to process ASpace records. Hope this helps! Jesse On Wed, Jul 12, 2023 at 10:19?AM Mark Cyzyk wrote: > Darn: > > { > "responseHeader":{ > "status":0, > "QTime":187, > "params":{ > "q":"*:*", > "indent":"true", > "q.op":"OR", > "_":"1689171084647"}}, > "response":{"numFound":0,"start":0,"numFoundExact":true,"docs":[] > }} > > > I will look more carefully at my Solr Aspace config (and yet the steps in > my Vagrant file for setting this up are the same as last summer when I did > this!). > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins Universitymcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/12/23 10:09, Jesse Martinez wrote: > > Thanks for sharing that, Mark! > > I have another quick follow up question. > > What do you see when you run a solr search like this one: > > http://localhost:8983/solr/#/archivesspace/query?q=*:*&q.op=OR&indent=true > > You should see all your indexed records. But if you don't see any results > then it may indicate that your archivesspace configuration directory is not > correct. > > Jesse > > On Wed, Jul 12, 2023 at 10:05?AM Mark Cyzyk wrote: > >> >> Thanks, Jesse, >> >> Here is the output of those commands: >> >> ps aux | grep solr | grep -v grep >> solr 898 0.0 0.1 19096 9812 ? Ss Jul11 0:00 >> /lib/systemd/systemd --user >> solr 910 0.0 0.0 169492 3368 ? S Jul11 0:00 >> (sd-pam) >> solr 1223 0.5 12.5 4018692 742508 ? Sl Jul11 7:41 java >> -server -Xms512m -Xmx512m -XX:+UseG1GC -XX:+PerfDisableSharedMem >> -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=250 -XX:+UseLargePages >> -XX:+AlwaysPreTouch -XX:+ExplicitGCInvokesConcurrent -verbose:gc >> -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps >> -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution >> -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log >> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M >> -Dsolr.jetty.inetaccess.includes= -Dsolr.jetty.inetaccess.excludes= >> -Dsolr.log.dir=/var/solr/logs -Djetty.port=8983 -DSTOP.PORT=7983 >> -DSTOP.KEY=solrrocks -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow >> -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs >> -Djetty.home=/opt/solr/server -Dsolr.solr.home=/var/solr/data >> -Dsolr.data.home= -Dsolr.install.dir=/opt/solr >> -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf >> -Dlog4j.configurationFile=/var/solr/log4j2.xml -Xss256k >> -Dsolr.log.muteconsole -jar start.jar --module=http --module=gzip >> >> Puzzling! >> >> Mark >> >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins Universitymcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> >> On 7/12/23 09:52, Jesse Martinez wrote: >> >> ps aux | grep solr | grep -v grep >> >> >> > > -- > Jesse Martinez > Senior Library Applications Developer > O'Neill Library, Boston College > jesse.martinez at bc.edu > 617-552-2509 > he/him/his > > > -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at gmail.com Wed Jul 12 10:46:27 2023 From: mcyzyk at gmail.com (Mark Cyzyk) Date: Wed, 12 Jul 2023 10:46:27 -0400 Subject: [Archivesspace_Users_Group] Staging upgrade using Vagrant/Virtualbox, data in MySQL tables, Solr core present, reindexed, yet no data displayed in ASpace application In-Reply-To: References: <118167f5-da88-3092-a2d2-f40b8b5021fd@gmail.com> <24b05ff9-7f86-1ffc-5455-e61af0ab93be@gmail.com> Message-ID: Jesse, I'm pretty sure that's what I'm already doing.? From my Vagrantfile: > ? solr_provision = <