Update from 3.5.1 to 4.1.1 failing

13 views
Skip to first unread message

Johnnie Adams

unread,
Aug 11, 2025, 4:32:44 PMAug 11
to Archivesspace_Users_Group
Hi, folks,

     I'm trying to update and getting this error:

Loading ArchivesSpace configuration file from path: /u01/app/svc_archivesspace/archivesspace/config/config.rb

/u01/app/svc_archivesspace/archivesspace-v3.5.1/gems/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/error.rb:105: warning: constant DidYouMean::SPELL_CHECKERS is deprecated

Calling `DidYouMean::SPELL_CHECKERS.merge!(error_name => spell_checker)' has been deprecated. Please call `DidYouMean.correct_error(error_name, spell_checker)' instead.

Aug 11, 2025 3:21:49 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: An exception happened during JRuby-Rack startup

/u01/app/svc_archivesspace/archivesspace-v3.5.1/gems/gems/public_suffix-6.0.1/lib/public_suffix/rule.rb:224: syntax error, unexpected '{ arg'

        new(value: content.to_s[2..], private: private)


     The error makes little sense to me, because I'm not pointed at 3.5.1 any more.


Thanks,


     John A

Johnnie Adams

unread,
Aug 11, 2025, 4:39:14 PMAug 11
to Archivesspace_Users_Group, Johnnie Adams

And of course, I was pointed at 3.5.1, which I changed, and I am now getting this error:

org.jruby.exceptions.NoMethodError: (NoMethodError) undefined method `bytesize' for Rack::Utils:Module

at RUBY.call(uri:classloader:/jruby/rack/error_app/show_status.rb:30)

at org.jruby.rack.ext.Servlet.call(org/jruby/rack/ext/Servlet.java:83)


Aug 11, 2025 3:37:07 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: due a previous initialization failure application instance can not be returned

Aug 11, 2025 3:37:07 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: resetting rack response due exception

uri:classloader:/jruby/rack/error_app/show_status.rb:19: warning: Rack::Utils::HeaderHash is deprecated and will be removed in Rack 3.1, switch to Rack::Headers


Johnnie Adams

unread,
Aug 11, 2025, 4:42:37 PMAug 11
to Archivesspace_Users_Group, Johnnie Adams
And of course that led me to finding out I had database migrations to do, which then led me to this:

I, [2025-08-11T15:41:14.684497 #740849]  INFO -- : Begin applying migration version 158, direction: up

E, [2025-08-11T15:41:15.438348 #740849] ERROR -- : Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'ark_uniq_check' already exists: CREATE TABLE `ark_uniq_check` (`id` integer PRIMARY KEY AUTO_INCREMENT, `record_uri` varchar(255) NOT NULL, `value` varchar(255) NOT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8


    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    !!                                                                                                !!

    !!                                      Database migration error.                                 !!

    !!                                  Your upgrade has encountered a problem.                       !!

    !!                  You must resolve these issues before the database migration can complete.     !!

    !!                                                                                                !!

    !!                                                                                                !!

    !!                                                Error:                                          !!

    !! Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'ark_uniq_check' already exists

    !!                                                                                                !!

    !!                                                                                                !!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Sequel::DatabaseError: Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: Table 'ark_uniq_check' already exists


Johnnie Adams

unread,
Aug 11, 2025, 4:51:47 PMAug 11
to Archivesspace_Users_Group, Johnnie Adams

But I don't have database migrations to do. I thought I remembered 175 being the schema for 3.5.0, checked, and was right about it. At this point, I'm just plain confused.
Reply all
Reply to author
Forward
0 new messages