Description:
The failure signs include crashes like
https://central.sun.net/http://pb2.norway.sun.com/?template=mysql_show_test_failure&test_f...
pl.rpl_backup_multi [ fail ]
Test ended at 2010-01-08 02:23:03
CURRENT_TEST: rpl.rpl_backup_multi
Server [mysqld.2 - pid: 12248, winpid: 12248, exit: 256] failed during test run
Server log from this test:
100108 4:22:56 [Note] Plugin 'FEDERATED' is disabled.
100108 4:22:56 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
100108 4:22:56 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
100108 4:22:57 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
100108 4:22:58 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
100108 4:22:59 InnoDB Plugin 1.0.5 started; log sequence number 0
100108 4:22:59 [Warning] /export/home/pb2/test/sb_0-1161284-1262907881.47/mysql-5.6.0-beta-linux-x86_64-test/libexec/mysqld: unknown variable 'loose-debug-sync-timeout=300'
100108 4:22:59 [Note] Event Scheduler: Loaded 0 events
100108 4:22:59 [Note] /export/home/pb2/test/sb_0-1161284-1262907881.47/mysql-5.6.0-beta-linux-x86_64-test/libexec/mysqld: ready for connections.
Version: '5.6.0-beta-log' socket: '/export/home/pb2/test/sb_0-1161284-1262907881.47/tmp/3rgM0WfMOS/mysqld.2.sock' port: 13001 Source distribution
100108 4:22:59 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem.
100108 4:22:59 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:13000',replication started in log 'FIRST' at position 4
100108 4:22:59 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './mysqld-relay-bin.000001' position: 4
100108 4:22:59 [Note] Slave I/O thread killed while reading event
100108 4:22:59 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.000001', position 107
100108 4:22:59 [Note] Slave SQL thread exiting, replication stopped in log 'mysqld-bin.000001' at position 107
100108 4:23:00 [Note] Start binlog_dump to slave_server(3), pos(mysqld-bin.000001, 4)
100108 4:23:00 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:13000',replication started in log 'mysqld-bin.000001' at position 4
100108 4:23:01 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.000001' at position 4, relay log './mysqld-relay-bin.000001' position: 4
100108 4:23:02 [Note] Backup: Starting backup process
100108 4:23:02 [Note] Backup: Backing up 2 database(s) `db1`,`db2`
100108 4:23:02 [Note] Backup: Backup completed
100108 4:23:03 - 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.
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=3
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60652 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x134c51a0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x415c70e8 thread_stack 0x40000
and
result mismatch like
https://central.sun.net/http://pb2.norway.sun.com/?template=mysql_show_test_failure&test_f...
rpl.rpl_backup_multi [ fail ]
Test ended at 2010-01-08 06:05:37
CURRENT_TEST: rpl.rpl_backup_multi
--- /export/home2/pb2/test/sb_1-1161308-1262922187.43/mysql-5.6.0-beta-solaris10-x86_64-test/mysql-test/suite/rpl/r/rpl_backup_multi.result 2010-01-08 02:55:44.000000000 +0300
+++ /export/home2/pb2/test/sb_1-1161308-1262922187.43/mysql-5.6.0-beta-solaris10-x86_64-test/mysql-test/suite/rpl/r/rpl_backup_multi.reject 2010-01-08 08:05:37.719137000 +0300
@@ -377,7 +377,7 @@
# Show the incident event issued as a result of restore. This will cause
# slave1 and slave3 to stop. slave2 will function normally
Log_name Pos Event_type Server_id End_log_pos Info
-mysqld-bin.000001 # Incident 1 # #2 (RESTORE_ON_MASTER)
+mysqld-bin.000001 # Incident 1 # #2 (¾)
mysqld-bin.000001 # Rotate 1 # mysqld-bin.000002;pos=4
How to repeat:
To run the test or to see PB2.