Bug #89340 mysqlfrm cannot use a login-path named 'client' to connect to the server
Submitted: 22 Jan 2018 9:46 Modified: 23 Jan 2018 9:25
Reporter: claire wahl Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Utilities Severity:S3 (Non-critical)
Version:1.6.5-1debian8 OS:Debian
Assigned to: CPU Architecture:Any
Tags: login-path, mysqlfrm

[22 Jan 2018 9:46] claire wahl
Description:
mysqlfrm cannot be used with the '--server=client' option, which should refer to a login-path named client.

Here is the login-path:
# mysql_config_editor print --all
[client]
user = root
password = *****
host = localhost
socket = /var/run/mysqld/mysqld.sock

Here is the failure log:
# mysqlfrm -q --user=root --server client --port=3315 /vol/vol_mysql_bkp_prod/rdblx/weekly/xtrabkp-n-1/ArchiExpoDonnees/CR_CompteRendu.frm -vvv
# Cloning the MySQL server located at /usr.
# Configuring new instance...
# Locating mysql tools...
# Location of files:
#                       mysqld: /usr/sbin/mysqld
#                   mysqladmin: /usr/bin/mysqladmin
#      mysql_system_tables.sql: /usr/share/mysql/mysql_system_tables.sql
# mysql_system_tables_data.sql: /usr/share/mysql/mysql_system_tables_data.sql
# mysql_test_data_timezone.sql: /usr/share/mysql/mysql_test_data_timezone.sql
#         fill_help_tables.sql: /usr/share/mysql/fill_help_tables.sql
# Setting up empty database and mysql tables...
2018-01-22 10:21:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-01-22 10:21:02 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
2018-01-22 10:21:02 0 [Note] /usr/sbin/mysqld (mysqld 5.6.37) starting as process 9268 ...
2018-01-22 10:21:02 9268 [Note] Plugin 'FEDERATED' is disabled.
2018-01-22 10:21:02 9268 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-01-22 10:21:02 9268 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-22 10:21:02 9268 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-22 10:21:02 9268 [Note] InnoDB: Memory barrier is not used
2018-01-22 10:21:02 9268 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-22 10:21:02 9268 [Note] InnoDB: Using Linux native AIO
2018-01-22 10:21:02 9268 [Note] InnoDB: Using CPU crc32 instructions
2018-01-22 10:21:02 9268 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-01-22 10:21:02 9268 [Note] InnoDB: Completed initialization of buffer pool
2018-01-22 10:21:02 9268 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2018-01-22 10:21:02 9268 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2018-01-22 10:21:02 9268 [Note] InnoDB: Database physically writes the file full: wait...
2018-01-22 10:21:02 9268 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2018-01-22 10:21:02 9268 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2018-01-22 10:21:02 9268 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2018-01-22 10:21:02 9268 [Warning] InnoDB: New log files created, LSN=45781
2018-01-22 10:21:02 9268 [Note] InnoDB: Doublewrite buffer not found: creating new
2018-01-22 10:21:02 9268 [Note] InnoDB: Doublewrite buffer created
2018-01-22 10:21:02 9268 [Note] InnoDB: 128 rollback segment(s) are active.
2018-01-22 10:21:02 9268 [Warning] InnoDB: Creating foreign key constraint system tables.
2018-01-22 10:21:02 9268 [Note] InnoDB: Foreign key constraint system tables created
2018-01-22 10:21:02 9268 [Note] InnoDB: Creating tablespace and datafile system tables.
2018-01-22 10:21:02 9268 [Note] InnoDB: Tablespace and datafile system tables created.
2018-01-22 10:21:02 9268 [Note] InnoDB: Waiting for purge to start
2018-01-22 10:21:03 9268 [Note] InnoDB: 5.6.37 started; log sequence number 0
2018-01-22 10:21:04 9268 [Note] Binlog end
2018-01-22 10:21:04 9268 [Note] InnoDB: FTS optimize thread exiting.
2018-01-22 10:21:04 9268 [Note] InnoDB: Starting shutdown...
2018-01-22 10:21:05 9268 [Note] InnoDB: Shutdown completed; log sequence number 1625977
# Starting new instance of the server...
# Startup command for new server:
/usr/sbin/mysqld --no-defaults --basedir=/usr --datadir=/tmp/tmpC1E3pz --pid-file=/tmp/tmpC1E3pz/clone.pid --port=3315 --server-id=101 --socket=/tmp/tmpC1E3pz/mysql.sock --tmpdir=/tmp/tmpC1E3pz --user=root
# Testing connection to new instance...
2018-01-22 10:21:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-01-22 10:21:06 0 [Note] /usr/sbin/mysqld (mysqld 5.6.37) starting as process 9290 ...
2018-01-22 10:21:06 9290 [Note] Plugin 'FEDERATED' is disabled.
2018-01-22 10:21:06 9290 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-01-22 10:21:06 9290 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-22 10:21:06 9290 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-22 10:21:06 9290 [Note] InnoDB: Memory barrier is not used
2018-01-22 10:21:06 9290 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-22 10:21:06 9290 [Note] InnoDB: Using Linux native AIO
2018-01-22 10:21:06 9290 [Note] InnoDB: Using CPU crc32 instructions
2018-01-22 10:21:06 9290 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-01-22 10:21:06 9290 [Note] InnoDB: Completed initialization of buffer pool
2018-01-22 10:21:06 9290 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-22 10:21:06 9290 [Note] InnoDB: 128 rollback segment(s) are active.
2018-01-22 10:21:06 9290 [Note] InnoDB: Waiting for purge to start
2018-01-22 10:21:06 9290 [Note] InnoDB: 5.6.37 started; log sequence number 1625977
2018-01-22 10:21:06 9290 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 9303d3de-ff55-11e7-992f-005056bb2ae4.
2018-01-22 10:21:06 9290 [Note] Server hostname (bind-address): '*'; port: 3315
2018-01-22 10:21:06 9290 [Note] IPv6 is available.
2018-01-22 10:21:06 9290 [Note]   - '::' resolves to '::';
2018-01-22 10:21:06 9290 [Note] Server socket created on IP: '::'.
2018-01-22 10:21:06 9290 [Note] Event Scheduler: Loaded 0 events
2018-01-22 10:21:06 9290 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.37'  socket: '/tmp/tmpC1E3pz/mysql.sock'  port: 3315  MySQL Community Server (GPL)
# trying again...
# Success!
# Setting the root password...
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: YES)'
# Connection Information:
#  -uroot -proot --socket=/tmp/tmpC1E3pz/mysql.sock
#...done.
ERROR: Spawn server operation failed. To diagnose, run the utility again and use the --verbose option to view the messages from the spawned server and correct any errors presented then run the utility again.

If I rename the login-path to 'pivot', it works perfectly:
# mysql_config_editor print --all
[pivot]
user = root
password = *****
host = localhost
socket = /var/run/mysqld/mysqld.sock

# mysqlfrm -q --user=root --server pivot --port=3315 /vol/vol_mysql_bkp_prod/rdblx/weekly/xtrabkp-n-1/ArchiExpoDonnees/CR_CompteRendu.frm
#
# CREATE statement for /vol/vol_mysql_bkp_prod/rdblx/weekly/xtrabkp-n-1/ArchiExpoDonnees/CR_CompteRendu.frm:
#
***

How to repeat:
1. configure a login-path named client
2. mysqlfrm -q --user=root --server client --port=3315 <frm file> -vvv
[23 Jan 2018 9:25] MySQL Verification Team
Hello claire,

Thank you for the report and feedback.

Thanks,
Umesh