More:

The nice thing about Vagrant is that you can pretty quickly run things on a totally different OS.  So this I just did.  I'm now on CentOS-7 (which is what we are running in Dev and Prod anyway).

Again, no issues whatsoever in running the setup-database script and, presumably, getting schemas in sync.

But I boot up archivesspace.sh, and this:

INFO -- : Thread-2000: All tables checked and confirmed set to UTF-8.  Nice job!
========================================================================
      A trace file has been written to the following location: /usr/share/archivesspace/data/tmp/aspace_diagnostic_1596058212.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.
========================================================================
Jul 29, 2020 9:30:12 PM org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: An exception happened during JRuby-Rack startup
undefined method `[]' for nil:NilClass
--- System
jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK 64-Bit Server VM 25.252-b09 on 1.8.0_252-b09 +jit [linux-x86_64]
Time: 2020-07-29 21:30:12 UTC
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
NoMethodError: undefined method `[]' for nil:NilClass
       block in prepare_schemas at uri:classloader:/record_inheritance.rb:31
                           each at org/jruby/RubyArray.java:1735
       block in prepare_schemas at uri:classloader:/record_inheritance.rb:16
                           each at org/jruby/RubyHash.java:1350
                prepare_schemas at uri:classloader:/record_inheritance.rb:15   block in ArchivesSpaceService at /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:108                       configure at /usr/share/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411    <class:ArchivesSpaceService> at /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:79                          <main> at /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:39
                        require at org/jruby/RubyKernel.java:956
                         (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1                block in require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
                  instance_eval at org/jruby/RubyBasicObject.java:1691
                         (root) at /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4                          <main> at uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55
                   start_server at launcher/launcher.rb:92
                           main at launcher/launcher.rb:157
                         <main> at launcher/launcher.rb:261

This is on a fully updated CentOS-7 box.  Something just after the UTF-8 check.

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.

On 7/28/20 11:18 AM, Mark Cyzyk wrote:

Update on this:

Upgraded to latest MySQL Connector (8.0.21).    Still no joy,

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.
On 7/27/20 11:35 AM, Mark Cyzyk wrote:

Hi Lora!

Sorry, I should have mentioned this, I'm running against MariaDB:

MariaDB from Ubuntu 20.04 repository, version 10.3

(We're running against MariaDB here in Prod and Dev on CentOS 7.)

Thanks!

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.
On 7/27/20 11:22 AM, Lora Woodford wrote:

Hiya Mark!

So, if the issue were a db schema mismatch, you’d likely get an error message explaining that.  Something like “Schema Info Mismatch. Expected #{expected schema version}, received #{your schema version} for ASPACE version #{version you’re trying to run}.”


What version of mysql (if mysql?) are you using?  I’ve seen similar issues with folks attempting to run against MySql 8.  Can you try 5.7?

Lora

*From: *<archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcy...@jhu.edu> *Reply-To: *"mcy...@jhu.edu" <mcy...@jhu.edu>, Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
*Date: *Monday, July 27, 2020 at 10:55 AM
*To: *"archivesspace_users_group@lyralists.lyrasis.org" <archivesspace_users_group@lyralists.lyrasis.org> *Subject: *[Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"


All,

I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box before upgrading for real.

I was having problems running the /scripts/database-setup.sh migration script via my Vagrant file, and, as with Vagrant, Ansible, etc. found myself spending lots of time troubleshooting the script I've written to install the software, when I could have just installed the software!

So now I have my Vagrant box up and running, I SSH in and run /scripts/database-setup.sh without any problem.

BUT now that I've kicked this can down the road, the next issue is:

When I go to boot up ASpace, I end up with the following error:

    INFO: DEBUG: resetting rack response due exception
    E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004:
    Connection to backend failed (<!DOCTYPE HTML PUBLIC "-//W3C//DTD
    HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd";
    <http://www.w3.org/TR/html4/loose.dtd>>


I read that if the schema in the DB does not match the schema in the ASpace codebase, the backend will not start.

And yet, the setup-database.sh migration script ran without error, so at this point the schemas should be in sync.

Any advice on how to get the backend up and running greatly appreciated,

Mark

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu  <mailto:mcy...@jhu.edu>
Verba volant, scripta manent.



_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to