<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>We noticed that error as well and ever tried with <span
style="color: rgb(32, 31, 30); font-family: "Segoe
UI", "Segoe UI Web (West European)", "Segoe
UI", -apple-system, BlinkMacSystemFont, Roboto,
"Helvetica Neue", sans-serif; font-size: 15px;
background-color: rgb(255, 255, 255); display: inline
!important">BINLOG_FORMAT =MIXED but MySQL can't even get
started. What I didn't mention in the first place, I don't have
any problem migrating the SAME MySQL dump and ASpace binaries to
my own personal sandbox where same Redhat 7, MySQL v5.5.52 and
openjDK 1.8.0_65 are present whereas the virtual box is prepared
our by Campus IT. Agreed, this seems to not be a problem about
ArchivesSpace per se but more related to "compatibility" between
ASpace (v2.2.1) and MySQL. Thank you.<br>
</span></p>
<p><span style="color: rgb(32, 31, 30); font-family: "Segoe
UI", "Segoe UI Web (West European)", "Segoe
UI", -apple-system, BlinkMacSystemFont, Roboto,
"Helvetica Neue", sans-serif; font-size: 15px;
background-color: rgb(255, 255, 255); display: inline
!important"><br>
</span></p>
<p><span style="color: rgb(32, 31, 30); font-family: "Segoe
UI", "Segoe UI Web (West European)", "Segoe
UI", -apple-system, BlinkMacSystemFont, Roboto,
"Helvetica Neue", sans-serif; font-size: 15px;
background-color: rgb(255, 255, 255); display: inline
!important">Mang<br>
</span></p>
<div class="moz-cite-prefix">On 4/16/2020 12:01 PM,
<a class="moz-txt-link-abbreviated" href="mailto:blake.carver@lyrasis.org">blake.carver@lyrasis.org</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DM6PR22MB23097155C7ECAF2B567EF7209FD80@DM6PR22MB2309.namprd22.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
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:</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
<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><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif;
font-size: 12pt; color: rgb(0, 0, 0);">
"i<span style="color: rgb(32, 31, 30); font-family: "Segoe
UI", "Segoe UI Web (West European)",
"Segoe UI", -apple-system, BlinkMacSystemFont,
Roboto, "Helvetica Neue", sans-serif; font-size:
15px; background-color: rgb(255, 255, 255); display: inline
!important">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></div>
<div>
<div id="Signature">
<div id="divtagdefaultwrapper" dir="ltr"
style="color:rgb(0,0,0); background-color:rgb(255,255,255)">
</div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
<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-rfc2396E" href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><archivesspace_users_group-bounces@lyralists.lyrasis.org></a>
on behalf of Mang Sun <a class="moz-txt-link-rfc2396E" href="mailto:ms20@rice.edu"><ms20@rice.edu></a><br>
<b>Sent:</b> Thursday, April 16, 2020 12:53 PM<br>
<b>To:</b> <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-rfc2396E" href="mailto:archivesspace_users_group@lyralists.lyrasis.org"><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</font>
<div> </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?
<br>
</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<font
color="#ff8000">14: Error communicating with authentication
source DBAuth:
</font>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>
<font color="#ff8000">#<RuntimeError: Authentication to
backend failed: {"error":"Login failed"}</font><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"}<br>
</p>
<p>Thank you.<br>
</p>
<p>Mang Sun</p>
<p>Rice U.<br>
</p>
</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>