- discuss - lists.mariadb.org

[Maria-discuss] 10.1.21 - tests: main.analyze_format_json w4 [ fail ]
by Reindl Harald 26 Jan '17

26 Jan '17

main.analyze_format_json w4 [ fail ] Test ended at 2017-01-21 16:23:31 CURRENT_TEST: main.analyze_format_json --- /usr/share/mysql-test/r/analyze_format_json.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/analyze_format_json.reject 2017-01-21 16:23:31.740853974 +0100 @@ -455,7 +455,7 @@ "r_loops": 1, "rows": 10, "r_rows": 10, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-4, "filtered": 100, "r_filtered": 20, "attached_condition": "(tbl2.a in (2,3))" mysqltest: Result length mismatch

2 1

[Maria-discuss] question about generating logs on MariaDB 10.1.21
by Chris Adams 25 Jan '17

25 Jan '17

Hello, I have just moved from a MySQL 5.6 server on CentOS 6.8 to a MariaDB 10.1.21 server on CentOS 7. It is installed and working. I would like to set up some logging, but it has not gone as expected. I have binary logging working. However, I can't generate general logs or error logs. Here is part of the /etc/my.cnf file: user=mysql port = 3306 socket = /var/lib/mysql/mysql.sock datadir = /mnt/mysqldbs log_error = /var/log/mysql/error.log general_log_file = /var/log/mysql/mysql.log general_log = 1 log_bin = /mnt/mysqldbs/logs/mysql-bin I assume that after a restart, the logs will be generated, then logged to as events happen. As it is, no log files are generated. Many thanks.

4 7

[Maria-discuss] MariaDB 10.1.x: tablespace does not exist or is just being dropped
by Reindl Harald 23 Jan '17

23 Jan '17

Hi that crap temp files never deleted are from years ago and a crash until now it was enough to keep that tempfiles, with 10.1.x mariadb don't start at all - *how to get rid of that crap* the idiotic warnings are one thing but the segfauls now... it's about a decade that it's not possible to cleanup such stuff http://grokbase.com/t/mysql/mysql/136kx5qp1w/how-can-i-drop-a-table-that-is… 2017-01-23 22:01:27 139913013700928 [ERROR] InnoDB: Trying to do i/o to a tablespace which exists without .ibd data file. i/o type 10, space id 545, page no 0, i/o length 8192 bytes 2017-01-23 22:01:27 7f40097b2940 InnoDB: Error: trying to access tablespace 545 page no. 0, InnoDB: but the tablespace does not exist or is just being dropped. 2017-01-23 22:01:27 139913013700928 [ERROR] InnoDB: tablespace id is 545 in the data dictionary but in file ./dbmail/#sql2-704-271.ibd it is 690! 2017-01-23 22:01:31 140380157278528 [ERROR] InnoDB: Trying to do i/o to a tablespace which exists without .ibd data file. i/o type 10, space id 545, page no 0, i/o length 8192 bytes 2017-01-23 22:01:31 7faccd687940 InnoDB: Error: trying to access tablespace 545 page no. 0, InnoDB: but the tablespace does not exist or is just being dropped. InnoDB: Error: Unable to read tablespace 545 page no 0 into the buffer pool after 100 attempts InnoDB: The most probable cause of this error may be that the table has been corrupted. InnoDB: You can try to fix this problem by using innodb_force_recovery. InnoDB: Please see reference manual for more details. InnoDB: Aborting... 2017-01-23 22:01:31 7faccd687940 InnoDB: Assertion failure in thread 140380157278528 in file buf0buf.cc line 3080 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170123 22:01:31 [ERROR] mysqld got signal 6 ; 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.1.21-MariaDB key_buffer_size=33554432 read_buffer_size=131072 max_used_connections=0 max_threads=52 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 53739 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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 = 0x0 thread_stack 0x48400 /usr/libexec/mysqld(my_print_stacktrace+0x29)[0x560568d7a139] /usr/libexec/mysqld(handle_fatal_signal+0x3ad)[0x5605689d780d] /lib64/libpthread.so.0(+0x10c30)[0x7faccb39cc30] /lib64/libc.so.6(gsignal+0x35)[0x7faccaffe765] /lib64/libc.so.6(abort+0x16a)[0x7faccb00036a] /usr/libexec/mysqld(+0x80a9b9)[0x560568cce9b9] /usr/libexec/mysqld(+0x85426d)[0x560568d1826d] /usr/libexec/mysqld(+0x8593ca)[0x560568d1d3ca] /usr/libexec/mysqld(+0x8440b8)[0x560568d080b8] /usr/libexec/mysqld(+0x7b8978)[0x560568c7c978] /usr/libexec/mysqld(+0x702902)[0x560568bc6902] /usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x5d)[0x5605689d999d] /usr/libexec/mysqld(+0x3dddfb)[0x5605688a1dfb] /usr/libexec/mysqld(_Z11plugin_initPiPPci+0x782)[0x5605688a2c32] /usr/libexec/mysqld(+0x353e75)[0x560568817e75] /usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x35f)[0x56056881c1ef] /lib64/libc.so.6(__libc_start_main+0xf1)[0x7faccafea731] /usr/libexec/mysqld(_start+0x29)[0x560568812eb9] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.

