[Archivesspace_Users_Group] AS upgrade from 1.5.3->2.2.1 blew up, help.

[Jeff Earickson]

Adam,

Once my DB guy said that mysql was fine, that was the next thing we did.
Still no go.

Regarding the other person's comment about going from 1.5.3 -> 2.1.2 ->
2.2.1 that is an idea (but I would have to get back to a working 1.5.3
first).  But...  I did not see
anyplace that the leap from 1.5x to 2.2.x was not allowed in the update
instructions.  :(

My attempt to retreat back to 1.5.3 via changing my symlink back to
arcspace-v1.5.3 and a database restore of 1.5.3 also failed.  Very
surprising and painful.

Jeff Earickson
Colby College

On Tue, Nov 28, 2017 at 12:13 PM, Adam Jazairi <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>
> wrote:
>
>> All,
>>
>> Per the instructions at 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=[R
>> EDACTED]&password=[REDACTED]&useSSL=false&useUnicode=true&ch
>> aracterEncoding=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/s
>> inatra-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/jrub
>> y.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
>>                   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
>>                          <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
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>>
>
>
> --
> Adam Jazairi
> Digital Library Applications Developer
> Boston College
> (617) 552-1404
> adam.jazairi at bc.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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171128/5e1dbcd2/attachment.html>