Error "old insecure authentication mechanism not supported"

Issue

After upgrading to Console 2.3.0, the old passwords mode of authentication is no longer supported. The following error appears on the Node's logs during an asperacentral restart:

Mar  8 12:42:35 shares asperacentral[27554]: ERR Could not connect to the db [007c817710e5ddc5@10.27.0.9:4406 aspera_console] on error [15,drizzle_state_handshake_result_read:old insecure authentication mechanism not supported]
Mar  8 12:42:35 shares asperacentral[27554]: LOG Init could not create db string formatter
Mar  8 12:42:35 shares asperacentral[27554]: ERR Init ERROR could not init mysql adapter

 

This is due to the MySQL server storing passwords in the old password mode. The fix is to edit the /etc/my.cnf file on the Console server, restart mysqld, and change the password for the database user of the node.

Environment

  • Product: Console
  • Version: Upgrade to 2.3.0
  • Operating System: Linux

 

Solution

1. Change the old_passwords line in /etc/my.cnf to match the following:

# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=0

 

2. Restart mysqld:

asctl mysql:restart

 

3. Get the DB username and password from the node's database section in /opt/aspera/etc/aspera.conf:

    <database>
        <server>10.27.0.9</server>
        <port>4406</port>
        <user>007c817710e5ddc5</user>
        <password>b1015090b7679ded0133c7ae25...c0a763dee6708665ca3</password>
        <database_name>aspera_console</database_name>
    </database>

 

4. Login as root in MySQL and reset the database user's password (in this example, the IP of 10.250.0.4 is the IP of the Managed Node connecting in):

# mysql -u root -p --socket /opt/aspera/common/mysql/var/run/mysql.sock

mysql> use mysql;
mysql> set password for '007c817710e5ddc5'@'10.250.0.4' = password('b1015090b7679ded0133c7ae25...c0a763dee6708665ca3');

 

5. Restart asperacentral on the node:

/etc/init.d/asperacentral restart

 

The error should no longer show up.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk