[Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"

Mon Jul 27 11:22:22 EDT 2020

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-bounces at lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk at jhu.edu>
Reply-To: "mcyzyk at jhu.edu" <mcyzyk at jhu.edu>, Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, July 27, 2020 at 10:55 AM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at 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

mcyzyk at jhu.edu<mailto:mcyzyk at jhu.edu>

Verba volant, scripta manent.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200727/d6b5ecd4/attachment.html>