What's the JAVA version on there? ________________________________ From: archivesspace_users_group-boun...@lyralists.lyrasis.org <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Cory Nimer <cory_ni...@byu.edu> Sent: Friday, April 23, 2021 12:42 PM To: Christine Di Bella <christine.dibe...@lyrasis.org>; Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org) <archivesspace_users_group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2
Christine, Here are the basic specs for our testing server according to our IT staff: RHEL 8.3 4 procs 5GB RAM For what it's worth, the error I posted that says there is a missing ruby gem is what I see if I go to the staff interface. If I go to the PUI, it will show a different missing ruby gem (sassc-2.4.0). Not sure if other pages might reveal other missing gems. Christine mentioned that others had seen a similar issue but the gem mentioned was different, so maybe they were looking at a different page. In any case it seems that somehow this build of ArchivesSpace is missing some required ruby gems. If you need other information about the server, please let me know. Best, Cory From: Christine Di Bella <christine.dibe...@lyrasis.org> Sent: Friday, April 23, 2021 9:17 AM To: Cory Nimer <cory_ni...@byu.edu>; Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org) <archivesspace_users_group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2 Hello Cory, We're investigating a gem-related issue where the second release candidate is not running correctly on some kinds of servers. (We encountered something similar on a Windows server yesterday, though the gem mentioned was different.) Would you please post the specs of your server here or email them to me directly? There was an issue that affected all Rails applications between the release of our first release candidate and our second one that required us to do some unplanned upgrades, though we were hopeful that the impact would be limited for 3.0 since Rails came out with a fix for their issue during that timeframe. We definitely want to hear from people if they are experiencing issues installing RC2. Thanks for your help, Christine ________________________________ From: Cory Nimer <cory_ni...@byu.edu<mailto:cory_ni...@byu.edu>> Sent: Friday, April 23, 2021 10:18 AM To: Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>) <archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>; Christine Di Bella <christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>> Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2 Christine, When installing the release candidate our IT staff reports that they are encountering an error, as described below: I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. Everything seemed to install ok, and the server seems to start up ok (based on the log output), but when I try to bring up the public or staff website I get an error. I'm wondering if you could post something on the listserv or point me in the right direction to do it. I upgraded from v2.8.1 and followed the upgrade directions here: https://archivesspace.github.io/tech-docs/administration/upgrading.html Here's the error I get when I try to bring up the staff website (https://asadminstg.lib.byu.edu<https://asadminstg.lib.byu.edu/>): Internal Server Error (500) Request Method: GET Request URL: http://asadminstg.lib.byu.edu/ Could not find rubyntlm-0.6.3 in any of the sources from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in `specs_for' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in `requested_specs' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in `block in requested_specs' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in `setup' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in `setup' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `block in <main>' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in `with_level' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in `silence' from /srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `<main>' from org/jruby/RubyKernel.java:974:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:130:in `require' from /srv/archivesspace-3.0.0-rc2/archivesspace/data/tmp/jetty-0.0.0.0-10080-frontend.war-_-any-/webapp/WEB-INF/config/boot.rb:10:in `<main>' from org/jruby/RubyKernel.java:974:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in `require' from uri:classloader:/jruby/rack/rails/environment3.rb:23:in `load_environment' from uri:classloader:/jruby/rack/rails_booter.rb:83:in `load_environment' from <script>:1:in `<main>' from launcher/launcher.rb:89:in `start_server' from launcher/launcher.rb:162:in `main' from launcher/launcher.rb:258:in `<main>' You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. Looking at the error, I'm wondering if this build might be missing some required ruby gems. I don't know if anyone else is experiencing this error with 3.0.0-RC2, but it is preventing us from being able to test the release candidate locally at this point. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_uac-boun...@lyralists.lyrasis.org<mailto:archivesspace_uac-boun...@lyralists.lyrasis.org> <archivesspace_uac-boun...@lyralists.lyrasis.org<mailto:archivesspace_uac-boun...@lyralists.lyrasis.org>> On Behalf Of Christine Di Bella Sent: Tuesday, April 20, 2021 7:15 AM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>; Archivesspace Member Reps <archivesspace_member_r...@lyralists.lyrasis.org<mailto:archivesspace_member_r...@lyralists.lyrasis.org>>; 'archivesspace_...@lyralists.lyrasis.org' <archivesspace_...@lyralists.lyrasis.org<mailto:archivesspace_...@lyralists.lyrasis.org>>; 'archivesspace_...@lyralists.lyrasis.org' <archivesspace_...@lyralists.lyrasis.org<mailto:archivesspace_...@lyralists.lyrasis.org>>; archivesspace_small_archives_users_gr...@lyralists.lyrasis.org<mailto:archivesspace_small_archives_users_gr...@lyralists.lyrasis.org> Cc: ArchivesSpace Board of Trustees mail list <archivesspace_bot_memb...@lyralists.lyrasis.org<mailto:archivesspace_bot_memb...@lyralists.lyrasis.org>> Subject: [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2 Hello ArchivesSpace members, The ArchivesSpace team is pleased to announce a release candidate, v3.0.0-RC2. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v3.0.0-RC2 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). We have put out a second release candidate because a good deal of code has gone into our main branch since the release of the first release candidate. While some consists of improvements to the agents work that is the focus of v3.0.0, there have also been additional contributions from community developers and substantial work from the program team developers. One of the community contributions I wanted to note is a new spreadsheet import feature from developers and archivists at Harvard University, focused on adding top containers and associated information to existing archival objects. With this feature, a user will download a file of archival objects for a resource, add top container information outside the application, and then import the information into the resource record, from the Load via Spreadsheet area. Some draft documentation for this feature written by Harvard Staff is available at https://docs.google.com/document/d/10poB5BDwgEWGYwrfLgkfy_sOjkhmbvStDat_BIm6ucw/edit?usp=sharing. Please feel free to leave feedback on the documentation. Also included in the community contributions are a range of performance, backend and staff interface improvements courtesy of work Hudson Molonglo developers James Bullen, Mark Triggs, and Payten Giles did for Queensland State Archives as part of a larger project. The core of this release candidate centers around changes to the agents module of ArchivesSpace to make it more standards-compliant with EAC-CPF and the MARCXML format for authority data, enabling deeper and richer description of people, families, and corporate entities, their relationships to each other and their relationships to materials held outside ArchivesSpace. This work is the result of a community specification written through the participation of many users across the ArchivesSpace community, mostly notably Cory Nimer, Sue Luftschein, and Brad Westbrook. Through this work new fields and sub-records have been added to the agents schema, and staff and public interface views, imports, exports, and auxiliary functionality like agent merging have all been updated. There is also a new Light mode for agents, which provides the option for users to continue to work with agent records in the staff interface in a pared down view that is similar to that of ArchivesSpace versions prior to this one. Thanks to the many community members who made contributions as we worked on bringing this expanded functionality to ArchivesSpace, including both individual archives staff and developers and our Testing and User Documentation sub-teams. Please try this release candidate out and let us know at archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by April 27 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. We are aiming to release 3.0.0 by the end of the month. Please get in touch if you have any questions. Thanks as always for your feedback and support. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org> 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium]
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
