<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<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:<br>
<br>
<blockquote>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 class="moz-txt-link-rfc2396E" href="http://www.w3.org/TR/html4/loose.dtd">"http://www.w3.org/TR/html4/loose.dtd"</a>><br>
</blockquote>
<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>
<pre class="moz-signature" cols="72">--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
<a class="moz-txt-link-abbreviated" href="mailto:mcyzyk@jhu.edu">mcyzyk@jhu.edu</a>
Verba volant, scripta manent.
</pre>
</body>
</html>