Bug #17863 mysql_install_db fails, when the IM is used

• Submitted: 2 Mar 2006 15:16
• Modified: 17 Apr 2006 16:57
• Reporter: Lenz Grimmer
• Status: Closed
• Category: MySQL Server: Installing
• Severity: S3 (Non-critical)
• Version: 5.1-BK, 5.1.7, any?
• OS: Linux (Linux)
• Assigned to: Alexander Nozdrin
• CPU Architecture: Any

[2 Mar 2006 15:16] Lenz Grimmer

Description:
I defined an instance as described in http://dev.mysql.com/doc/refman/5.0/en/instance-manager-configuration-files.html:

[mysqld]
mysqld-path=/usr/sbin/mysqld
socket=/var/lib/mysql/mysql.sock
port=3306

This causes mysql_install_db to fail (noticed that upon an RPM upgrade):

[SNIP]
Installing all prepared tables
060302 16:03:26 [ERROR] /usr/sbin/mysqld: unknown variable 'mysqld-path=/usr/sbin/mysqld'

Installation of system tables failed!
[SNIP]

This is suboptimal, especially since mysql_install_db

How to repeat:
Create a [mysql] instance in /etc/my.cnf that contains IM-specific variables like "mysqld-path", run mysql_install_db. Observe the error.

Suggested fix:
Not sure. Looks like it's not a good idea to have a [mysqld] instance, as the variables in that section are read by both the IM and mysqld...

[3 Mar 2006 13:31] Valeriy Kravchuk

Thank you for a problem report. Looks like either mysql_install_db should be changed to filter out IM options or, even better, my_print_defaults should be changed (option added to show IM-specific options).

[11 Apr 2006 17:57] Mike Hillyer

What specific fix? Just a list of disallowed names for instances? What names do we disallow?

[17 Apr 2006 16:57] Mike Hillyer

Documentation updated to always instruct the use of [mysqldN] section names.