1 3

[Maria-discuss] 10.1.21 - tests: main.analyze_stmt_orderby 'xtradb' w4 [ fail ]
by Reindl Harald 23 Jan '17

23 Jan '17

main.analyze_stmt_orderby 'xtradb' w4 [ fail ] Test ended at 2017-01-21 18:43:58 CURRENT_TEST: main.analyze_stmt_orderby --- /usr/share/mysql-test/r/analyze_stmt_orderby.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/analyze_stmt_orderby.reject 2017-01-21 18:43:58.130938437 +0100 @@ -417,7 +417,7 @@ "r_loops": 1, "rows": 10, "r_rows": 10, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-3, "filtered": 100, "r_filtered": 100 }, @@ -486,7 +486,7 @@ "r_loops": 1, "rows": 7, "r_rows": 7, - "r_total_time_ms": "REPLACED", + "r_total_time_ms": "REPLACED"e-4, "filtered": 100, "r_filtered": 100 }, mysqltest: Result length mismatch

2 2

[Maria-discuss] LTO build fails likely because -static-libgcc
by Reindl Harald 22 Jan '17

22 Jan '17

why does MariaDB use "-g -static-libgcc" in "mysql_release.cmake" and so besides override -g0 break -flto builds?

2 4

[Maria-discuss] 10.1.21 - tests: main.multi_update 'xtradb' w8 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

i guess that below makes not much sense when running with "--binlog-format=row" /mysql-test-run.pl --parallel=8 --max-test-fail=0 --mysqld=--binlog-format=row main.multi_update 'xtradb' w8 [ fail ] Test ended at 2017-01-21 18:43:50 CURRENT_TEST: main.multi_update --- /usr/share/mysql-test/r/multi_update.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/multi_update.reject 2017-01-21 18:43:49.979037948 +0100 @@ -1055,7 +1055,6 @@ Warnings: Warning 1264 Out of range value for column 'field1' at row 1 Warning 1264 Out of range value for column 'field1' at row 2 -Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. UPDATE (SELECT 128 as col1) x, table_11757486 SET field1=x.col1; ERROR 22003: Out of range value for column 'field1' at row 1 UPDATE table_11757486 SET field1=128; @@ -1069,7 +1068,6 @@ Warnings: Warning 1264 Out of range value for column 'field1' at row 1 Warning 1264 Out of range value for column 'field1' at row 2 -Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave. DROP TABLE table_11757486; SET SESSION SQL_MODE=default; end of 10.0 tests mysqltest: Result length mismatch

1 0

[Maria-discuss] for years failing tests
by Reindl Harald 21 Jan '17

21 Jan '17

