Bug #11483 possible port assignment problem in mysql-test-run.pl

• Submitted: 21 Jun 2005 14:17
• Modified: 1 Jul 2005 13:02
• Reporter: Ingo Strüwing
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.0
• OS: Linux (Linux/x86)
• Assigned to: Kent Boortz
• CPU Architecture: Any

[21 Jun 2005 14:17] Ingo Strüwing

Description:
The following command leads to a failing test:

cd mysql-test && ./mysql-test-run.pl --master_port=59142 --slave_port=59146 --force --local federated
...
federated                       [ fail ]
Errors are (from /home/mydev/mysql-5.0-bug10932/mysql-test/var/log/mysqltest-time) :
/home/mydev/mysql-5.0-bug10932/client/.libs/mysqltest: Could not open connection 'slave': Can't connect to MySQL server on '127.0.0.1' (111)
(the last lines may be the most important ones)

The same command, but without the '.pl' lets the test pass.

How to repeat:
cd mysql-test && ./mysql-test-run.pl --master_port=59142 --slave_port=59146 --force --local federated

Suggested fix:
'federated' probably needs a special port assignment.

[22 Jun 2005 1:31] MySQL Verification Team

Installing Slave Databases
=======================================================
Finding  Tests in the 'main' suite
Starting Tests in the 'main' suite

TEST                            RESULT
-------------------------------------------------------

federated                       [ fail ]
Errors are (from /home/miguel/dbs/mysql-5.0/mysql-test/var/log/mysqltest-time) :
/home/miguel/dbs/mysql-5.0/client/.libs/lt-mysqltest: Could not open connection 'slave': Can't connect to MySQL server on '127.0.0.1' (111)
(the last lines may be the most important ones)

[1 Jul 2005 13:02] Kent Boortz

The Perl version of mysql-test-run did not start the
slave node, giving a connect error. This is now
corrected.