3 messages in com.mysql.lists.bugsslave status in rpl000015.test| From | Sent On | Attachments |
|---|---|---|
| Julian Ladisch | 06 Oct 2002 18:10 | |
| Michael Widenius | 07 Oct 2002 10:49 | |
| Julian Ladisch | 07 Oct 2002 17:53 |
| Subject: | slave status in rpl000015.test |
|---|---|
| From: | Michael Widenius (mon...@mysql.com) |
| Date: | 10/07/2002 10:49:14 AM |
| List: | com.mysql.lists.bugs |
Hi!
"Julian" == Julian Ladisch <mysq...@ladisch.de> writes:
Description:
Julian> rpl000015.test fails because of an additional slave status result.
How-To-Repeat:
Julian> cd mysql-test Julian> ./mysql-test-run --do-test=rpl000015 Julian> *************** Julian> *** 5,10 **** Julian> --- 5,11 ---- Julian> reset slave; Julian> show slave status; Julian> Master_Host Master_User Master_Port Connect_retry Julian> Master_Log_File Read_Master_Log_PosRelay_Log_File Relay_Log_Pos Julian> Relay_Master_Log_File Slave_IO_Running Slave_SQL_Running Julian> Replicate_do_db Replicate_ignore_db Last_errno Last_error Julian> Skip_counter Exec_master_log_pos Relay_log_space Julian> + 127.0.0.1 root MASTER_PORT 1 4
This is strange; I have seen this problem once before but not being able to repeat this.
We did also run the test suite on all machines for which we make binaries, but didn't encounter this one for 4.0.4.
This probably means that we have a non critical timing issue when doing 'show slave status' just after a reset.
Can you repeat the above on your machine by doing just:
cd mysql-test mysql-test-run --local rpl000015.test ?
Note that even if this fails, your MySQL distribution should be ok.
Regards, Monty