Alan,
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.
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.
Mang
On 4/16/2020 12:26 PM, Huebschen, Alan M wrote:
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?
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.
-Alan
*From:*[email protected]
[mailto:[email protected]] *On
Behalf Of *[email protected]
*Sent:* Thursday, April 16, 2020 12:01 PM
*To:* Archivesspace Users Group
<[email protected]>
*Subject:* [EXTERNAL] Re: [Archivesspace_Users_Group] Can't get
ArchivesSpace (ASpace) connected to my SQL5.52 and 5.6
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:
https://dba.stackexchange.com/questions/58459/mysql-error-impossible-to-write-to-binary-log
"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."
------------------------------------------------------------------------
*From:*[email protected]
<mailto:[email protected]>
<[email protected]
<mailto:[email protected]>> on
behalf of Mang Sun <[email protected] <mailto:[email protected]>>
*Sent:* Thursday, April 16, 2020 12:53 PM
*To:* [email protected]
<mailto:[email protected]>
<[email protected]
<mailto:[email protected]>>
*Subject:* [Archivesspace_Users_Group] Can't get ArchivesSpace
(ASpace) connected to my SQL5.52 and 5.6
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.
_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
[email protected]
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
