Description:
see below
How to repeat:
CURRENT_TEST: rpl_stm_000001
060413 10:39:58 [Warning] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: u
nknown variable 'loose-binlog-show-xid=0'
060413 10:39:58 [Warning] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: u
nknown variable 'loose-binlog-show-xid=0'
060413 10:39:59 InnoDB: Started; log sequence number 0 860664
060413 10:39:59 [Note] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: read
y for connections.
Version: '5.1.10-beta-standard-max-log' socket: '/tmp/pbtmp-n_stm-5/slave.sock' port: 10052 MySQL Pushbuild Edition
060413 10:39:59 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/tmp/var-n_stm-5/log/slave-relay-bin.000001' pos
ition: 4
060413 10:39:59 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:10050', replication started in log 'FIRST' at position 4
060413 10:39:59 [Note] Slave I/O thread killed while reading event
060413 10:39:59 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1814
060413 10:39:59 [Note] Error reading relay log event: slave SQL thread was killed
060413 10:39:59 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 1814, relay log '/tmp/var-n_stm-5/log/slave-relay-
bin.000003' position: 1956
060413 10:39:59 [ERROR] Slave I/O thread: error connecting to master 'root@127.0.0.1:10050': Error: 'Access denied for user 'root'@'localhost' (using password: NO)
' errno: 1045 retry-time: 1 retries: 10
060413 10:40:02 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:10050', replication started in log 'master-bin.000001' at position 1814
060413 10:40:04 [Note] Slave I/O thread killed while reading event
060413 10:40:04 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 2412
060413 10:40:04 [Note] Error reading relay log event: slave SQL thread was killed
060413 10:40:04 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/tmp/var-n_stm-5/log/slave-relay-bin.000001' pos
ition: 4
060413 10:40:04 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:10050', replication started in log 'FIRST' at position 4
060413 10:40:10 [ERROR] Slave: Query partially completed on the master (error on master: 1053) and was aborted. There is a chance that your master is inconsistent
at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; ST
ART SLAVE; . Query: 'update t1 set n = n + get_lock('crash_lock%20C', 2)', Error_code: 1053
060413 10:40:10 [ERROR] Slave (additional info): Unknown error Error_code: 1105
060413 10:40:10 [Warning] Slave: Unknown error Error_code: 1105
060413 10:40:10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mas
ter-bin.000001' position 449399
060413 10:40:10 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 449399, relay log '/tmp/var-n_stm-5/log/slave-rela
y-bin.000003' position: 449541
060413 10:40:10 [Note] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: Norm
al shutdown
060413 10:40:10 [Note] Slave I/O thread killed while reading event
060413 10:40:10 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 450441
060413 10:40:10 [Note] Error reading relay log event: slave SQL thread was killed
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
Description: see below How to repeat: CURRENT_TEST: rpl_stm_000001 060413 10:39:58 [Warning] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: u nknown variable 'loose-binlog-show-xid=0' 060413 10:39:58 [Warning] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: u nknown variable 'loose-binlog-show-xid=0' 060413 10:39:59 InnoDB: Started; log sequence number 0 860664 060413 10:39:59 [Note] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: read y for connections. Version: '5.1.10-beta-standard-max-log' socket: '/tmp/pbtmp-n_stm-5/slave.sock' port: 10052 MySQL Pushbuild Edition 060413 10:39:59 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/tmp/var-n_stm-5/log/slave-relay-bin.000001' pos ition: 4 060413 10:39:59 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:10050', replication started in log 'FIRST' at position 4 060413 10:39:59 [Note] Slave I/O thread killed while reading event 060413 10:39:59 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1814 060413 10:39:59 [Note] Error reading relay log event: slave SQL thread was killed 060413 10:39:59 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 1814, relay log '/tmp/var-n_stm-5/log/slave-relay- bin.000003' position: 1956 060413 10:39:59 [ERROR] Slave I/O thread: error connecting to master 'root@127.0.0.1:10050': Error: 'Access denied for user 'root'@'localhost' (using password: NO) ' errno: 1045 retry-time: 1 retries: 10 060413 10:40:02 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:10050', replication started in log 'master-bin.000001' at position 1814 060413 10:40:04 [Note] Slave I/O thread killed while reading event 060413 10:40:04 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 2412 060413 10:40:04 [Note] Error reading relay log event: slave SQL thread was killed 060413 10:40:04 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '/tmp/var-n_stm-5/log/slave-relay-bin.000001' pos ition: 4 060413 10:40:04 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:10050', replication started in log 'FIRST' at position 4 060413 10:40:10 [ERROR] Slave: Query partially completed on the master (error on master: 1053) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; ST ART SLAVE; . Query: 'update t1 set n = n + get_lock('crash_lock%20C', 2)', Error_code: 1053 060413 10:40:10 [ERROR] Slave (additional info): Unknown error Error_code: 1105 060413 10:40:10 [Warning] Slave: Unknown error Error_code: 1105 060413 10:40:10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mas ter-bin.000001' position 449399 060413 10:40:10 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 449399, relay log '/tmp/var-n_stm-5/log/slave-rela y-bin.000003' position: 449541 060413 10:40:10 [Note] /export/home/mysqldev/pb/mysql-5.1-new-ndb/push-tomas@poseidon.ndb.mysql.com-20060413074548.info/mysql-5.1.10-beta-standard/sql/mysqld: Norm al shutdown 060413 10:40:10 [Note] Slave I/O thread killed while reading event 060413 10:40:10 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 450441 060413 10:40:10 [Note] Error reading relay log event: slave SQL thread was killed mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.