shouldn't the testsuite at some point in time run without errors? "run STOP SLAVE '' first" - uhm did i start it? it's scripted by shipped scripts [root@testserver:~]$ cat /usr/local/bin/mysql-test.sh #!/usr/bin/dash /usr/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --parallel=1 --max-test-fail=0 --mysqld=--binlog-format=mixed --force' mysql rm -rf /usr/share/mysql-test/var/* rpl.rpl_binlog_index 'row' [ fail ] Test ended at 2017-01-20 16:56:16 CURRENT_TEST: rpl.rpl_binlog_index mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/rpl_binlog_index.test at line 20: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc - saving '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' to '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' rpl.sec_behind_master-5114 'stmt' [ fail ] Test ended at 2017-01-20 16:58:33 CURRENT_TEST: rpl.sec_behind_master-5114 mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/sec_behind_master-5114.test at line 1: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ] Test ended at 2017-01-20 16:59:24 CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync mysqltest: At line 1: query 'set global rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system variable 'rpl_semi_sync_master_wait_point' The result from queries just before the failure was: set global rpl_semi_sync_master_wait_point=AFTER_SYNC; - saving '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/' to '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/'

3 11

[Maria-discuss] 10.1.21 - tests: main.compound w5 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.compound w5 [ fail ] Test ended at 2017-01-21 16:21:47 CURRENT_TEST: main.compound --- /usr/share/mysql-test/r/compound.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/compound.reject 2017-01-21 16:21:47.413144793 +0100 @@ -28,13 +28,16 @@ include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (4) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (5) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; INSERT INTO t1 VALUES (6) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT DROP TABLE t1| CREATE DATABASE mysqltest1| @@ -144,12 +147,17 @@ execute stmt using @a, @b, @c| include/show_binlog_events.inc Log_name Pos Event_type Server_id End_log_pos Info -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(9) -master-bin.000001 # Gtid # # GTID #-#-# -master-bin.000001 # Query # # use `test`; SELECT `test`.`fn`(1) master-bin.000001 # Gtid # # BEGIN GTID #-#-# -master-bin.000001 # Query # # use `test`; insert t1 values( NAME_CONST('a',4)+3) +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F +master-bin.000001 # Query # # COMMIT +master-bin.000001 # Gtid # # BEGIN GTID #-#-# +master-bin.000001 # Table_map # # table_id: # (test.t1) +master-bin.000001 # Write_rows_v1 # # table_id: # flags: STMT_END_F master-bin.000001 # Query # # COMMIT drop function fn| drop table t1| mysqltest: Result length mismatch

1 0

[Maria-discuss] 10.1.21 - tests: main.commit_1innodb 'xtradb' w6 [ fail ]
by Reindl Harald 21 Jan '17

21 Jan '17

main.commit_1innodb 'xtradb' w6 [ fail ] Test ended at 2017-01-21 16:21:39 CURRENT_TEST: main.commit_1innodb --- /usr/share/mysql-test/r/commit_1innodb.result 2017-01-17 20:38:20.000000000 +0100 +++ /usr/share/mysql-test/r/commit_1innodb.reject 2017-01-21 16:21:39.268245094 +0100 @@ -710,12 +710,12 @@ # drop temporary table t2; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 commit; call p_verify_status_increment(1, 0, 1, 0); -SUCCESS - +ERROR +Expected commit increment: 1 actual: 0 # 26. Verify that SET AUTOCOMMIT issues an implicit commit # insert t1 set a=3; @@ -831,8 +831,8 @@ Note 1050 Table 't2' already exists # Sic: first commits the statement, and then the transaction. call p_verify_status_increment(0, 0, 0, 0); -SUCCESS - +ERROR +Expected commit increment: 0 actual: 2 create table t3 select a from t2; call p_verify_status_increment(2, 0, 4, 4); SUCCESS mysqltest: Result length mismatch

1 0

[Maria-discuss] what about cleanly deprecation of config options
by Reindl Harald 20 Jan '17

20 Jan '17

what about spit some warnings in 10.0.x releases instead after update to 10.1.x service not starting and you can look what confdig options needs to be removed 2017-01-20 16:34:36 140555676232000 [ERROR] /usr/libexec/mysqld: unknown option '--skip-federated' 2017-01-20 16:34:36 140555676232000 [ERROR] Aborting

3 9