<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>Alan,</p>
    <p>The virtual box will have to use MySQL v5.5+. The step is that I
      shut down ArchivesSpace on the live and dump the ASpace database,
      then I copy the dump and the ASpace binaries to the new virtual
      instance prepared by our Campus IT. I then run "mysql -u root -p
      <Aspace.sql" to load the database into the MySQL (ever tried
      with v5.5.52 and v5.6.40) then on MySQL command line run grant all
      on archivesspace221.* to 'xx'@'localhost' identified by 'xxx',
      finally run "archivespace.sh start". I can get the staff/public UI
      ready but when clicking any link I see "unexpected error" message
      which leads me to dig errors in the Aspace log file.  Following
      the steps, I can successfully migrate and run ASpace on my
      personal sandbox where MySQL 5.5.52 and openjdk 1.8.0_65 are used.<br>
    </p>
    <p>The virtual box is Redhat 7.8 and running MySQL v5.5.52 (or MySQL
      v.5.6.40) and openjdk v1.8.0_24 while my personal sandbox is
      redhat 7.2.</p>
    <p><br>
    </p>
    <p>Mang<br>
    </p>
    <div class="moz-cite-prefix">On 4/16/2020 12:26 PM, Huebschen, Alan
      M wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:35bd0ceba08a4094a6ac06e6e783cc30@UISMBX03.uisad.uis.edu">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <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:"Segoe UI";
        panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">What
            steps did you take when migrating? Is everything but the
            MySQL version the same as your physical machine? Would it be
            possible to install MySQL v5.1.37 in your virtual instance
            at first?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I
            don’t know if the error could be caused by version
            differences but you might be able to get an exact replica
            instance running and upgrade MySQL once that’s working.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Alan<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
                  style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
                <a class="moz-txt-link-abbreviated" href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>
