Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Tom, Thanks for the suggestion. If I understand you correctly, the suggestion is to modify the "Gemfile.lock" file on the "aspace-oauth" gem to change the "public_suffix" version to 4.0.6. I gave it a try, and made the following changes to the "Gemfile.lock" file (and reran the "initialize-plugin.sh" script), and was able to start ArchivesSpace without error: * "public_suffix (4.0.7)" to "public_suffix (4.0.6)" * "addressable (2.8.1)" to "addressable (2.8.0)" * "public_suffix (>= 2.0.2, < 6.0)" to "public_suffix (>= 2.0.2, < 5.0)" I wonder, though, if the actual issue is something deeper. The "addressable"/"public_suffix" gem versions are specified in the following files of the ArchivesSpace v3.3.1 source code: * Gemfile.lock (addressable v2.7.0, public_suffix v4.0.6) * frontend/Gemfile.lock (addressable v2.8.0, public_suffix v4.0.6) * public/Gemfile.lock (addressable v2.8.0, publix_suffix v4.0.6) Also, the "backend/Gemfile" specifies the "rubyXL" v3.4.18 gem, which has a transitive dependency in its "Gemfile.lock" file ( https://github.com/weshatheleopard/rubyXL/blob/v3.4.18/Gemfile.lock) on the public_suffix v4.0.6 and addressable v2.8.0 gems. This problem does not seem to occur in our previous version (v3.1.1), because the addressable v2.80 and public_suffix v4.0.6 gems were provided in the "gems/gems" directory of the ArchivesSpace v3.1.1 binary distribution, but are not provided in the v3.3.1 binary distribution. Since at least one gem (rubyXL) in the ArchiveSpace source code appears to rely on the addressable/public_suffix gems, should they be included in the "gems/gems" directory of the ArchivesSpace binary distribution? Thanks for all the help, David On Tue, Dec 6, 2022 at 3:47 PM Tom Hanstra wrote: > Try updating the Gemfile.lock to use the 4.0.6 version of the gem and then > run the initialize_plugin script. I'm pretty sure that was how I got around > the issue at one point. > > You just need to get the plugin bundled. Version does not matter (in my > experience). > > Tom > > On Tue, Dec 6, 2022 at 3:03 PM David P. Steelman wrote: > >> Thanks for the quick responses. >> >> I have tried using aspace-oauth v3.2.0, and am running the >> 'initialize_plugin" script, and still receiving the same error. >> >> On the server, there is a >> "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a >> "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the >> "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem >> >> The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" >> WAR files from the ArchivesSpace distribution each contain a reference to >> "public_suffix" v4.0.6. >> >> In the ArchivesSpace v3.3.1 source distribution there are references to >> "plugin_suffix:4.0.6" in the following files: >> >> * Gemfile.lock >> * docs/Gemfile.lock >> * frontend/Gemfile.lock >> * public/Gemfile.lock >> >> So I'm wondering if there is some kind of confusion about which version >> of the gem is supposed to be used. >> >> Thanks, >> >> David >> >> On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra wrote: >> >>> There was a version of the aspace-oauth plugin in which the >>> public_suffix gem did not compile. I remember having some problems with >>> that. >>> >>> I just rebuilt mine here and it looks like the current version is >>> working right, with the 4.0.7 version. So it may help to simply download >>> again. >>> >>> Tom >>> >>> On Tue, Dec 6, 2022 at 2:19 PM Blake Carver >>> wrote: >>> Try using the latest tag version on that plugin. https://github.com/lyrasis/aspace-oauth/tags -- *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of David P. Steelman *Sent:* Tuesday, December 6, 2022 2:02 PM *To:* Archivesspace Users Group < archivesspace_users_group@lyralists.lyrasis.org> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin Hello all, In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am encountering the following error on startup: Dec 05, 2022 8:23:43 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find public_suffix-4.0.6 in any of the sources from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize' from org/jruby/RubyArray.java:2621:in `map!' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs' ... We are using the "aspace-oauth" plugin (
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Try updating the Gemfile.lock to use the 4.0.6 version of the gem and then run the initialize_plugin script. I'm pretty sure that was how I got around the issue at one point. You just need to get the plugin bundled. Version does not matter (in my experience). Tom On Tue, Dec 6, 2022 at 3:03 PM David P. Steelman wrote: > Thanks for the quick responses. > > I have tried using aspace-oauth v3.2.0, and am running the > 'initialize_plugin" script, and still receiving the same error. > > On the server, there is a > "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a > "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the > "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem > > The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" WAR > files from the ArchivesSpace distribution each contain a reference to > "public_suffix" v4.0.6. > > In the ArchivesSpace v3.3.1 source distribution there are references to > "plugin_suffix:4.0.6" in the following files: > > * Gemfile.lock > * docs/Gemfile.lock > * frontend/Gemfile.lock > * public/Gemfile.lock > > So I'm wondering if there is some kind of confusion about which version of > the gem is supposed to be used. > > Thanks, > > David > > On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra wrote: > >> There was a version of the aspace-oauth plugin in which the public_suffix >> gem did not compile. I remember having some problems with that. >> >> I just rebuilt mine here and it looks like the current version is working >> right, with the 4.0.7 version. So it may help to simply download again. >> >> Tom >> >> On Tue, Dec 6, 2022 at 2:19 PM Blake Carver >> wrote: >> >>> Try using the latest tag version on that plugin. >>> >>> >>> https://github.com/lyrasis/aspace-oauth/tags >>> -- >>> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < >>> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of >>> David P. Steelman >>> *Sent:* Tuesday, December 6, 2022 2:02 PM >>> *To:* Archivesspace Users Group < >>> archivesspace_users_group@lyralists.lyrasis.org> >>> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace >>> v3.3.1/aspace-oauth plugin >>> >>> Hello all, >>> >>> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am >>> encountering the following error on startup: >>> >>> >>> Dec 05, 2022 8:23:43 PM >>> org.eclipse.jetty.server.handler.ContextHandler$Context log >>> WARNING: ERROR: initialization failed >>> org.jruby.rack.RackInitializationException: Could not find >>> public_suffix-4.0.6 in any of the sources >>> from >>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in >>> `block in materialize' >>> from org/jruby/RubyArray.java:2621:in `map!' >>> from >>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in >>> `materialize' >>> from >>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in >>> `specs' >>> ... >>> >>> >>> We are using the "aspace-oauth" plugin ( >>> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin >>> from the configuration the error does not occur. >>> >>> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the >>> "gems/gems" directory in the v3.3.1 distribution includes significantly >>> fewer gems, and no longer includes a "public_suffix-3.0.6" directory. >>> >>> Any pointers in handling this issue are appreciated. >>> >>> Thanks, >>> >>> David >>> ___ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group@lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> >> >> -- >> *Tom Hanstra* >> *Sr. Systems Administrator* >> hans...@nd.edu >> >> >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Thanks for the quick responses. I have tried using aspace-oauth v3.2.0, and am running the 'initialize_plugin" script, and still receiving the same error. On the server, there is a "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" WAR files from the ArchivesSpace distribution each contain a reference to "public_suffix" v4.0.6. In the ArchivesSpace v3.3.1 source distribution there are references to "plugin_suffix:4.0.6" in the following files: * Gemfile.lock * docs/Gemfile.lock * frontend/Gemfile.lock * public/Gemfile.lock So I'm wondering if there is some kind of confusion about which version of the gem is supposed to be used. Thanks, David On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra wrote: > There was a version of the aspace-oauth plugin in which the public_suffix > gem did not compile. I remember having some problems with that. > > I just rebuilt mine here and it looks like the current version is working > right, with the 4.0.7 version. So it may help to simply download again. > > Tom > > On Tue, Dec 6, 2022 at 2:19 PM Blake Carver > wrote: > >> Try using the latest tag version on that plugin. >> >> >> https://github.com/lyrasis/aspace-oauth/tags >> -- >> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < >> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of >> David P. Steelman >> *Sent:* Tuesday, December 6, 2022 2:02 PM >> *To:* Archivesspace Users Group < >> archivesspace_users_group@lyralists.lyrasis.org> >> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace >> v3.3.1/aspace-oauth plugin >> >> Hello all, >> >> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am >> encountering the following error on startup: >> >> >> Dec 05, 2022 8:23:43 PM >> org.eclipse.jetty.server.handler.ContextHandler$Context log >> WARNING: ERROR: initialization failed >> org.jruby.rack.RackInitializationException: Could not find >> public_suffix-4.0.6 in any of the sources >> from >> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in >> `block in materialize' >> from org/jruby/RubyArray.java:2621:in `map!' >> from >> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in >> `materialize' >> from >> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in >> `specs' >> ... >> >> >> We are using the "aspace-oauth" plugin ( >> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin >> from the configuration the error does not occur. >> >> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the >> "gems/gems" directory in the v3.3.1 distribution includes significantly >> fewer gems, and no longer includes a "public_suffix-3.0.6" directory. >> >> Any pointers in handling this issue are appreciated. >> >> Thanks, >> >> David >> ___ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hans...@nd.edu > > > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
There was a version of the aspace-oauth plugin in which the public_suffix gem did not compile. I remember having some problems with that. I just rebuilt mine here and it looks like the current version is working right, with the 4.0.7 version. So it may help to simply download again. Tom On Tue, Dec 6, 2022 at 2:19 PM Blake Carver wrote: > Try using the latest tag version on that plugin. > > > https://github.com/lyrasis/aspace-oauth/tags > -- > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of > David P. Steelman > *Sent:* Tuesday, December 6, 2022 2:02 PM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace > v3.3.1/aspace-oauth plugin > > Hello all, > > In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am > encountering the following error on startup: > > > Dec 05, 2022 8:23:43 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > WARNING: ERROR: initialization failed > org.jruby.rack.RackInitializationException: Could not find > public_suffix-4.0.6 in any of the sources > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in > `block in materialize' > from org/jruby/RubyArray.java:2621:in `map!' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in > `materialize' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in > `specs' > ... > > > We are using the "aspace-oauth" plugin ( > https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from > the configuration the error does not occur. > > Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" > directory in the v3.3.1 distribution includes significantly fewer gems, and > no longer includes a "public_suffix-3.0.6" directory. > > Any pointers in handling this issue are appreciated. > > Thanks, > > David > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Try using the latest tag version on that plugin. https://github.com/lyrasis/aspace-oauth/tags From: archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of David P. Steelman Sent: Tuesday, December 6, 2022 2:02 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin Hello all, In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am encountering the following error on startup: Dec 05, 2022 8:23:43 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find public_suffix-4.0.6 in any of the sources from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize' from org/jruby/RubyArray.java:2621:in `map!' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize' from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs' ... We are using the "aspace-oauth" plugin (https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from the configuration the error does not occur. Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" directory in the v3.3.1 distribution includes significantly fewer gems, and no longer includes a "public_suffix-3.0.6" directory. Any pointers in handling this issue are appreciated. Thanks, David ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin
Be sure to run the initialize_plugin script again after the upgrade. Tom On Tue, Dec 6, 2022 at 2:06 PM David P. Steelman wrote: > Hello all, > > In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am > encountering the following error on startup: > > > Dec 05, 2022 8:23:43 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > WARNING: ERROR: initialization failed > org.jruby.rack.RackInitializationException: Could not find > public_suffix-4.0.6 in any of the sources > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in > `block in materialize' > from org/jruby/RubyArray.java:2621:in `map!' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in > `materialize' > from > /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in > `specs' > ... > > > We are using the "aspace-oauth" plugin ( > https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from > the configuration the error does not occur. > > Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" > directory in the v3.3.1 distribution includes significantly fewer gems, and > no longer includes a "public_suffix-3.0.6" directory. > > Any pointers in handling this issue are appreciated. > > Thanks, > > David > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
