[Archivesspace_Users_Group] AS v.1.3.0 upgrade failure -- setup_database.bat

Chris Fitzpatrick Chris.Fitzpatrick at lyrasis.org
Mon Sep 14 09:58:29 EDT 2015


Hi Lee,


Yes, the reports features added some stored procedures that have to be installed. Is it possible for you to run the migration as a different user than the user that you normally use to run the application?


b,chris.


Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Cornelison, Lee <cornelison at mitre.org>
Sent: Friday, September 11, 2015 10:55 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Cc: Cornelison, Lee
Subject: [Archivesspace_Users_Group] AS v.1.3.0 upgrade failure -- setup_database.bat

Problem trying to upgrade v1.1.0  to v1.3.0.

My site uses a remote  MySQL 5.6 instance, on a *shared*  institutional MySQL server.

The database migration steps run by setup_database.bat are failing with that error about the Binary Logging:



Running migrations against jdbc:mysql://mysqldev2.mitre.org:3306/archivesspace?user=archivesspace&password=****************&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true
Sequel::DatabaseError: Java::JavaSql::SQLException: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)

  -- AND  trying log_bin_trust_fuction_creators=1  as a connection string parameter ---


Running migrations against jdbc:mysql://mysqldev2.mitre.org:3306/archivesspace?user=archivesspace&password=****************&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true&log_bin_trust_function_creators=1
Sequel::DatabaseError: Java::JavaSql::SQLException: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)


According to follow-up research in the MySQL manuals --

   https://dev.mysql.com/doc/refman/5.6/en/stored-programs-logging.html



One must either have SUPER grants to the entire MySQL installation
OR
Set global   log_bin_trust_function_creators  for the entire installation:


 set the global log_bin_trust_function_creators system variable to 1. By default, this variable has a value of 0, but you can change it like this:

mysql> SET GLOBAL log_bin_trust_function_creators = 1;

You can also set this variable by using the --log-bin-trust-function-creators=1 option when starting the server.


Since my MySQL db is hosted in a multi-user MySQL install,  the dba's are not willing to make these changes that affect other users' dbs.


Is there a way to defeat the Binary Logging requirements for V1.3.0?   This wasn't needed for the v1.x  installations.


Thanks,

Lee Cornelison
The MITRE Corporation



Referred to earlier thread:

http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-July/001898.html










Lee Cornelison
Electronic Records Management Service Architect
R504 - Electronic Content and Records Services
The MITRE Corporation<http://www.mitre.org/> | Bedford, MA
202 Burlington Road, Bedford, MA 01730
1-781-271-5051 | cornelison at mitre.org<mailto:cornelison at mitre.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150914/7991419f/attachment.html>


More information about the Archivesspace_Users_Group mailing list