Troubleshoot errors commonly encountered during or post migration to Azure Database for MySQL
APPLIES TO: Azure Database for MySQL - Single Server Azure Database for MySQL - Flexible Server
Azure Database for MySQL - Single Server is on the retirement path. We strongly recommend for you to upgrade to Azure Database for MySQL - Flexible Server. For more information about migrating to Azure Database for MySQL - Flexible Server, see What's happening to Azure Database for MySQL Single Server?
Azure Database for MySQL is a fully managed service powered by the community version of MySQL. The MySQL experience in a managed service environment may differ from running MySQL in your own environment. In this article, you'll see some of the common errors users may encounter while migrating to or developing on Azure Database for MySQL for the first time.
Common Connection Errors
ERROR 1184 (08S01): Aborted connection 22 to db: 'db-name' user: 'user' host: 'hostIP' (init_connect command failed)
The above error occurs after successful sign-in but before executing any command when session is established. The above message indicates you have set an incorrect value of
init_connect server parameter, which is causing the session initialization to fail.
There are some server parameters like
require_secure_transport that aren't supported at the session level, and so trying to change the values of these parameters using
init_connect can result in Error 1184 while connecting to the MySQL server as shown below:
mysql> show databases; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id: 64897 Current database: *** NONE *** ERROR 1184 (08S01): Aborted connection 22 to db: 'db-name' user: 'user' host: 'hostIP' (init_connect command failed)
init_connect value in Server parameters tab in Azure portal and set only the supported server parameters using init_connect parameter.
Errors due to lack of SUPER privilege and DBA role
The SUPER privilege and DBA role aren't supported on the service. As a result, you may encounter some common errors listed below:
ERROR 1419: 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)
The above error may occur while creating a function, trigger as below or importing a schema. The DDL statements like CREATE FUNCTION or CREATE TRIGGER are written to the binary log, so the secondary replica can execute them. The replica SQL thread has full privileges, which can be exploited to elevate privileges. To guard against this danger for servers that have binary logging enabled, the MySQL engine requires that stored function creators have the SUPER privilege, in addition to the usual CREATE ROUTINE privilege.
CREATE FUNCTION f1(i INT) RETURNS INT DETERMINISTIC READS SQL DATA BEGIN RETURN i; END;
Resolution: To resolve the error, set
log_bin_trust_function_creators to 1 from server parameters blade in portal, execute the DDL statements or import the schema to create the desired objects. You can continue to maintain
log_bin_trust_function_creators to 1 for your server to avoid the error in future. Our recommendation is to set
log_bin_trust_function_creators as the security risk highlighted in MySQL community documentation is minimal in Azure Database for MySQL as bin log isn't exposed to any threats.
ERROR 1227 (42000) at line 101: Access denied; you need (at least one of) the SUPER privilege(s) for this operation. Operation failed with exitcode 1
The above error may occur while importing a dump file or creating procedure that contains definers.
Resolution: To resolve this error, the admin user can grant privileges to create or execute procedures by running GRANT command as in the following examples:
GRANT CREATE ROUTINE ON mydb.* TO 'someuser'@'somehost'; GRANT EXECUTE ON PROCEDURE mydb.myproc TO 'someuser'@'somehost';
Alternately, you can replace the definers with the name of the admin user that is running the import process as shown below.
DELIMITER;; /*!50003 CREATE*/ /*!50017 DEFINER=`root`@`127.0.0.1`*/ /*!50003 DELIMITER;; /* Modified to */ DELIMITER ;; /*!50003 CREATE*/ /*!50017 DEFINER=`AdminUserName`@`ServerName`*/ /*!50003 DELIMITER ;
ERROR 1227 (42000) at line 295: Access denied; you need (at least one of) the SUPER or SET_USER_ID privilege(s) for this operation
The above error may occur while executing CREATE VIEW with DEFINER statements as part of importing a dump file or running a script. Azure Database for MySQL doesn't allow SUPER privileges or the SET_USER_ID privilege to any user.
- Use the definer user to execute CREATE VIEW if possible. It's likely that there are many views with different definers having different permissions, so this may not be feasible. OR
- Edit the dump file or CREATE VIEW script and remove the DEFINER= statement from the dump file. OR
- Edit the dump file or CREATE VIEW script and replace the definer values with user with admin permissions who is performing the import or execute the script file.
Use sed or perl to modify a dump file or SQL script to replace the DEFINER= statement
ERROR 1227 (42000) at line 18: Access denied; you need (at least one of) the SUPER privilege(s) for this operation
The above error may occur if you're using trying to import the dump file from MySQL server with GTID enabled to the target Azure Database for MySQL server. Mysqldump adds SET @@SESSION.sql_log_bin=0 statement to a dump file from a server where GTIDs are in use, which disables binary logging while the dump file is being reloaded.
Resolution: To resolve this error while importing, remove or comment out the below lines in your mysqldump file and run import again to ensure it's successful.
SET @MYSQLDUMP_TEMP_LOG_BIN = @@SESSION.SQL_LOG_BIN; SET @@SESSION.SQL_LOG_BIN= 0; SET @@GLOBAL.GTID_PURGED=''; SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;
Common connection errors for server admin sign-in
When an Azure Database for MySQL server is created, a server admin sign-in is provided by the end user during the server creation. The server admin sign-in allows you to create new databases, add new users and grant permissions. If the server admin sign-in is deleted, its permissions are revoked or its password is changed, you may start to see connections errors in your application while connections. Following are some of the common errors
ERROR 1045 (28000): Access denied for user 'username'@'IP address' (using password: YES)
The above error occurs if:
- The username doesn't exist.
- The user username was deleted.
- its password is changed or reset.
Validate if "username" exists as a valid user in the server or is accidentally deleted. You can execute the following query by logging into the Azure Database for MySQL user:
select user from mysql.user;
If you can't sign in to the MySQL to execute the above query itself, we recommend you to reset the admin password using Azure portal. The reset password option from Azure portal will help recreate the user, reset the password, and restore the admin permissions, which will allow you to sign in using the server admin and perform further operations.
If you didn't find the answer you're looking for, consider the following options:
- Post your question on Microsoft Q&A question page or Stack Overflow.
- Send an email to the Azure Database for MySQL Team @Ask Azure DB for MySQL. This email address isn't a technical support alias.
- Contact Azure Support, file a ticket from the Azure portal. To fix an issue with your account, file a support request in the Azure portal.
- To provide feedback or to request new features, create an entry via UserVoice.
Submit and view feedback for