Bug #44406 rpl.rpl_init_slave fails on pb-2
Submitted: 22 Apr 2009 12:18 Modified: 15 Jul 2009 12:15
Reporter: Alfranio Tavares Correia Junior Email Updates:
Status: Duplicate Impact on me:
None 
Category:Tools: MTR / mysql-test-run Severity:S3 (Non-critical)
Version:5.1, 6.0 OS:Windows
Assigned to: Bjørn Munch CPU Architecture:Any
Tags: pb-2, replication, test

[22 Apr 2009 12:18] Alfranio Tavares Correia Junior
Description:
worker[1] mysql-test-run: WARNING: Process [mysqld.2 - pid: 3348, winpid: 3348, exit: 256] died
Could not open event or process 3348, error: 87
Couldn't open the winpid: 3348 for pid: 3348, try one more time
Could not open event or process 3348, error: 87
Couldn't open the winpid: 3348 for pid: 3348, continue and see what happens...
rpl.rpl_init_slave [ f

How to repeat:
See http://tinyurl.com/cplcvu
[29 Apr 2009 0:19] Alfranio Tavares Correia Junior
It seems to be a a mtr bug. See the command line below:

On windows:
### safe_path: ./lib/My/SafeProcess/debug/my_safe_process.exe --verbose -- D:/ac
orreia/bug-38174/bug-38174/mysql-5.1-bugteam/sql/debug/mysqld.exe --defaults-gro
up-suffix=.2 --defaults-file=D:/acorreia/bug-38174/bug-38174/mysql-5.1-bugteam/m
ysql-test/var/my.cnf --log-output=table,file --loose-skip-innodb "--init-slave=s
et global max_connections=500" --binlog-format=row --core-file

In Linux:

### safe_path: ./lib/My/SafeProcess/my_safe_process --verbose -- /home/acorreia/workspace.sun/repository.mysql/bzrwork/bug-44389/mysql-5.1-bugteam/sql/mysqld --defaults-group-suffix=.2 --defaults-file=/home/acorreia/workspace.sun/repository.mysql/bzrwork/bug-44389/mysql-5.1-bugteam/mysql-test/var/my.cnf --log-output=table,file --loose-skip-innodb --init-slave=set global max_connections=500 --binlog-format=row --core-file  

The option --init-slave=set global max_connections=500 is not being defined properly. 

Setting Lars Heil as Leader and changing the category.
[22 May 2009 23:46] Luis Soares
See also BUG#44920.
[15 Jul 2009 12:15] Bjørn Munch
This is the same problem as Bug #43005, caused by incorrect handling of server arguments containing spaces.