Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Incomplete
-
10.0.22
-
None
Description
In Debian, the builds for the unofficial alpha platform fails due to failing test:
rpl.rpl_skip_replication 'innodb_plugin,stmt' w3 [ fail ]
|
Test ended at 2015-12-11 03:35:25
|
|
|
CURRENT_TEST: rpl.rpl_skip_replication
|
=== SHOW MASTER STATUS ===
|
---- 1. ----
|
File slave-bin.000001
|
Position 1493
|
Binlog_Do_DB
|
Binlog_Ignore_DB
|
==========================
|
|
|
=== SHOW SLAVE STATUS ===
|
---- 1. ----
|
Slave_IO_State Connecting to master
|
Master_Host 127.0.0.1
|
Master_User root
|
Master_Port 16040
|
Connect_Retry 1
|
Master_Log_File master-bin.000005
|
Read_Master_Log_Pos 367
|
Relay_Log_File slave-relay-bin.000012
|
Relay_Log_Pos 655
|
Relay_Master_Log_File master-bin.000005
|
Slave_IO_Running Connecting
|
Slave_SQL_Running Yes
|
Replicate_Do_DB
|
Replicate_Ignore_DB
|
Replicate_Do_Table
|
Replicate_Ignore_Table
|
Replicate_Wild_Do_Table
|
Replicate_Wild_Ignore_Table
|
Last_Errno 0
|
Last_Error
|
Skip_Counter 0
|
Exec_Master_Log_Pos 367
|
Relay_Log_Space 996
|
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 0
|
Last_SQL_Error
|
Replicate_Ignore_Server_Ids
|
Master_Server_Id 1
|
Master_SSL_Crl
|
Master_SSL_Crlpath
|
Using_Gtid No
|
Gtid_IO_Pos
|
=========================
|
|
|
=== SHOW PROCESSLIST ===
|
---- 1. ----
|
Id 22
|
User root
|
Host localhost:40264
|
db test
|
Command Sleep
|
Time 303
|
State
|
Info
|
Progress 0.000
|
---- 2. ----
|
Id 23
|
User root
|
Host localhost:40266
|
db test
|
Command Sleep
|
Time 303
|
State
|
Info
|
Progress 0.000
|
---- 3. ----
|
Id 26
|
User root
|
Host localhost:40278
|
db test
|
Command Query
|
Time 0
|
State init
|
Info SHOW PROCESSLIST
|
Progress 0.000
|
---- 4. ----
|
Id 27
|
User root
|
Host localhost:40280
|
db test
|
Command Sleep
|
Time 303
|
State
|
Info
|
Progress 0.000
|
---- 5. ----
|
Id 33
|
User system user
|
Host
|
db
|
Command Connect
|
Time 300
|
State Connecting to master
|
Info
|
Progress 0.000
|
---- 6. ----
|
Id 34
|
User system user
|
Host
|
db
|
Command Connect
|
Time 300
|
State Slave has read all relay log; waiting for the slave I/O thread to update it
|
Info
|
Progress 0.000
|
========================
|
|
|
analyze: sync_with_master
|
mysqltest: At line 106: sync_slave_with_master failed: 'select master_pos_wait('master-bin.000005', 721, 300, '')' returned -1 indicating timeout after 300 seconds
|
|
|
The result from queries just before the failure was:
|
< snip >
|
INSERT INTO t2(a) VALUES (3);
|
FLUSH NO_WRITE_TO_BINLOG LOGS;
|
SHOW TABLES;
|
Tables_in_test
|
t1
|
t2
|
SELECT * FROM t1;
|
a b
|
1 NULL
|
SELECT * FROM t2;
|
a b
|
1 NULL
|
DROP TABLE t3;
|
FLUSH NO_WRITE_TO_BINLOG LOGS;
|
STOP SLAVE;
|
SET GLOBAL replicate_events_marked_for_skip=REPLICATE;
|
START SLAVE;
|
SET skip_replication=1;
|
CREATE TABLE t3 (a INT PRIMARY KEY, b INT) ENGINE=myisam;
|
INSERT INTO t3(a) VALUES(2);
|
|
|
More results from queries before failure can be found in /«PKGBUILDDIR»/builddir/mysql-test/var/3/log/rpl_skip_replication.log
|
|
|
|
|
== /«PKGBUILDDIR»/builddir/mysql-test/var/3/tmp/analyze-sync_with_master-mysqld.1.err ==
|
|
|
############################## default ##############################
|
|
|
**** SHOW WARNINGS on default ****
|
SHOW WARNINGS;
|
Level Code Message
|
|
|
**** SELECT replication-related variables on default ****
|
SELECT NOW(), @@SERVER_ID;
|
NOW() @@SERVER_ID
|
2015-12-11 03:33:24 1
|
|
|
**** SHOW SLAVE STATUS on default ****
|
SHOW SLAVE STATUS;
|
|
|
**** SHOW MASTER STATUS on default ****
|
SHOW MASTER STATUS;
|
File master-bin.000005
|
Position 721
|
Binlog_Do_DB
|
Binlog_Ignore_DB
|
|
|
**** SHOW SLAVE HOSTS on default ****
|
SHOW SLAVE HOSTS;
|
|
|
**** SHOW PROCESSLIST on default ****
|
SHOW PROCESSLIST;
|
Id User Host db Command Time State Info Progress
|
30 root localhost NULL Query 0 init SHOW PROCESSLIST 0.000
|
|
|
**** SHOW BINARY LOGS on default ****
|
SHOW BINARY LOGS;
|
Log_name File_size
|
master-bin.000001 1536
|
master-bin.000002 553
|
master-bin.000003 922
|
master-bin.000004 553
|
master-bin.000005 721
|
|
|
**** SHOW BINLOG EVENTS on default ****
|
binlog_name = 'master-bin.000005'
|
SHOW BINLOG EVENTS IN 'master-bin.000005';
|
Log_name Pos Event_type Server_id End_log_pos Info
|
master-bin.000005 4 Format_desc 1 248 Server ver: 10.0.22-MariaDB-2-log, Binlog ver: 4
|
master-bin.000005 248 Gtid_list 1 287 [0-1-12]
|
master-bin.000005 287 Binlog_checkpoint 1 327 master-bin.000004
|
master-bin.000005 327 Binlog_checkpoint 1 367 master-bin.000005
|
master-bin.000005 367 Gtid 1 405 GTID 0-1-13
|
master-bin.000005 405 Query 1 524 use `test`; CREATE TABLE t3 (a INT PRIMARY KEY, b INT) ENGINE=myisam
|
master-bin.000005 524 Gtid 1 562 BEGIN GTID 0-1-14
|
master-bin.000005 562 Query 1 652 use `test`; INSERT INTO t3(a) VALUES(2)
|
master-bin.000005 652 Query 1 721 COMMIT
|
|
|
**** SHOW RELAYLOG EVENTS on default ****
|
relaylog_name = 'No such row'
|
SHOW RELAYLOG EVENTS IN 'No such row';
|
Log_name Pos Event_type Server_id End_log_pos Info
|
|
|
== /«PKGBUILDDIR»/builddir/mysql-test/var/3/tmp/analyze-sync_with_master-mysqld.2.err ==
|
mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL server at 'waiting for initial communication packet', system error: 60 "Connection timed out"
|
|
|
|
|
|
|
- saving '/«PKGBUILDDIR»/builddir/mysql-test/var/3/log/rpl.rpl_skip_replication-innodb_plugin,stmt/' to '/«PKGBUILDDIR»/builddir/mysql-test/var/log/rpl.rpl_skip_replication-innodb_plugin,stmt/'
|
|
|
Retrying test rpl.rpl_skip_replication, attempt(2/3)...
|
|
|
***Warnings generated in error logs during shutdown after running tests: rpl.rpl_skip_replication rpl.rpl_relay_space_innodb rpl.rpl_savepoint
|
|
|
151211 3:28:24 [ERROR] mysqld got signal 11 ;
|
Attempting backtrace. You can use the following information to find out
|
InnoDB: Warning: semaphore wait:
|
InnoDB: Warning: semaphore wait:
|
InnoDB: Warning: semaphore wait:
|
Full log at https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0&arch=alpha&ver=10.0.22-2&stamp=1449822712
This issue is very minor, I don't expect anybody to fix it unless the fix is very easy or if somebody anywhere ever actually is found to be using Alpha machines.
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
Re-opening – if we have to mark the test as unstable, we can't just close the report.
cvicentiu, could you please check if it's still valid, and close if it's not? Thanks
The only alpha build I can find now is this 40-day-old 10.6 on Sid
https://buildd.debian.org/status/logs.php?pkg=mariadb-10.6&ver=1%3A10.6.10-1&arch=alpha
and it didn't build, so no MTR was run.
MariaDB 10.5 a year ago still built on Alpha:
https://buildd.debian.org/status/logs.php?pkg=mariadb-10.5
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5&arch=alpha&ver=1%3A10.5.12-1&stamp=1628596323&raw=0
While Alpha is an esoteric architecture, mistakes that break cross-arch builds are typically due to misuse of C++ syntax/concepts and fixing them usually benefits all architectures.
This also looks like a server crash, possibly the same as in
MDEV-9269(because both seem to happen upon establishing connection to the server).Since both tests are disabled, there is no telling whether it was a one-time issue or it's persistent.
We need access to the machine if we want to investigate it.