MySQL Bugs: #12629: mysqld_multi produces syntax error

Bug #12629	mysqld_multi produces syntax error
Submitted:	17 Aug 2005 20:22	Modified:	30 Sep 2005 13:44
Reporter:	Victoria Reznichenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Linux (linux)
Assigned to:	Jani Tolonen	CPU Architecture:	Any

Description:
If I run MySQL server via mysqld_multi script with the following InnoDB startup options I get syntax error:

innodb_data_home_dir=
innodb_data_file_path=/users/victoria/mysql-5.0.11/u02/mysqldata/mysqld3/ibdata1:20M;/users/victoria/mysql-5.0.11/u02/mysqldata/mysqld3/i
bdata2:20M:autoextend

Error mesage:
050817 22:13:25 [ERROR] InnoDB: syntax error in innodb_data_file_path
050817 22:13:25 [ERROR] Can't init databases
050817 22:13:25 [ERROR] Aborting

If I use mysqld_multi that comes with 4.1 distribution it works fine.

How to repeat:
Add InnoDB start up options to the my.cnf and start MySQL server via mysqlod_multi v2.14:

innodb_data_home_dir=
innodb_data_file_path=/users/victoria/mysql-5.0.11/u02/mysqldata/mysqld3/ibdata1:20M;/users/victoria/mysql-5.0.11/u02/mysqldata/mysqld3/i
bdata2:20M:autoextend

I experienced the same error when specifying more than 1 innodb_logfile in the my_multi.cnf that is called from mysqld_multi.  The error occurs whether or not you specify the autoextend option for the last specified logfilename.

Error occurs when specifying the following in referenced --config-file for mysqld_multi:
innodb_data_file_path     = innodb_data2a:10M;innodb_data2b:10M
- or -
innodb_data_file_path     = innodb_data2a:10M;innodb_data2b:10M:autoextend
- or -
innodb_data_file_path     = innodbdata2a:10M;innodbdata2b:10M

still get:
050825 10:08:46  mysqld started
050825 10:08:46 [ERROR] InnoDB: syntax error in innodb_data_file_path
050825 10:08:46 [ERROR] Can't init databases
050825 10:08:46 [ERROR] Aborting

050825 10:08:46 [Note] /u01/app/mysql/mysql-standard-5.0.10-beta-solaris9-sparc-64bit/bin/mysqld: Shutdown complete

050825 10:08:46  mysqld ended

I think it is not reading the semi-colon separator correctly!

Hi!

If I recall, this problem with semicolon was there 4 years ago, but Jani Tolonen or someone else fixed mysqld_multi at that time. Maybe the same bug has slipped into 5.0.

Regards,

Heikki

Ok, I know this is Jani's bug, but I wanted to get multi-servers running myself, and saw that if I simply run via the command line what mysqld_multi tries to run for each server, the semicolon that's escaped with two back slashes is what causes the error:

mysql@krsna:~> /usr/local/mysql/libexec/mysqld --port="3306" --socket="/tmp/mysql.sock" --datadir="/usr/local/mysql/var" --wait_timeout="300" --log="/usr/local/mysql/var/mysql.log" --language="/usr/local/mysql/share/mysql/english" --skip-locking --key_buffer="16M" --max_allowed_packet="128M" --table_cache="64" --sort_buffer_size="512K" --net_buffer_length="8K" --myisam_sort_buffer_size="8M" --log-bin --server-id="1" --innodb_data_home_dir="" --innodb_data_file_path="/usr/local/mysql/data/ibdata1:10M\\;/usr/local/mysql/data/ibdata2:10M:autoextend" --innodb_log_group_home_dir="/usr/local/mysql/var/" --innodb_log_arch_dir="/usr/local/mysql/var/" --innodb_buffer_pool_size="200M" --innodb_additional_mem_pool_size="20M" --innodb_log_file_size="50M" --innodb_log_buffer_size="20M" --innodb_flush_log_at_trx_commit="1" --innodb_lock_wait_timeout="50"
050929 23:29:49 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=krsna-bin' to avoid this problem.
050929 23:29:49 [ERROR] InnoDB: syntax error in innodb_data_file_path
050929 23:29:49 [ERROR] Can't init databases
050929 23:29:49 [ERROR] Aborting

But if I take out the '\\'

mysql@krsna:~> /usr/local/mysql/libexec/mysqld --port="3306" --socket="/tmp/mysql.sock" --datadir="/usr/local/mysql/var" --wait_timeout="300" --log="/usr/local/mysql/var/mysql.log" --language="/usr/local/mysql/share/mysql/english" --skip-locking --key_buffer="16M" --max_allowed_packet="128M" --table_cache="64" --sort_buffer_size="512K" --net_buffer_length="8K" --myisam_sort_buffer_size="8M" --log-bin --server-id="1" --innodb_data_home_dir="" --innodb_data_file_path="/usr/local/mysql/data/ibdata1:10M;/usr/local/mysql/data/ibdata2:10M:autoextend" --innodb_log_group_home_dir="/usr/local/mysql/var/" --innodb_log_arch_dir="/usr/local/mysql/var/" --innodb_buffer_pool_size="200M" --innodb_additional_mem_pool_size="20M" --innodb_log_file_size="50M" --innodb_log_buffer_size="20M" --innodb_flush_log_at_trx_commit="1" --innodb_lock_wait_timeout="50"
050929 23:30:11 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=krsna-bin' to avoid this problem.
050929 23:30:12  InnoDB: Error: page 7 log sequence number 0 45226
InnoDB: is in the future! Current system log sequence number 0 43669.

ok, yes, warnings, but the main issue is fixed ;)

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/30540

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/30562

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html