Bug #49327 MySQL 4.0.13 does not do - show MASTER STATUS.
Submitted: 2 Dec 2009 6:43 Modified: 2 Dec 2009 8:04
Reporter: Amit Bora Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.13 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[2 Dec 2009 6:43] Amit Bora
Description:
Hi,

I have installed MySQL 4.0.13. But I couldn't found the my.ini file anywhere.

I am trying to make a setup for switchover /failover. 
I cerated my.ini file on "C:\my.ini" with content as

[mysqld]
basedir="C:/mysql/"
datadir="C:/mysql/Data/"
binlog-do-db=mysql_repl
server-id=1
log-bin="C:/MySQL_Binary_Log/"

Is this the correct way to create my.ini file?

After When I do the steps for replication as:

On Master machine:

mysql> GRANT REPLICATION SLAVE ON *.* TO 'slave_user'@'10.77.176.105' IDENTIFIED
BY 'password';
Query OK, 0 rows affected (0.05 sec)

mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.03 sec)

mysql> USE mysql_repl;
Database changed
mysql> FLUSH TABLES WITH READ LOCK;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW MASTER STATUS;
Empty set (0.02 sec)

mysql> select user, host from mysql.user;
+------------+---------------+
| user | host |
+------------+---------------+
| | % |
| root | % |
| slave_user | 10.77.176.105 |
| | localhost |
| root | localhost |
+------------+---------------+
5 rows in set (0.11 sec)

mysql> SHOW MASTER STATUS;
Empty set (0.00 sec)

mysql>

It does not show me the master status. Then How can I dump the database on Slave machine?

Any help on this highly appreciated.

P.S.-> I know MySQL 4.0.13 is outdated but we are using it.

How to repeat:

mysql> GRANT REPLICATION SLAVE ON *.* TO 'slave_user'@'10.77.176.105' IDENTIFIED
BY 'password';
Query OK, 0 rows affected (0.05 sec)

mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.03 sec)

mysql> USE mysql_repl;
Database changed
mysql> FLUSH TABLES WITH READ LOCK;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW MASTER STATUS;
Empty set (0.02 sec)
[2 Dec 2009 7:10] Sveta Smirnova
Thank you for taking the time to report a problem.  Unfortunately you are not using a current version of the product you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.

Did you restart server after creating ini file? Check error log also.
[2 Dec 2009 8:04] Amit Bora
I have already tried using MySQL version 5.1.34, it is working fine.

As we are still using MySQL 4,0.13, Let me just confirm that Is this problem occurred in MySQL 4.0.13?
[24 Sep 2010 15:36] Guenter K
oh well ...
not only that you're 3 major branches behind - even with the 4.0.x branch you're 14 versions behind latest ...
I can understand well that its difficult to upgrade from 4.0.x to a later version due to date whoes and such, but you could at least update to 4.0.27 which should be absolutely painless - means update binaries and your existing dbs continue to work without changes:
http://mirrors.ukfast.co.uk/sites/ftp.mysql.com/Downloads/MySQL-4.0/?P=*noinstall*

HTH, G.