[<a class="moz-txt-link-freetext" href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
                <b>On Behalf Of </b><a class="moz-txt-link-abbreviated" href="mailto:blake.carver@lyrasis.org">blake.carver@lyrasis.org</a><br>
                <b>Sent:</b> Thursday, April 16, 2020 12:01 PM<br>
                <b>To:</b> Archivesspace Users Group
                <a class="moz-txt-link-rfc2396E" href="mailto:archivesspace_users_group@lyralists.lyrasis.org"><archivesspace_users_group@lyralists.lyrasis.org></a><br>
                <b>Subject:</b> [EXTERNAL] Re:
                [Archivesspace_Users_Group] Can't get ArchivesSpace
                (ASpace) connected to my SQL5.52 and 5.6<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <p class="MsoNormal"><span
              style="font-family:"Calibri",sans-serif;color:black">I
              don't think that's really an ArchivesSpace problem, it's a
              MySQL error that's probably unrelated to your
              ArchivesSpace set up. If you ask your favorite search
              engine about that error, there are solutions. Here's one:<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-family:"Calibri",sans-serif;color:black"><a
href="https://dba.stackexchange.com/questions/58459/mysql-error-impossible-to-write-to-binary-log"
                moz-do-not-send="true">https://dba.stackexchange.com/questions/58459/mysql-error-impossible-to-write-to-binary-log</a><o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-family:"Calibri",sans-serif;color:black">"i</span><span
              style="font-size:11.5pt;font-family:"Segoe
              UI",sans-serif;color:#201F1E;background:white">mpossible
              to write to binary log since BINLOG_FORMAT = STATEMENT and
              at least one table uses a storage engine limited to
              row-based logging. InnoDB is limited to row-logging when
              transaction isolation level is READ COMMITTED or READ
              UNCOMMITTED."</span><span
              style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
        </div>
        <div class="MsoNormal" style="text-align:center" align="center">
          <hr width="98%" size="2" align="center">
        </div>
        <div id="divRplyFwdMsg">
          <p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">
              <a
                href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"
                moz-do-not-send="true">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>
              <<a
                href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"
                moz-do-not-send="true">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
              on behalf of Mang Sun <<a href="mailto:ms20@rice.edu"
                moz-do-not-send="true">ms20@rice.edu</a>><br>
              <b>Sent:</b> Thursday, April 16, 2020 12:53 PM<br>
              <b>To:</b> <a
                href="mailto:archivesspace_users_group@lyralists.lyrasis.org"
                moz-do-not-send="true">archivesspace_users_group@lyralists.lyrasis.org</a>
              <<a
                href="mailto:archivesspace_users_group@lyralists.lyrasis.org"
                moz-do-not-send="true">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
              <b>Subject:</b> [Archivesspace_Users_Group] Can't get
              ArchivesSpace (ASpace) connected to my SQL5.52 and 5.6</span>
            <o:p></o:p></p>
          <div>
            <p class="MsoNormal"> <o:p></o:p></p>
          </div>
        </div>
        <div>
          <p>We are trying to move our ASpace to a new virtual box where
            only MySQL v5.5.52 and 5.6 are available from our current
            physical box where MySQL v.5.1.37 is running. However we
            keep seeing the following errors (excerpted) related to
            login authentication with both versions. MySQL user
            name/passwd I can confirm is right. Java version is openjdk
            1.8.0_242. mysql-connector-java-5.1.34.jar is used. Our
            current ASpace in production  uses MySQL v5.1.37 and JAVA
            1.7.x. Any suggestions?
            <o:p></o:p></p>
          <p>D, [2020-04-16T11:18:03.151130 #4864] DEBUG -- :
            Thread-2252: Responded with [403,
            {"Content-Type"=>"application/json",
            "Cache-Control"=>"private, must-revalidate, max-age=0",
            "Content-Length"=>"25"}, ["{\"error\":\"Login
            failed\"}\n"]]... in 144ms<br>
            E, [2020-04-16T11:18:07.179648 #4864] ERROR -- : Thread-20<span
              style="color:#FF8000">14: Error communicating with
              authentication source DBAuth:
            </span>Java::JavaSql::SQLException: Cannot execute
            statement: impossible to write to binary log since
            BINLOG_FORMAT = STATEMENT and at least one table uses a
            storage engine limited to row-based logging. InnoDB is
            limited to row-logging when transaction isolation level is
            READ COMMITTED or READ UNCOMMITTED.<br>
            E, [2020-04-16T11:18:07.180038 #4864] ERROR -- :<br>
com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:996)<br>
com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3887)<br>
com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3823)<br>
            D, [2020-04-16T11:18:07.181186 #4864] DEBUG -- :
            Thread-2014: Responded with [403,
            {"Content-Type"=>"application/json",
            "Cache-Control"=>"private, must-revalidate, max-age=0",
            "Content-Length"=>"25"}, ["{\"error\":\"Login
            failed\"}\n"]]... in 124ms<br>
            <span style="color:#FF8000">#<RuntimeError:
              Authentication to backend failed: {"error":"Login failed"}</span><br>
            E, [2020-04-16T11:18:12.313302 #4864] ERROR -- :
            Thread-2014: Error communicating with authentication source
            DBAuth: Java::JavaSql::SQLException: Cannot execute
            statement: impossible to write to binary log since
            BINLOG_FORMAT = STATEMENT and at least one table uses a
            storage engine limited to row-based logging. InnoDB is
            limited to row-logging when transaction isolation level is
            READ COMMITTED or READ UNCOMMITTED.<br>
            E, [2020-04-16T11:18:12.313746 #4864] ERROR -- :<br>
com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:996)<br>
com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3887)<br>
com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3823)<br>
            D, [2020-04-16T11:18:12.314931 #4864] DEBUG -- :
            Thread-2014: Responded with [403,
            {"Content-Type"=>"application/json",
            "Cache-Control"=>"private, must-revalidate, max-age=0",
            "Content-Length"=>"25"}, ["{\"error\":\"Login
            failed\"}\n"]]... in 124ms<br>
            #<RuntimeError: Authentication to backend failed:
            {"error":"Login failed"}<o:p></o:p></p>
          <p>Thank you.<o:p></o:p></p>
          <p>Mang Sun<o:p></o:p></p>
          <p>Rice U.<o:p></o:p></p>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Archivesspace_Users_Group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a>
<a class="moz-txt-link-freetext" href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a>
</pre>
    </blockquote>
  </body>
</html>