<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hiya Mark!<br>
<br>
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}.”<o:p></o:p></p>
<p class="MsoNormal"><br>
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?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Lora<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk@jhu.edu><br>
<b>Reply-To: </b>"mcyzyk@jhu.edu" <mcyzyk@jhu.edu>, Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Date: </b>Monday, July 27, 2020 at 10:55 AM<br>
<b>To: </b>"archivesspace_users_group@lyralists.lyrasis.org" <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject: </b>[Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
All,<br>
<br>
I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box before upgrading for real.<br>
<br>
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!<br>
<br>
So now I have my Vagrant box up and running, I SSH in and run /scripts/database-setup.sh without any problem.<br>
<br>
BUT now that I've kicked this can down the road, the next issue is:<br>
<br>
When I go to boot up ASpace, I end up with the following error:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">INFO: DEBUG: resetting rack response due exception<br>
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"
<a href="http://www.w3.org/TR/html4/loose.dtd">"http://www.w3.org/TR/html4/loose.dtd"</a>><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
I read that if the schema in the DB does not match the schema in the ASpace codebase, the backend will not start.<br>
<br>
And yet, the setup-database.sh migration script ran without error, so at this point the schemas should be in sync.<br>
<br>
Any advice on how to get the backend up and running greatly appreciated,<br>
<br>
Mark<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><o:p> </o:p></pre>
<pre>Mark Cyzyk, M.A., M.L.S.<o:p></o:p></pre>
<pre>Library Applications Group<o:p></o:p></pre>
<pre>The Sheridan Libraries<o:p></o:p></pre>
<pre>The Johns Hopkins University<o:p></o:p></pre>
<pre><a href="mailto:mcyzyk@jhu.edu">mcyzyk@jhu.edu</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Verba volant, scripta manent. <o:p></o:p></pre>
</div>
</body>
</html>