[Archivesspace_Users_Group] Can't get ArchivesSpace (ASpace) connected to my SQL5.52 and 5.6

[Mang Sun]

The version of our ASpace is v2.2.1.

Mang

On 4/16/2020 11:53 AM, Mang Sun wrote:
>
> 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?
>
> 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
> E, [2020-04-16T11:18:07.179648 #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.
> E, [2020-04-16T11:18:07.180038 #4864] ERROR -- :
> com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:996)
> com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3887)
> com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3823)
> 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
> #<RuntimeError: Authentication to backend failed: {"error":"Login failed"}
> 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.
> E, [2020-04-16T11:18:12.313746 #4864] ERROR -- :
> com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:996)
> com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3887)
> com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3823)
> 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
> #<RuntimeError: Authentication to backend failed: {"error":"Login failed"}
>
> Thank you.
>
> Mang Sun
>
> Rice U.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200416/b577ee0b/attachment.html>