Description:
pushbuild failure:
rpl.rpl_row_max_relay_size [ fail ]
CURRENT_TEST: rpl.rpl_row_max_relay_size
=== SHOW MASTER STATUS ===
---- 1. ----
File slave-bin.000042
Position 818
Binlog_Do_DB
Binlog_Ignore_DB
==========================
=== SHOW SLAVE STATUS ===
---- 1. ----
Slave_IO_State Queueing master event to the relay log
Master_Host 127.0.0.1
Master_User root
Master_Port 11010
Connect_Retry 1
Master_Log_File master-bin.000001
Read_Master_Log_Pos 20120
Relay_Log_File slave-relay-bin.000003
Relay_Log_Pos 18446744073697230938
Relay_Master_Log_File master-bin.000001
Slave_IO_Running Yes
Slave_SQL_Running No
Replicate_Do_DB
Replicate_Ignore_DB
Replicate_Do_Table
Replicate_Ignore_Table
Replicate_Wild_Do_Table
Replicate_Wild_Ignore_Table
Last_Errno 1594
Last_Error Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
Skip_Counter 0
Exec_Master_Log_Pos 4
Relay_Log_Space 20935
Until_Condition None
Until_Log_File
Until_Log_Pos 0
Master_SSL_Allowed No
Master_SSL_CA_File
Master_SSL_CA_Path
Master_SSL_Cert
Master_SSL_Cipher
Master_SSL_Key
Seconds_Behind_Master
Master_SSL_Verify_Server_Cert No
Last_IO_Errno 0
Last_IO_Error
Last_SQL_Errno 1594
Last_SQL_Error Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
=========================
=== SHOW PROCESSLIST ===
---- 1. ----
Id 2
User root
Host localhost:1530
db test
Command Query
Time 0
State
Info SHOW PROCESSLIST
---- 2. ----
Id 3
User root
Host localhost:1531
db test
Command Sleep
Time 2
State
Info
---- 3. ----
Id 10
User system user
Host
db
Command Connect
Time 0
State Queueing master event to the relay log
Info
---- 4. ----
Id 11
User system user
Host
db
Command Connect
Time 0
State Waiting for slave mutex on exit
Info
========================
analyze: sync_with_master
mysqltest: In included file ".\extra\rpl_tests\rpl_max_relay_size.test": At line 69: sync_with_master failed: 'select master_pos_wait('master-bin.000001', 169868, 300)' returned NULL indicating slave SQL thread failure
The result from queries just before the failure was:
< snip >
Master_SSL_CA_File
Master_SSL_CA_Path
Master_SSL_Cert
Master_SSL_Cipher
Master_SSL_Key
Seconds_Behind_Master #
Master_SSL_Verify_Server_Cert No
Last_IO_Errno #
Last_IO_Error #
Last_SQL_Errno 0
Last_SQL_Error
#
# Test 3: max_relay_log_size = 0
#
stop slave;
reset slave;
set global max_relay_log_size=0;
select @@global.max_relay_log_size;
@@global.max_relay_log_size 0
start slave;
More results from queries before failure can be found in e:\var-ps_row-101\log\rpl_row_max_relay_size.log
== e:/var-ps_row-101/tmp/analyze-sync_with_master
-mysqld.1.err ==
== e:/var-ps_row-101/tmp/analyze-sync_with_master
-mysqld.2.err ==
- saving 'e:/var-ps_row-101/log/rpl.rpl_row_max_relay_size/' to 'e:/var-ps_row-101/log/rpl.rpl_row_max_relay_size/'
Retrying test, attempt(2/3)...
cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/sql/release/mysqld.exe
cygpath -m e:/var-ps_row-101/mysqld.1/mysqld.err
cygpath -m e:/var-ps_row-101/mysqld.1/mysqld.err
cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/sql/release/mysqld.exe
cygpath -m e:/var-ps_row-101/mysqld.2/mysqld.err
cygpath -m e:/var-ps_row-101/mysqld.2/mysqld.err
cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/client/release//mysqltest.exe
cygpath -m e:/var-ps_row-101/tmp/check-mysqld.1.err
cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/client/release//mysqltest.exe
cygpath -m e:/var-ps_row-101/tmp/check-mysqld.2.err
cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/client/release//mysqltest.exe
cygpath -m e:/var-ps_row-101/log/current_test
How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-5.1-rpl&order=39 vm-win2003-64-b/ps_row
has only failed here, according to xref:
http://tinyurl.com/5rbw2y
Description: pushbuild failure: rpl.rpl_row_max_relay_size [ fail ] CURRENT_TEST: rpl.rpl_row_max_relay_size === SHOW MASTER STATUS === ---- 1. ---- File slave-bin.000042 Position 818 Binlog_Do_DB Binlog_Ignore_DB ========================== === SHOW SLAVE STATUS === ---- 1. ---- Slave_IO_State Queueing master event to the relay log Master_Host 127.0.0.1 Master_User root Master_Port 11010 Connect_Retry 1 Master_Log_File master-bin.000001 Read_Master_Log_Pos 20120 Relay_Log_File slave-relay-bin.000003 Relay_Log_Pos 18446744073697230938 Relay_Master_Log_File master-bin.000001 Slave_IO_Running Yes Slave_SQL_Running No Replicate_Do_DB Replicate_Ignore_DB Replicate_Do_Table Replicate_Ignore_Table Replicate_Wild_Do_Table Replicate_Wild_Ignore_Table Last_Errno 1594 Last_Error Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Skip_Counter 0 Exec_Master_Log_Pos 4 Relay_Log_Space 20935 Until_Condition None Until_Log_File Until_Log_Pos 0 Master_SSL_Allowed No Master_SSL_CA_File Master_SSL_CA_Path Master_SSL_Cert Master_SSL_Cipher Master_SSL_Key Seconds_Behind_Master Master_SSL_Verify_Server_Cert No Last_IO_Errno 0 Last_IO_Error Last_SQL_Errno 1594 Last_SQL_Error Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. ========================= === SHOW PROCESSLIST === ---- 1. ---- Id 2 User root Host localhost:1530 db test Command Query Time 0 State Info SHOW PROCESSLIST ---- 2. ---- Id 3 User root Host localhost:1531 db test Command Sleep Time 2 State Info ---- 3. ---- Id 10 User system user Host db Command Connect Time 0 State Queueing master event to the relay log Info ---- 4. ---- Id 11 User system user Host db Command Connect Time 0 State Waiting for slave mutex on exit Info ======================== analyze: sync_with_master mysqltest: In included file ".\extra\rpl_tests\rpl_max_relay_size.test": At line 69: sync_with_master failed: 'select master_pos_wait('master-bin.000001', 169868, 300)' returned NULL indicating slave SQL thread failure The result from queries just before the failure was: < snip > Master_SSL_CA_File Master_SSL_CA_Path Master_SSL_Cert Master_SSL_Cipher Master_SSL_Key Seconds_Behind_Master # Master_SSL_Verify_Server_Cert No Last_IO_Errno # Last_IO_Error # Last_SQL_Errno 0 Last_SQL_Error # # Test 3: max_relay_log_size = 0 # stop slave; reset slave; set global max_relay_log_size=0; select @@global.max_relay_log_size; @@global.max_relay_log_size 0 start slave; More results from queries before failure can be found in e:\var-ps_row-101\log\rpl_row_max_relay_size.log == e:/var-ps_row-101/tmp/analyze-sync_with_master -mysqld.1.err == == e:/var-ps_row-101/tmp/analyze-sync_with_master -mysqld.2.err == - saving 'e:/var-ps_row-101/log/rpl.rpl_row_max_relay_size/' to 'e:/var-ps_row-101/log/rpl.rpl_row_max_relay_size/' Retrying test, attempt(2/3)... cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/sql/release/mysqld.exe cygpath -m e:/var-ps_row-101/mysqld.1/mysqld.err cygpath -m e:/var-ps_row-101/mysqld.1/mysqld.err cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/sql/release/mysqld.exe cygpath -m e:/var-ps_row-101/mysqld.2/mysqld.err cygpath -m e:/var-ps_row-101/mysqld.2/mysqld.err cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/client/release//mysqltest.exe cygpath -m e:/var-ps_row-101/tmp/check-mysqld.1.err cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/client/release//mysqltest.exe cygpath -m e:/var-ps_row-101/tmp/check-mysqld.2.err cygpath -m C:/cygwin/home/pushbuild/pb1/pb/bzr_mysql-5.1-rpl/39/mysql-5.1.28-pb39/client/release//mysqltest.exe cygpath -m e:/var-ps_row-101/log/current_test How to repeat: https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-5.1-rpl&order=39 vm-win2003-64-b/ps_row has only failed here, according to xref: http://tinyurl.com/5rbw2y