<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<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">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>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Mang Sun <ms20@rice.edu><br>
<b>Sent:</b> Thursday, April 16, 2020 12:53 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org <archivesspace_users_group@lyralists.lyrasis.org><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>
</body>
</html>