[Archivesspace_Users_Group] AS upgrade from 1.5.3->2.2.1 blew up, help.
Mang Sun
mang.sun at rice.edu
Tue Nov 28 14:25:51 EST 2017
I guess jump straight from 1.5.x to 2.2.1 may possibly miss the
migration (convert to UTF-8) step for that table but upgrade first to
2.1.2 can get the said migration step applied.
Mang
On 11/28/2017 12:37 PM, Jeff Earickson wrote:
> All,
>
> Problem Solved!!!
>
> The issue was thus, near the top of the log output, a warning that
> turns out to be **FATAL**:
>
> *W, [2017-11-28T10:22:03.136709 #9290]WARN -- : Thread-2000:*
>
> *The following MySQL database tables are not set to use UTF-8 for
> their character*
>
> *encoding:*
>
>
> ** rights_statement_pre_088*
>
>
> The fix is to convert that database table (not the database) to UTF-8
> in either Sql Workbench or via:
>
> ALTER TABLE rights_statement_pre_088 CONVERT TO CHARACTER SET utf8;
>
>
> BTW, I ended up at mysql-connector-java-5.1.40 by chance after I got
> it restarted. Per the advice here, I am going to leave it at that
> version for the time being.
>
> Thanks to all who responded.
>
>
> -----------------------------------
> Jeff A. Earickson, Ph.D
> Senior Server System Administrator
> Colby College,
> 4214 Mayflower Hill,
> Waterville ME, 04901-8842
> 207-859-4214 (fax 207-859-4186)
> Eastern Time Zone, USA
> -----------------------------------
>
> On Tue, Nov 28, 2017 at 12:13 PM, Adam Jazairi <jazairi at bc.edu
> <mailto:jazairi at bc.edu>> wrote:
>
> Hi Jeff,
>
> Could you try switching back to mysql-connector-java-5.1.40 or
> mysql-connector-java-5.1.39 and see if that fixes it? We've had
> problems in the past with versions above 5.1.40.
>
> Adam
>
> On Tue, Nov 28, 2017 at 11:52 AM, Jeff Earickson
> <jaearick at colby.edu <mailto:jaearick at colby.edu>> wrote:
>
> All,
>
> Per the instructions at
> http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/
> <http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/>
> I upgraded from 1.5.3 to 2.2.1 this morning. The database
> conversion went fine.
>
> Now I cannot get AS restarted, the logs say:
>
> E, [2017-11-28T10:22:03.545378 #9290] ERROR -- : Thread-2000:
> ***** DATABASE CONNECTION FAILED *****
>
> ArchivesSpace could not connect to your specified database URL
> (jdbc:mysql://vrpmysql2.colby.edu:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useSSL=false&useUnicode=true&characterEncoding=UTF-8
> <http://vrpmysql2.colby.edu:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useSSL=false&useUnicode=true&characterEncoding=UTF-8>).
>
> Please check your configuration and try again.
> ========================================================================
> A trace file has been written to the following location:
> /opt/archivesspace-v2.2.1/data/tmp/aspace_diagnostic_1511882523.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.
> ========================================================================
> Nov 28, 2017 10:22:03 AM
> org.eclipse.jetty.server.handler.ContextHandler$Context log
> INFO: An exception happened during JRuby-Rack startup
> Database connection failed
> --- System
> jruby 9.1.8.0 (2.3.1) 2017-03-06 90fc7ab OpenJDK 64-Bit Server
> VM 25.151-b12 on 1.8.0_151-b12 +jit [linux-x86_64]
> Time: 2017-11-28 10:22:03 -0500
> Server: jetty/8.1.5.v20120716
> jruby.home: uri:classloader://META-INF/jruby.home
>
> --- Context Init Parameters:
> jruby.compat.version = 1.9
> jruby.max.runtimes = 1
> jruby.min.runtimes = 1
> public.root = /
> rack.env = production
>
> --- Backtrace
> RuntimeError: Database connection failed
> block in ArchivesSpaceService at
> /opt/archivesspace-v2.2.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101
> configure at
> /opt/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411
> <class:ArchivesSpaceService> at
> /opt/archivesspace-v2.2.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78
> <main> at
> /opt/archivesspace-v2.2.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38
> require at org/jruby/RubyKernel.java:961
> require at
> uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
> block in (root) at
> /opt/archivesspace-v2.2.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1
> <http://config.ru:1>
> instance_eval at
> org/jruby/RubyBasicObject.java:1687
> (root) at
> /opt/archivesspace-v2.2.1/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4
> <http://config.ru:4>
> <main> at
> uri:classloader:/vendor/rack-1.5.5/rack/builder.rb:55
> start_server at launcher/launcher.rb:92
> main at launcher/launcher.rb:157
> <main> at launcher/launcher.rb:261
>
> I huddled with my DB guy and he says that there is nothing
> wrong with the database. He could connect to it with the
> username and password.
>
> The other thing I did in the upgrade was
> move mysql-connector-java-5.1.40 to 5.1.44, putting the mysql
> jar file in the lib subdir in 2.2.1.
>
> What's wrong? How to fix? I have the diagnostic file available.
>
> My system: Redhat 7.4, java-1.8.0-openjdk-1.8.0.151-1
> installed via rpm.
>
> Jeff Earickson
> Colby College
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
>
>
>
>
> --
> Adam Jazairi
> Digital Library Applications Developer
> Boston College
> (617) 552-1404 <tel:%28617%29%20552-1404>
> adam.jazairi at bc.edu <mailto:adam.jazairi at bc.edu>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
>
>
>
>
> _______________________________________________
> 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171128/d6aa18a8/attachment.html>
More information about the Archivesspace_Users_Group
mailing list