Bug #23808 Instance Manager reporting "Too many arguments (first argument is '')"

• Submitted: 31 Oct 2006 16:38
• Modified: 28 Nov 2006 14:14
• Reporter: Craig Sylvester
• Status: Can't repeat
• Category: Instance Manager
• Severity: S3 (Non-critical)
• Version: 5.0.26
• OS: Linux (SuSE Linux Desktop 10.0)
• CPU Architecture: Any

[31 Oct 2006 16:38] Craig Sylvester

Description:
Instance Manager fails to start database server with the following error being reported:

061031 11:02:10 guardian: starting instance mysqld2
/usr/local/mysql5.0.26/bin/mysqld: Too many arguments (first extra is '').
Use --help to get a list of available options

Entry in /etc/my.cnf file reads:

[mysqld50026]
mysqld-path = /usr/local/mysql5.0.26/bin/mysqld
server-id = 1
port  = 3306
pid-file = /tmp/mysql50026.pid
socket  = /tmp/mysql50026.sock
datadir  = /usr/local/mysql5.0.26/data

NOTE: This appears to be related to bug #21275 and if fact may be the same issue if the XXX contains periods.

How to repeat:
Install server in directory (or create link) with periods in the path (i.e., /usr/local/mysql5.0.26) and change my.cnf entries accordingly.

Modify the mysql.server script to start the Instance Manager instead of using mysqld_safe:

    use_mysqld_safe = 0

Attempt to start server with instance manager:

"$MYSQL_HOME/bin/mysqlmanager --user=mysql --pid-file=/tmp/mysqlmanager.pid"

or "/etc/init.d/mysql.server start"

Suggested fix:
Removing the periods from the mysqld-path entry fixes the problem. 

So the my.cnf entry now reads:

[mysqld50026]
mysqld-path = /usr/local/mysql50026/bin/mysqld
server-id = 1
port  = 3306
pid-file = /tmp/mysql50026.pid
socket  = /tmp/mysql50026.sock
datadir  = /usr/local/mysql50026/data

[28 Nov 2006 14:14] MySQL Verification Team

Thank you for the bug report. I was unable to repeat with today source
repository server on Suse Linux 10:

061128 12:06:19 IM pid file: '/tmp/mysqlmanager.pid'; PID: 5758.
061128 12:06:20 guardian: starting instance 'mysqld5032'...
061128 12:06:20 starting instance 'mysqld5032'...
061128 12:06:20 accepting connections on ip socket (port: 2273)
061128 12:06:20 accepting connections on unix socket '/tmp/mysqlmanager.sock'
061128 12:06:20  InnoDB: Started; log sequence number 0 43655
061128 12:06:21 [Note] /home/miguel/mysql5.0.32/libexec/mysqld: ready for connections.
Version: '5.0.32-debug'  socket: '/tmp/mysql50032.sock'  port: 3306  Source distribution
061128 12:06:40 guardian: instance 'mysqld5032' is running, set state to STARTED.