- discuss - lists.mariadb.org

[Maria-discuss] innodb and corrupted tables
by Federico Razzoli 20 Nov '17

20 Nov '17

I just noticed this old MySQL bug:https://bugs.mysql.com/bug.php?id=10132 In the comments (2005 to 2014) everyone seems to agree that current behaviour should be treated as a bug.The main commenter now works for MariaDB.What is currently your opinion? Will this behaviour change at some point? If so, what will be the consequences for Galera? Federico

3 3

[Maria-discuss] MariaDB GUI: BSL 1.1 - Debate
by Juan Telleria 19 Nov '17

19 Nov '17

Dear MariaDb Developers, I am writing because I would like to open a debate whether if MariaDB, now that has gained investment from Microsoft, Alibaba, and the European Union, shall create its own SQL Graphical User Interface, as good as (or better than) MySQL Workbench. I agree that MariaDB includes by default HeidiSQL in its Windows builds, but in my opinion, if MariaDB really wants to look Oracle's MySQL face to face, HeidiSQL is not nearly as good as MySQL Workbench. If this wants to be done: 1st) The brand new GUI shall have a Business Source Licence v1.1, which only companies which invest in MariaDB would be able to use. 2nd) In 3 years now, MariaDB would be better positioned and have a fully Open Source GUI which would allow MariaDB to look face to face to Oracle. 3rd) And in 4/5 years now, MariaDB Corporation shall be brave enough to to continue Developing this GUI as a truly open source product, without the BSL, and adopting a purely GPLv2 with incremental improvements, distributing it through the MariaDB Foundation Webpage, as individuals or other companies apart from MariaDB Corporation, will not support the product if it is not totally Open Source. So BSL v1.1 might prove useful to launch the project, but with time, it shall have a GPLv2 for gaining investment from third companies. ¿What do you thing on the topic? Thank you all, Juan Telleria

1 1

[Maria-discuss] MariaDB upgrade 10.1 to 10.2 CentOS7
by Karthick Subramanian 13 Nov '17

13 Nov '17

All, Did anyone face issues after upgrading the mariadb from 10.1 to 10.2 to login to root user as shown below: mysql -u root I got the error - unix_socket not loaded. I noticed that the unix_socket authentication is required after the upgrade for root login from localhost. Can anyone confirm whether this is part of the feature after upgrades. In my previous version: select user, plugin from mysql.user; +-----------+------+-------------+ | Host | User | plugin | +-----------+------+-------------+ | localhost | root | | ------------------------------------ After upgrade: select user, plugin from mysql.user; +-----------+------+-------------+ | Host | User | plugin | +-----------+------+-------------+ | localhost | root | unix_socket | --------------------------------------- Regards, Karthick

3 9

[Maria-discuss] RPM CMake build arguments - Fedora
by Michal Schorm 13 Nov '17

13 Nov '17

Hello everybody, I want to update Fedora SPECfile to the latest best practise. This time, I want to fix CMake arguments. As the time flown, we were adding more and more arguments and for many of them, I'm not sure of their correct values. Are they (the values) ON/OFF? ON/NO? ... I already - incorrectly - filed it as a JIRA issue, but it is nicely formated, so I'd recomment to read it through. https://jira.mariadb.org/browse/MDEV-14344 You can reply to both mail and JIRA, I guess, I'll check them both. -- I'll be glad for any advice on how the values should look like, because reading through the Cmake files is kinda hard and slow for me. -- Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat

3 4

[Maria-discuss] Contributing my ideas with Mariadb
by Rajat Rawat 11 Nov '17

11 Nov '17

Respected Sir/Mam Hello, Myself Rajat from India. I wanted to contribute/work with Mariadb. As we know that Mariadb dosen’t have cascade truncate function available yet, so I want to contribute to Mariadb towards this topic. My topic is “Cascade Truncate”. Since we can’t truncate the parent table unless the referential integrity constraints are present in the child table also. Hence, we can do a way that we can provide a command that truncate the child table as well. This enhancement is already provided in the Oracle Database in their 12c Version, by using the truncate cascade command. It is better to truncate the child table at the time when we want to truncate our parent table. As we know that we have already on Delete Cascade command available, but that command works only row by row and not for all rows at one time. So, at one time if we want to truncate our whole table then Cascade Truncate is a better Option. That’s all about my proposal. If you like my proposal, then let me know about about it. I am very eager to contribute for you. I also forked and downloaded on my local machine, the file of Maraidb which is available on Github, and currently I am reading/understanding all the patches, but I am confused with only 1 thing that from where should I start. So, if you like proposal then let me know about it and please guide me that from where should I start contributing for it. My skills: C, C++, Java, SQL, PL/SQL Achievement: Oracle Certified Associate Java Programmer SE 7. By contributing for you I will definitely learn many new things and implement my ideas, while working with you. Hope I could be of any help for you. Your sincerely Rajat

2 1

[Maria-discuss] slow_query_log: Binlog Dump
by Reindl Harald 05 Nov '17

05 Nov '17

these entries are *not* helpful when you need to seek for real queryies like a needle SET timestamp=1509853561; # administrator command: Binlog Dump; # Time: 171105 4:47:04 # User@Host: replication[replication] @ [192.168.196.106] # Thread_id: 415842 Schema: QC_hit: No # Query_time: 62.807846 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 # Rows_affected: 0 SET timestamp=1509853624; # administrator command: Binlog Dump; # Time: 171105 4:49:04 # User@Host: replication[replication] @ [192.168.196.106] # Thread_id: 415899 Schema: QC_hit: No # Query_time: 120.228237 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 # Rows_affected: 0 SET timestamp=1509853744; # administrator command: Binlog Dump; # Time: 171105 4:51:01 # User@Host: replication[replication] @ [192.168.196.106] # Thread_id: 416036 Schema: QC_hit: No # Query_time: 117.412204 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 # Rows_affected: 0 SET timestamp=1509853861; # administrator command: Binlog Dump; # Time: 171105 4:52:01 # User@Host: replication[replication] @ [192.168.196.106] # Thread_id: 416184 Schema: QC_hit: No # Query_time: 60.132083 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 # Rows_affected: 0 SET timestamp=1509853921; # administrator command: Binlog Dump; # Time: 171105 4:56:01 # User@Host: replication[replication] @ [192.168.196.106] # Thread_id: 416257 Schema: QC_hit: No # Query_time: 240.021180 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 # Rows_affected: 0 SET timestamp=1509854161; # administrator command: Binlog Dump; # Time: 171105 4:58:08 # User@Host: replication[replication] @ [192.168.196.106] # Thread_id: 416567 Schema: QC_hit: No # Query_time: 127.012674 Lock_time: 0.000000 Rows_sent: 1 Rows_examined: 0 # Rows_affected: 0 SET timestamp=1509854288; # administrator command: Binlog Dump;

1 0

[Maria-discuss] Question on building 10.1.26 binary from sources
by Prasad Rallapalli 03 Nov '17

03 Nov '17

Hi, I am trying to build 10.1.26 from mariadb sources and compare the performance with the release binary for the same query on the same database. cmake using -DBUILD_CONFIG=mysql_release resulted in a "jemalloc not found" error. So, I did a cmake without any parameters and the build was successful. The binary which i built has a performance drop of 20-30% for the queries, compared to that of the released binary, for the same queries. I compared both the mysqld binaries. The release binary seems to be accessing jemalloc functions and the mysqld binary which i built do not have these functions. I am building this on Centos 6.8. Any help or pointers will be appreciated. Regards Prasad

3 3

[Maria-discuss] Building 10.2 from source issues
by Guillaume Lefranc 02 Nov '17

02 Nov '17

Hi, I am trying to build 10.2 from sources while disabling some plugins (building with all plugins works without issues). e.g. $ cmake . -DPLUGIN_MROONGA=NO -DPLUGIN_TOKUDB=NO -DPLUGIN_SPHINX=NO -DPLUGIN_ROCKSDB=NO $ make This fails with the following errors: [ 98%] Building CXX object extra/mariabackup/CMakeFiles/mariabackup.dir/changed_page_bitmap.cc.o In file included from /home/tanj/mariadb-10.2/storage/innobase/include/univ.i:83:0, from /home/tanj/mariadb-10.2/storage/innobase/include/ut0rbt.h:29, from /home/tanj/mariadb-10.2/extra/mariabackup/changed_page_bitmap.h:28, from /home/tanj/mariadb-10.2/extra/mariabackup/changed_page_bitmap.cc:25: /home/tanj/mariadb-10.2/extra/mariabackup/common.h: In function ‘size_t xb_read_full(File, uchar*, size_t)’: /home/tanj/mariadb-10.2/extra/mariabackup/common.h:162:45: error: ‘MY_WME’ was not declared in this scope tbytes = my_read(fd, buf, len - tlen, MYF(MY_WME)); ^ /home/tanj/mariadb-10.2/include/my_global.h:1025:24: note: in definition of macro ‘MYF’ #define MYF(v) (myf) (v) ^ In file included from /home/tanj/mariadb-10.2/extra/mariabackup/changed_page_bitmap.cc:27:0: /home/tanj/mariadb-10.2/extra/mariabackup/common.h:162:12: error: ‘my_read’ was not declared in this scope tbytes = my_read(fd, buf, len - tlen, MYF(MY_WME)); ^~~~~~~ /home/tanj/mariadb-10.2/extra/mariabackup/common.h:162:12: note: suggested alternative: ‘my_sha1’ tbytes = my_read(fd, buf, len - tlen, MYF(MY_WME)); ^~~~~~~ my_sha1 /home/tanj/mariadb-10.2/extra/mariabackup/common.h:163:32: error: ‘MY_FILE_ERROR’ was not declared in this scope if (tbytes == 0 || tbytes == MY_FILE_ERROR) { ^~~~~~~~~~~~~ /home/tanj/mariadb-10.2/extra/mariabackup/common.h:163:32: note: suggested alternative: ‘DB_IO_ERROR’ if (tbytes == 0 || tbytes == MY_FILE_ERROR) { ^~~~~~~~~~~~~ DB_IO_ERROR make[2]: *** [extra/mariabackup/CMakeFiles/mariabackup.dir/build.make:111: extra/mariabackup/CMakeFiles/mariabackup.dir/changed_page_bitmap.cc.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [CMakeFiles/Makefile2:4270: extra/mariabackup/CMakeFiles/mariabackup.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 98%] Built target mysqld [ 98%] Built target explain_filename-t make: *** [Makefile:163: all] Error 2 $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc-multilib/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --enable-default-pie --enable-default-ssp Thread model: posix gcc version 7.2.0 (GCC) Please advise. Thanks

2 5

[Maria-discuss] Async replication between two Galera clusters, GTIDs on non slave node in "slave cluster" don't match
by Warner, Paul 02 Nov '17

02 Nov '17

Hi! I have two Galera clusters of three nodes each, let's call them cluster A and cluster B. Cluster B has one member set up as a slave to one of the members in cluster A. The cluster B member that runs the slave protocol shows it's GTID matches that of the nodes in cluster A, but the other two nodes in cluster B (not running slaves themselves, but in the cluster with the node running as a slave) have GTIDs that are always 4 behind the other nodes. So just to lay it out again: A0 5-24-5 - master A1 5-24-5 A2 5-24-5 B0 5-24-5 - slave to A0 B1 5-24-1 B2 5-24-1 The GTIDS stay 4 apart, and replication seems fine. I add rows on any A cluster node and they show up in all three B nodes. The GTID on the node running slave stays in sync with the A cluster. The A0 cluster is set up using xtrabackupv2 for SST. The A cluster is completely up before doing anything on the B cluster. The B cluster is started like: 1. Start B0 as first node in the Galera cluster 2. mysqldump from A0 to B0 with --gtid. <https://gist.github.com/warnerpr/011cabb876600c33e5bee42d7d0b17d2> https://gist.github.com/warnerpr/011cabb876600c33e5bee42d7d0b17d2 3. Master of B0 is set to A0 4. Slave is started on B0 5. B1 and B2 are started and set to join the existing cluster. Cluster A and B have log_slave_updates = ON. Details: B0 Slave - https://gist.github.com/warnerpr/59c287bb201302961742bb89d5035559 B1 - https://gist.github.com/warnerpr/0fb8825e49bce72761e0bdd95b0512d9 A1 Master - https://gist.github.com/warnerpr/91e0df1eb04f425baca3675335639c0f Any pointers are greatly appreciated! Paul

2 1

[Maria-discuss] Current Kernel/Distro with best support for performance/stability for VMs (HyperV)
by Alexandre hadjinlian guerra 01 Nov '17

01 Nov '17

Hi I've been looking for improvements in block device handling / XFS filesystem on linux kernel and it looks like that on Kernel 4.11 there is some interesting improvements Im looking to settle on a newer distro/kernel which supports MariaDB 10.2 and ColumnStore and have a long term support. its a new deployment Thanks

1 0

[Maria-discuss] MariaDB 10.2 'show engine innodb status' format change for Pending AIO
by Jonathan Nicol 31 Oct '17

31 Oct '17

Hi, Starting with 10.2, in 'show engine innodb status', the format has changed for pending reads/writes... The old (pre-5.5) format looked like: Pending normal aio reads: 0, aio writes: 0, In 5.5 it switched to: Pending normal aio reads: 0 [0, 0, 0, 0] , aio writes: 0 [0, 0, 0, 0] , (where each value in the brackets corresponds to a read or write thread) Now in 10.2 it looks like: Pending normal aio reads: [0, 0, 0, 0] , aio writes: [0, 0, 0, 0] , I was never clear on what the values outsides the brackets in 5.5-10.1 represented... assumed it was a total of all threads. We were previously monitoring this value, should we move forward monitoring a sum of all threads? It seems a little odd to remove a useful metric from the status output. thanks Jon

1 0

Re: [Maria-discuss] upgrading from 10.1 -> 10.2 with galera cluster
by Jeff Dyke 31 Oct '17

31 Oct '17

Thanks for the tip, that will be helpful for sure. I'm about to set it up on three aws instances and see what happens. Perhaps i can contribute my learnings to the ticket you opened. Best, Jeff On Tue, Oct 31, 2017 at 2:20 PM, Chris Calender <chris.calender(a)mariadb.com> wrote: > Hi Jeff, > > Be sure you have upgraded Xtrabackup to 2.4, or if one of the 10.2 needs > to SST, it will fail with an "No valid checkpoint found" error (as > Xtrabackup 2.3 is not 100% compatible with MariaDB 10.2): > > https://jira.mariadb.org/browse/MDEV-13657 > > Also, I did file a documentation request about this topic last light, if > interested (though you might have this implemented before the page is > added): > > https://jira.mariadb.org/browse/MDEV-14226 > > Hope this helps. > > Best wishes, > Chris > > > > On 10/31/2017 10:09 AM, Jeff Dyke wrote: > >> I have a 10.1 install of galera cluster running in master master mode, i >> would like to upgrade to 10.2.9, and have seen the instructions here[1] >> about "regular" updates, but i'd like to keep the cluster online while i >> upgrade. Is there any difference or things to look out for to keep data >> consistency. can a 10.2 node replicate to a 10.1 node (my guess would be >> no due to the new fields after mysql_upgrade) Downtime offline is a >> possibility, but i'd like to avoid it, as would anyone. >> >> Any hints/links are greatly appreciated. >> Jeff >> >> [1] https://mariadb.com/kb/en/library/upgrading-from-mariadb- >> 101-to-mariadb-102/ >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> >> > > -- > Chris Calender, M.S., Technical Support Manager > MariaDB Corporation >

1 0

[Maria-discuss] upgrading from 10.1 -> 10.2 with galera cluster
by Jeff Dyke 31 Oct '17

31 Oct '17

I have a 10.1 install of galera cluster running in master master mode, i would like to upgrade to 10.2.9, and have seen the instructions here[1] about "regular" updates, but i'd like to keep the cluster online while i upgrade. Is there any difference or things to look out for to keep data consistency. can a 10.2 node replicate to a 10.1 node (my guess would be no due to the new fields after mysql_upgrade) Downtime offline is a possibility, but i'd like to avoid it, as would anyone. Any hints/links are greatly appreciated. Jeff [1] https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/

1 0

[Maria-discuss] Aria_pack error
by Kenneth Penza 27 Oct '17

27 Oct '17

Good afternoon, I am currently working on MariaDB version 10.1.26-MariaDB-1~yakkety running on Ubuntu 16.10 and have encountered an error whilst using aria_pack. The process used to generate the tables is as follows: 1) create table SQL script 2) shutdown MariaDB (systemctl shutdown mariadb.service) 3 )Disable indexes to speedup loading $ aria_chk --keys-used=0 -rq /var/lib/mysql/mygo/term - recovering (with keycache) Aria-table '/var/lib/mysql/mygo/term' Data records: 0 Table: /var/lib/mysql/mygo/term doesn't have an auto increment key State updated 4) startup MariaDB (systemctl start mariadb.service) 5) load data $ mysqlimport -u penzk001 --password=penzk100 -L mygo term.txt mygo.term: Records: 46032 Deleted: 0 Skipped: 0 Warnings: 0 6) shutdown mariadb (systemctl shutdown mariadb.service) 7) Check table $ aria_chk /var/lib/mysql/mygo/term Checking Aria file: /var/lib/mysql/mygo/term Data records: 46032 Deleted blocks: 0 - check file-size - check key delete-chain - check index reference - check record links State update 8) Compress table $ aria_pack /var/lib/mysql/mygo/term Compressing /var/lib/mysql/mygo/term.MAD: (46032 records) - Calculating statistics - Compressing file Segmentation fault (core dumped) When I run steps 1, 5 and 8 I get the following error message: $ aria_pack /var/lib/mysql/mygo/term /var/lib/mysql/mygo/term gave error 132 on open Am I doing something wrong? Any pointers what I can check? Thanks

1 0

[Maria-discuss] Aria_pack error
by Kenneth Penza 27 Oct '17

27 Oct '17

Good afternoon, I am currently working on MariaDB version 10.1.26-MariaDB-1~yakkety running on Ubuntu 16.10 and have encountered an error whilst using aria_pack. The process used to generate the tables is as follows: 1) create table SQL script 2) shutdown MariaDB (systemctl shutdown mariadb.service) 3 )Disable indexes to speedup loading $ aria_chk --keys-used=0 -rq /var/lib/mysql/mygo/term - recovering (with keycache) Aria-table '/var/lib/mysql/mygo/term' Data records: 0 Table: /var/lib/mysql/mygo/term doesn't have an auto increment key State updated 4) startup MariaDB (systemctl start mariadb.service) 5) load data $ mysqlimport -u penzk001 --password=penzk100 -L mygo term.txt mygo.term: Records: 46032 Deleted: 0 Skipped: 0 Warnings: 0 6) shutdown mariadb (systemctl shutdown mariadb.service) 7) Check table $ aria_chk /var/lib/mysql/mygo/term Checking Aria file: /var/lib/mysql/mygo/term Data records: 46032 Deleted blocks: 0 - check file-size - check key delete-chain - check index reference - check record links State update 8) Compress table $ aria_pack /var/lib/mysql/mygo/term Compressing /var/lib/mysql/mygo/term.MAD: (46032 records) - Calculating statistics - Compressing file Segmentation fault (core dumped) When I run steps 1, 5 and 8 I get the following error message: $ aria_pack /var/lib/mysql/mygo/term /var/lib/mysql/mygo/term gave error 132 on open Am I doing something wrong? Any pointers what I can check? Thanks Kenneth

1 0

[Maria-discuss] maria won't start after giving up on mysql 5.7
by Richard Whitney 24 Oct '17

24 Oct '17

Hello, I have been trying for a week to get mysql 5.7 setup on raspbian and have thrown in the towel. I have now installed (tried to install) mariadb 10.1 and it seems to hang on install and then won't start Let me try one more time ....... sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: default-mysql-server 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 9,216 B disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 126235 files and directories currently installed.) Removing default-mysql-server (1.0.2) ... Setting up mariadb-server-10.1 (10.1.23-9+deb9u1) ... Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. invoke-rc.d: initscript mysql, action "start" failed. ● mariadb.service - MariaDB database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2017-10-24 13:25:21 MST; 60ms ago Process: 5576 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 5487 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) Process: 5482 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 5479 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 5576 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" Oct 24 13:25:16 qa.com systemd[1]: Starting MariaDB database server... Oct 24 13:25:18 qa.com mysqld[5576]: 2017-10-24 13:25:18 1996230656 [Note] /usr/sbin/mysqld (mysqld 10.1.…576 ... Oct 24 13:25:21 qa.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Oct 24 13:25:21 qa.com systemd[1]: Failed to start MariaDB database server. Oct 24 13:25:21 qa.com systemd[1]: mariadb.service: Unit entered failed state. Oct 24 13:25:21 qa.com systemd[1]: mariadb.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package mariadb-server-10.1 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mariadb-server: mariadb-server depends on mariadb-server-10.1 (>= 10.1.23-9+deb9u1); however: Package mariadb-server-10.1 is not configured yet. dpkg: error processing package mariadb-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mariadb-server-10.1 mariadb-server E: Sub-process /usr/bin/dpkg returned an error code (1) any ideas? Thank you! -- Richard Whitney phpMyDEV, LLC phpmydev.com 602-334-7771 May there always be tread and air in your tires and oatmeal and butter in your bowl - Author Unknown

1 0

[Maria-discuss] MaxScale behaviour differs for TLs and non-TLS clients
by Pak Chan 16 Oct '17

16 Oct '17

Hi, I'm (still) testing MaxScale, set up to connect only to the master node, on Ubuntu 16.04 fronting a Galera cluster. The cluster comprises of 2 MariaDB 10.1 instances on different servers, with a Galera Arbitrator instance running on the MaxScale server. I'm testing this using the MariaDB client (mysql) from a fourth machine. My test scenario is to see what the client experiences if I stop and restart a MariaDB node part-way through a transaction. I start with the "slave" node, to give me a baseline for comparison, before doing it with the master node. However, the baseline case gives me different results, depending on whether the MySQL client is connecting via TLS or not. If I connect to MaxScale via TLS, the connection disappears when the "slave" node comes back (but not when it goes down). Watching it via a network packet trace, I can see that, just after the slave comes back up, MaxScale sends the client an encrypted packet to the mysql client, then sends a MySQL Quit command to the master node before disconnecting. The syslog contains the line "[galeramon] There are no cluster members". If I connect to MaxScale without TLS, the connection remains stable regardless of the number of times the slave node goes down and up, and the "galeramon" line doesn't appear in the syslog. (I discovered this when I disabled the TLS in order to see what the encrypted packet being sent to the client was...I still don't know what it is!) Has anyone else come across this behaviour? MaxScale is configured as follows (the commented-out configuration is uncommented when connecting via TLS): [dbnode1] type=server address=172.16.1.22 port=3306 protocol=MySQLBackend priority=1 [dbnode2] type=server address=172.16.1.23 port=3306 protocol=MySQLBackend priority=2 [Galera Monitor] type=monitor module=galeramon servers=dbnode1,dbnode2 user=galeramon passwd=galeramon monitor_interval=1000 available_when_donor=true use_priority=true [Galera Service] type=service router=readrouteconn router_options=master servers=dbnode1,dbnode2 user=galeramon passwd=galeramon [MaxAdmin Service] type=service router=cli [Galera Listener] type=listener service=Galera Service protocol=MySQLClient port=3306 #ssl=required #ssl_version=TLSv12 #ssl_cert=/etc/mysql/ssl/server-cert.pem #ssl_key=/etc/mysql/ssl/server-key.pem #ssl_ca_cert=/etc/mysql/ssl/ca-cert.pem #ssl_cert_verify_depth=1 [MaxAdmin Listener] type=listener service=MaxAdmin Service protocol=maxscaled socket=default PC

2 3

[Maria-discuss] GitHub morgo/mysql-compatibility-config - add MariaDB
by Lukas Lehner 15 Oct '17

15 Oct '17

Hey I really like https://github.com/morgo/mysql-compatibility-config is there something similar for MariaDB? Since the repo is owned by some Oracle guy, I guess he won't add MariaDB. Lukas

1 0

[Maria-discuss] MaxScale (lack of) resilience to Galera cluster changes
by Pak Chan 06 Oct '17

06 Oct '17

Hi, Following on from my other thread, I'm testing MaxScale fronting a 2-node Galera cluster (with a Galera Arbitrator acting as the third node). My current test outline is as follows: 1. Identify the Write Master server in MaxScale 2. Connect two mysql clients to MaxScale, and put them both into "READ COMMITTED" isolation level ("set global transaction isolation level read committed") 3. Begin a transaction in each client session 4. Take down the non-Write master node in the Galera cluster ("systemctl stop mysql" on that server) 5. Commit the transaction in client 1 6. Confirm that the clients can see the committed change 7. Start up the stopped node in the Galera cluster ("systemctl start mysql" on that server) 8. Commit the transaction in client 2 9. Confirm that the clients can see the committed change 10. ... What happens is that everything appear to work up until step 8, when client 2 loses its connection to the database when trying to commit, reconnects and loses its uncommitted transaction as a result. At step 9, client 1 announces that it has lost the connection and reconnects. Is this meant to happen? If I run the same test, bypassing MaxScale and connecting both clients directly to the same Galera node, I don't get the connection loss. I understand that MaxScale will route writes to one node and reads to another, but surely the loss of connection to a read node should not result in the loss of connection to the write node? Am I doing something wrong? Yours very puzzled. PC

1 1

[Maria-discuss] MaxScale Server SSL version
by Pak Chan 05 Oct '17

05 Oct '17

Hi, I'm in the process of setting up MaxScale on Ubuntu 16.04 fronting a Galera cluster where the MariaDB database nodes (also on Ubuntu 16.04) are set to use TLSv1.2. There is a "test" user and a "galeramon" user on the database, both requiring SSL. According to the documentation, I can configure this in MaxScale as follows: [dbnode1] type=server address=172.16.1.22 port=3306 protocol=MySQLBackend ssl=required ssl_version=TLSv12 ssl_cert=/etc/mysql/ssl/db-client-cert.pem ssl_key=/etc/mysql/ssl/db-client-key.pem ssl_ca_cert=/etc/mysql/ssl/ca-cert.pem [dbnode2] type=server address=172.16.1.23 port=3306 protocol=MySQLBackend ssl=required ssl_version=TLSv12 ssl_cert=/etc/mysql/ssl/db-client-cert.pem ssl_key=/etc/mysql/ssl/db-client-key.pem ssl_ca_cert=/etc/mysql/ssl/ca-cert.pem [Galera Monitor] type=monitor module=galeramon servers=dbnode1,dbnode2 user=galeramon passwd=galeramon monitor_interval=1000 [Galera Service] type=service router=readwritesplit servers=dbnode1,dbnode2 user=galeramon passwd=galeramon [MaxAdmin Service] type=service router=cli [Galera Listener] type=listener service=Galera Service protocol=MySQLClient port=3306 authenticator=MySQL ssl=required ssl_version=TLSv12 ssl_cert=/etc/mysql/ssl/server-cert.pem ssl_key=/etc/mysql/ssl/server-key.pem ssl_ca_cert=/etc/mysql/ssl/ca-cert.pem ssl_cert_verify_depth=9 [MaxAdmin Listener] type=listener service=MaxAdmin Service protocol=maxscaled socket=default However, this never successfully connects. I ran a packet capture on the connection, and found that the reason it was failing was that MaxScale was trying to connect using TLSv1.0 despite the specification. Changing the "ssl_version" setting to "MAX" had no effect. The version of openssl and libssl1.0.0 on the server are both 1.0.2g-1ubuntu4.8, so it should support TLSv1.2. I installed MaxScale with: curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=mariadb-10.1 sudo apt install maxscale I can disable the TLS requirement for the "galeramon" user, which allows MaxScale to start up, but the moment I log into the database via MaxScale as the "test" user, the connection fails, as the following transcript (from a different server) shows: test@dbclient01:~$ mysql -h 172.16.2.1 -u test -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 31200 Server version: 10.0.0 2.1.9-maxscale Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MySQL [(none)]> show databases; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id: 31200 Current database: *** NONE *** ERROR 2003 (HY000): Authentication with backend failed. Session will be closed. MySQL [(none)]> Is this a known issue, or is there something wrong with the configuration? For the record, I can connect to a database instance over TLSv1.2 from the MaxScale server using the mysql client with the same ("db-client-*") certificate as specified above. PC

2 2

[Maria-discuss] 10.2: Aborted connection 1880 to db.....
by Reindl Harald 30 Sep '17

30 Sep '17

what are these messages which appear in 10.2 regulary - the single enry below is nothing else than stop a slave service and the other flood which is really annoying is libnss-mysql (system users and groups wihtin a mysql database) 2017-09-30 22:28:02 140709059794688 [Warning] Aborted connection 1880 to db: 'unconnected' user: 'replication' host: 'x.x.x.x' (Got an error writing communication packets) at least name it 'Notice' instead of 'Warning' so that it don't trigger alert mails seeking for 'error', 'failed' and 'warning' over severeal hosts and service logs _____________________________________ 2017-09-30 11:06:27 140340005750528 [Warning] Aborted connection 5 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:27 140340005144320 [Warning] Aborted connection 6 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:27 140340004538112 [Warning] Aborted connection 7 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:34 140340005750528 [Warning] Aborted connection 13 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:34 140340005144320 [Warning] Aborted connection 14 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:35 140340004538112 [Warning] Aborted connection 15 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:35 140340003325696 [Warning] Aborted connection 17 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:06:35 140340003628800 [Warning] Aborted connection 16 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:07:30 140340005144320 [Warning] Aborted connection 22 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:07:30 140340005750528 [Warning] Aborted connection 21 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:10:01 140340006356736 [Warning] Aborted connection 28 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:10:01 140340006962944 [Warning] Aborted connection 27 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:10:01 140339927049984 [Warning] Aborted connection 26 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:15:01 140340005144320 [Warning] Aborted connection 38 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:15:01 140340003628800 [Warning] Aborted connection 40 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:15:01 140340004538112 [Warning] Aborted connection 39 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:15:01 140340003325696 [Warning] Aborted connection 41 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:15:02 140340005750528 [Warning] Aborted connection 37 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:17:15 140340005144320 [Warning] Aborted connection 46 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:19:08 140339927049984 [Warning] Aborted connection 34 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:19:08 140340003325696 [Warning] Aborted connection 33 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:20:01 140340006962944 [Warning] Aborted connection 59 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:20:01 140340003628800 [Warning] Aborted connection 56 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:20:01 140340006356736 [Warning] Aborted connection 60 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:20:01 140340005750528 [Warning] Aborted connection 61 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:20:01 140339927049984 [Warning] Aborted connection 58 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:20:02 140340003325696 [Warning] Aborted connection 57 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:25:01 140340003628800 [Warning] Aborted connection 72 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:25:01 140340004538112 [Warning] Aborted connection 71 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140340003628800 [Warning] Aborted connection 80 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140340004538112 [Warning] Aborted connection 79 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140340006962944 [Warning] Aborted connection 83 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140340005750528 [Warning] Aborted connection 85 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140339927049984 [Warning] Aborted connection 82 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140340006356736 [Warning] Aborted connection 84 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:30:01 140340003325696 [Warning] Aborted connection 81 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:35:01 140340005144320 [Warning] Aborted connection 94 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:35:01 140340005750528 [Warning] Aborted connection 93 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:40:01 140340004538112 [Warning] Aborted connection 103 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:40:01 140340003628800 [Warning] Aborted connection 104 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:40:01 140340003325696 [Warning] Aborted connection 105 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:40:01 140339927049984 [Warning] Aborted connection 106 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:40:01 140340005144320 [Warning] Aborted connection 102 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:40:01 140340005750528 [Warning] Aborted connection 101 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:45:01 140340006356736 [Warning] Aborted connection 116 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:45:01 140340005750528 [Warning] Aborted connection 117 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:45:01 140340004538112 [Warning] Aborted connection 119 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:45:02 140340003628800 [Warning] Aborted connection 120 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:45:02 140340005144320 [Warning] Aborted connection 118 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:50:01 140340003628800 [Warning] Aborted connection 128 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:50:01 140340003325696 [Warning] Aborted connection 129 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:55:01 140340003628800 [Warning] Aborted connection 136 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 11:55:01 140340003325696 [Warning] Aborted connection 137 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340003325696 [Warning] Aborted connection 145 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140339927049984 [Warning] Aborted connection 146 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340006962944 [Warning] Aborted connection 147 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340005750528 [Warning] Aborted connection 149 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340006962944 [Warning] Aborted connection 155 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340006356736 [Warning] Aborted connection 148 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140339927049984 [Warning] Aborted connection 154 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340003325696 [Warning] Aborted connection 153 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340003628800 [Warning] Aborted connection 152 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340003628800 [Warning] Aborted connection 144 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340005144320 [Warning] Aborted connection 150 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:00:01 140340004538112 [Warning] Aborted connection 151 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:01:01 140339927049984 [Warning] Aborted connection 162 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:01:01 140340006356736 [Warning] Aborted connection 164 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:01:02 140340006962944 [Warning] Aborted connection 163 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:02:01 140340003325696 [Warning] Aborted connection 169 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:02:01 140340003628800 [Warning] Aborted connection 168 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:03:01 140340006356736 [Warning] Aborted connection 172 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:05:01 140340004538112 [Warning] Aborted connection 175 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:05:01 140340003628800 [Warning] Aborted connection 176 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:10:01 140340003628800 [Warning] Aborted connection 184 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:10:01 140340003325696 [Warning] Aborted connection 185 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:10:01 140340004538112 [Warning] Aborted connection 183 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:15:01 140340003628800 [Warning] Aborted connection 192 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:15:01 140340003325696 [Warning] Aborted connection 193 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:15:01 140340006962944 [Warning] Aborted connection 195 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:15:01 140340006356736 [Warning] Aborted connection 196 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:15:01 140339927049984 [Warning] Aborted connection 194 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:20:01 140340006356736 [Warning] Aborted connection 204 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:20:01 140340004538112 [Warning] Aborted connection 207 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:20:01 140340003628800 [Warning] Aborted connection 208 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:20:01 140340003325696 [Warning] Aborted connection 209 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:20:02 140340005750528 [Warning] Aborted connection 205 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:20:02 140340005144320 [Warning] Aborted connection 206 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:25:01 140340006962944 [Warning] Aborted connection 219 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:25:01 140340006356736 [Warning] Aborted connection 220 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:26:53 140340003628800 [Warning] Aborted connection 224 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:30:01 140340005750528 [Warning] Aborted connection 229 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:30:01 140339927049984 [Warning] Aborted connection 234 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:30:01 140340003628800 [Warning] Aborted connection 232 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:30:01 140340004538112 [Warning] Aborted connection 231 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets) 2017-09-30 12:30:01 140340006356736 [Warning] Aborted connection 228 to db: 'pam_mysql' user: 'pam_mysql' host: 'localhost' (Got an error reading communication packets)

1 0

[Maria-discuss] 10.2: https://mariadb.com/kb/en/library/defragmenting-innodb-tablespaces/
by Reindl Harald 30 Sep '17

30 Sep '17

https://mariadb.com/kb/en/library/defragmenting-innodb-tablespaces/ seems to be silently broken in 10.2 or why is there a fat temp-file as well as the progress display from previous versions don't work in 10.1/10.2 in a useable way (a pseudo progress for small tables is nice but when you see no output at all when 'optimize table' is running on a table with 10 GB it's broken) "innodb-defragment = 1" is set -rw-rw---- 1 mysql mysql 2,6G 2017-09-30 21:39 '#sql-ib3030-2883732087.ibd' MariaDB [dbmail]> OPTIMIZE TABLE `dbmail_users`; +---------------------+----------+----------+-------------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +---------------------+----------+----------+-------------------------------------------------------------------+ | dbmail.dbmail_users | optimize | note | Table does not support optimize, doing recreate + analyze instead | | dbmail.dbmail_users | optimize | status | OK | +---------------------+----------+----------+-------------------------------------------------------------------+

1 1

[Maria-discuss] Fwd: [MariaDB Announce] MariaDB 10.2.9, MariaDB 10.1.28 and MariaDB Connector/J releases
by Reindl Harald 29 Sep '17

29 Sep '17

it would be really cool if MariaDB minor updates (10.2.8 to 10.2.9 in that case) would work like for any other software - just replace the tarball, raise the version in the spec-file and hit "rpmbuild -bb mariadb.spec" CMakeError.log as tar.bz2 attached.... ________________________________________________________________________________________ CMake Error at sql/CMakeLists.txt:387 (TARGET_LINK_LIBRARIES): Target "mysqld" of type EXECUTABLE may not be linked into another target. One may link only to STATIC or SHARED libraries, or to executables with the ENABLE_EXPORTS property set. CMake Deprecation Warning at cmake/for_clients.cmake:15 (CMAKE_POLICY): The OLD behavior for policy CMP0007 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. Call Stack (most recent call first): CMakeLists.txt:415 (INCLUDE) ________________________________________________________________________________________ cmake . \ -DFEATURE_SET="large" \ -DCMAKE_INSTALL_PREFIX="%{_prefix}" \ -DINSTALL_INCLUDEDIR=include/mysql \ -DINSTALL_LAYOUT=RPM \ -DDAEMON_NAME="mysqld" \ -DDAEMON_NO_PREFIX="mysqld" \ -DNICE_PROJECT_NAME="MariaDB" \ -DINSTALL_LIBDIR="%{_lib}/mysql" \ -DINSTALL_MANDIR=share/man \ -DINSTALL_MYSQLSHAREDIR=share/mysql \ -DINSTALL_MYSQLTESTDIR=share/mysql-test \ -DINSTALL_PLUGINDIR="%{_lib}/mysql/plugin" \ -DINSTALL_SBINDIR=libexec \ -DINSTALL_SCRIPTDIR=bin \ -DINSTALL_SQLBENCHDIR= \ -DINSTALL_SUPPORTFILESDIR=share/mysql \ -DMYSQL_DATADIR="%{_sharedstatedir}/mysql" \ -DMYSQL_UNIX_ADDR="%{_sharedstatedir}/mysql/mysql.sock" \ -DENABLED_PROFILING=OFF \ -DENABLE_DEBUG_SYNC=OFF \ -DENABLE_DTRACE=OFF \ -DPLUGIN_ARIA=YES \ -DPLUGIN_CSV=YES \ -DPLUGIN_MYISAM=YES \ -DPLUGIN_ARCHIVE=NO \ -DPLUGIN_BLACKHOLE=NO \ -DPLUGIN_CASSANDRA=NO \ -DPLUGIN_CONNECT=NO \ -DPLUGIN_EXAMPLE=NO \ -DPLUGIN_FEDERATED=NO \ -DPLUGIN_FEDERATEDX=NO \ -DPLUGIN_FEEDBACK=NO \ -DPLUGIN_MROONGA=NO \ -DPLUGIN_MYISAMMRG=NO \ -DPLUGIN_OQGRAPH=NO \ -DPLUGIN_PARTITION=NO \ -DPLUGIN_PERFSCHEMA=NO \ -DPLUGIN_ROCKSDB=NO \ -DPLUGIN_SEMISYNC=NO \ -DPLUGIN_SEQUENCE=NO \ -DPLUGIN_SPHINX=NO \ -DPLUGIN_SPIDER=NO \ -DPLUGIN_TOKUDB=NO \ -DPLUGIN_XTRADB=NO \ -DWITHOUT_DYNAMIC_PLUGINS=ON \ -DWITH_ATOMIC_OPS=smp \ -DWITH_EMBEDDED_SERVER=OFF \ -DWITH_INNODB_DISALLOW_WRITES=OFF \ -DWITH_INNODB_BZIP2=OFF \ -DWITH_INNODB_LZ4=OFF \ -DWITH_INNODB_LZMA=OFF \ -DWITH_INNODB_LZO=OFF \ -DWITH_INNODB_SNAPPY=OFF \ -DWITH_MYSQLCOMPAT=ON \ -DSECURITY_HARDENED=OFF \ -DWITH_LIBARCHIVE=OFF \ -DWITH_LIBWRAP=OFF \ -DWITH_MARIABACKUP=OFF \ -DWITH_PIC=NO \ -DWITH_READLINE=OFF \ -DWITH_SAFEMALLOC=OFF \ -DWITH_VALGRIND=OFF \ -DWITH_WSREP=OFF \ -DWITH_JEMALLOC=OFF \ -DWITH_SSL=system \ -DWITH_ZLIB=system \ -DCOMPILATION_COMMENT="thelounge" %{__make} %{?_smp_mflags} ________________________________________________________________________________________ -------- Weitergeleitete Nachricht -------- Betreff: [MariaDB Announce] MariaDB 10.2.9, MariaDB 10.1.28 and MariaDB Connector/J releases Datum: Thu, 28 Sep 2017 11:57:47 +0200 Von: MariaDB Announce List <announce(a)mariadb.org> An: announce(a)mariadb.org The MariaDB project is pleased to announce the availability of MariaDB 10.2.9, MariaDB 10.1.28, MariaDB Connector/J 2.1.2 and MariaDB Connector/J 1.6.5. These are all stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.9 - Release Notes: https://mariadb.com/kb/en/mdb-1029-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1029-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.9 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ MariaDB 10.1.28 - Release Notes: https://mariadb.com/kb/en/mdb-10128-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10128-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.28 About MariaDB 10.1: - https://mariadb.com/kb/en/what-is-mariadb-101/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 2.1.2 - Release Notes: https://mariadb.com/kb/en/mcj-212-rn/ - Changelog: https://mariadb.com/kb/en/mcj-212-cl/ - Downloads: https://downloads.mariadb.org/connector-java/2.1.2/ MariaDB Connector/J 1.6.5 - Release Notes: https://mariadb.com/kb/en/mcj-165-rn/ - Changelog: https://mariadb.com/kb/en/mcj-165-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.6.5/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://jira.mariadb.org - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadbfdn Knowledge Base - http://mariadb.com/kb _______________________________________________ announce mailing list announce(a)mariadb.org https://lists.askmonty.org/cgi-bin/mailman/listinfo/announce To unsubscribe, send an email with "unsubscribe" as the Subject: to announce-request(a)mariadb.org

2 9

[Maria-discuss] 10.2.9: failing innodb tests
by Reindl Harald 29 Sep '17

29 Sep '17

that looks not good innodb.table_flags '32k,innodb' w1 [ fail ] Test ended at 2017-09-29 14:17:44 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/1/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,32k.result~ 2017-09-26 17:07:32.071814438 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,32k.reject 2017-09-29 14:17:44.692570878 +0200 @@ -176,7 +176,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/1/log/innodb.table_flags-32k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-32k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1a1); dictionary contains id=3, flags=0x101a1 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:17:39 139655137466688 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:39 139655137466688 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1a1); dictionary contains id=3, flags=0x101a1 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:39 139654955267840 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 innodb.table_flags '64k,innodb' w4 [ fail ] Test ended at 2017-09-29 14:17:46 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/4/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,64k.result~ 2017-09-26 17:07:29.435940019 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,64k.reject 2017-09-29 14:17:46.209498842 +0200 @@ -176,7 +176,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/4/log/innodb.table_flags-64k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-64k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1e1); dictionary contains id=3, flags=0x101e1 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:17:40 139995643373888 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:40 139995643373888 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x1e1); dictionary contains id=3, flags=0x101e1 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12321 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:17:41 139995554035456 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 innodb.table_flags '4k,innodb' w2 [ fail ] Test ended at 2017-09-29 14:18:19 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/2/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,4k.result~ 2017-09-26 17:08:10.304992901 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,4k.reject 2017-09-29 14:18:18.954943828 +0200 @@ -174,7 +174,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/2/log/innodb.table_flags-4k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-4k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0xe1); dictionary contains id=3, flags=0x100e1 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:18:13 140291687692608 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:13 140291687692608 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0xe1); dictionary contains id=3, flags=0x100e1 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:13 140291589162752 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 sys_vars.innodb_file_per_table_basic 'innodb' w2 [ pass ] 4 innodb.index_tree_operation 'innodb' w1 [ pass ] 19 innodb.innodb_bug60049 'innodb' w3 [ pass ] 2522 innodb.create_isl_with_direct 'innodb' w2 [ pass ] 8 innodb.innodb_force_pk 'innodb' w2 [ pass ] 13 innodb.101_compatibility '8k,innodb' w4 [ pass ] 4519 main.flush_block_commit_notembedded 'innodb' w3 [ pass ] 2061 binlog.binlog_checksum 'innodb,row' w2 [ pass ] 834 main.mysql_upgrade 'innodb' w3 [ skipped ] Test requires partitioning innodb.alter_missing_tablespace '8k,innodb' w4 [ pass ] 2518 innodb.innodb_bug14147491 'innodb' w1 [ pass ] 4107 innodb.innodb_autoinc_lock_mode_zero 'innodb' w3 [ pass ] 12 innodb.innodb-mdev-7408 'innodb' w1 [ pass ] 6 innodb.innodb_bug42101-nonzero 'innodb' w3 [ pass ] 5 innodb.innodb-alter-nullable '8k,innodb' w4 [ pass ] 52 innodb.innodb_information_schema_buffer 'innodb' w1 [ pass ] 25 innodb.innodb-alter-table '8k,innodb' w4 [ pass ] 523 binlog.binlog_commit_wait 'innodb,row' w2 [ pass ] 5275 binlog.binlog_dmls_on_tmp_tables_readonly 'innodb,row' w2 [ pass ] 11 innodb.innodb_bug39438 'innodb' w3 [ pass ] 8 main.bug46760 'innodb' w1 [ pass ] 12 main.row-checksum-old 'innodb' w3 [ pass ] 16 innodb.innodb_trx_weight 'innodb' w1 [ pass ] 40 innodb.innodb-alter 'innodb' w3 [ pass ] 245 main.row-checksum 'innodb' w1 [ pass ] 10 innodb.temporary_table_optimization 'innodb' w3 [ pass ] 47 innodb.data_types 'innodb' w1 [ pass ] 5 innodb.innodb-index-online-norebuild 'innodb' w3 [ pass ] 8 innodb.innodb-stats-modified-counter 'innodb' w1 [ pass ] 8 innodb.table_flags '8k,innodb' w4 [ fail ] Test ended at 2017-09-29 14:18:40 CURRENT_TEST: innodb.table_flags /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/4/tmp/table_flags/ibtmp1' (Errcode: 2 "No such file or directory") --- /usr/share/mysql-test/suite/innodb/r/table_flags,8k.result~ 2017-09-26 17:08:28.249137992 +0200 +++ /usr/share/mysql-test/suite/innodb/r/table_flags,8k.reject 2017-09-29 14:18:40.460922576 +0200 @@ -174,7 +174,6 @@ SELECT * FROM tp; a DROP TABLE tr,tc,td,tz,tp; -ib_buffer_pool ib_logfile0 ib_logfile1 ibdata1 mysqltest: Result length mismatch - saving '/usr/share/mysql-test/var/4/log/innodb.table_flags-8k,innodb/' to '/usr/share/mysql-test/var/log/innodb.table_flags-8k,innodb/' ***Warnings generated in error logs during shutdown after running tests: innodb.table_flags 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x121); dictionary contains id=3, flags=0x10121 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2017-09-29 14:18:35 139736414353728 [Warning] InnoDB: Ignoring tablespace for `test`.`td` because it could not be opened. 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:35 139736414353728 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tr` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=65 SYS_TABLES.MIX_LEN=4294967295 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tc` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=129 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Refusing to load './test/td.ibd' (id=3, flags=0x121); dictionary contains id=3, flags=0x10121 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: The error means the system cannot find the path specified. 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tz` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=12323 SYS_TABLES.N_COLS=2147483649 2017-09-29 14:18:35 139736317077248 [ERROR] InnoDB: Table `test`.`tp` in InnoDB data dictionary contains invalid flags. SYS_TABLES.TYPE=289 SYS_TABLES.N_COLS=2147483649 innodb.innodb_information_schema_tables 'innodb' w3 [ pass ] 17 innodb.innodb-trim 'innodb' w1 [ pass ] 1101 innodb.innodb-autoinc-56228 'innodb' w1 [ pass ] 4 innodb.innodb_mysql_rbk 'innodb' w3 [ pass ] 3885 binlog.binlog_implicit_commit 'innodb,row' w2 [ pass ] 16518 binlog.binlog_innodb 'innodb,row' w2 [ pass ] 2708 innodb.innodb-lock-schedule-algorithm 'innodb' w4 [ pass ] 10193 main.commit_1innodb 'innodb' w2 [ fail ] Test ended at 2017-09-29 14:18:51 CURRENT_TEST: main.commit_1innodb --- /usr/share/mysql-test/r/commit_1innodb.result 2017-09-25 08:33:24.000000000 +0200 +++ /usr/share/mysql-test/r/commit_1innodb.reject 2017-09-29 14:18:51.351405429 +0200 @@ -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 - saving '/usr/share/mysql-test/var/2/log/main.commit_1innodb-innodb/' to '/usr/share/mysql-test/var/log/main.commit_1innodb-innodb/'

1 0

[Maria-discuss] perl-dbi
by Ruben Safir 26 Sep '17

26 Sep '17

Does anything need to be ported to mariabd if we are using perl::DBI or can I just pull the files from cpan. I have a large number of legacy applications I need to adapt based on MYSQL::DBI modules. Ruben -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

1 0

[Maria-discuss] mysqld_safe and pid files
by Ruben Safir 26 Sep '17

26 Sep '17

hello monty et al i'm trying to write an init script for maria and artix, which is using openrc I got it to start up but the pid-file is a problem and I think that the command line options for mysqld_safe is not working. it doesnt create the specified pid file [www3 ~]# /usr/bin/mysqld_safe --pid-file=/run/mariadb.pid 170926 10:41:52 mysqld_safe Logging to '/usr/local/var/www3.err'. 170926 10:41:52 mysqld_safe Starting mysqld daemon with databases from /usr/local/var [www3 ~]# cat /run/mariadb.pid cat: /run/mariadb.pid: No such file or directory [www3 ~]# tail -f /usr/local/var/www3.err 2017-09-26 10:41:53 139828287336192 [Note] InnoDB: 128 rollback segment(s) are active. 2017-09-26 10:41:53 139828287336192 [Note] InnoDB: Waiting for purge to start 2017-09-26 10:41:53 139828287336192 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.0 started; log sequence number 1601111 2017-09-26 10:41:53 139828287336192 [Note] Plugin 'FEEDBACK' is disabled. 2017-09-26 10:41:53 139827658368768 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-09-26 10:41:53 139828287171328 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist 2017-09-26 10:41:53 139828287336192 [Note] Server socket created on IP: '::'. 2017-09-26 10:41:53 139828286868224 [ERROR] mysqld: Can't create/write to file '/run/mariadb.pid' (Errcode: 13 "Permission denied") 2017-09-26 10:41:53 139828286868224 [ERROR] Can't start server: can't create PID file: Permission denied 170926 10:41:53 mysqld_safe mysqld from pid file /run/mariadb.pid ended drwxr-xr-x 16 root root 620 Sep 25 21:45 run what do you recommend to do? The system is uniform -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

3 6

Re: [Maria-discuss] URI data source for XML/JSON CONNECT tables?
by Olivier Bertrand 14 Sep '17

14 Sep '17

Hi! Le 18/02/2015 à 08:05, Kolbe Kegel a écrit : > Hi! > > I had some fun using the JSON table type recently. But what fun is it to read JSON from a file. FYI, CONNECT new versions (already distributed in 10.2) include getting Json info directly from MongoDB collections. > JSON comes from RESTful APIs :) > > Has there been any thought about functionality to read JSON from a URI? See above and the attached doc. > This introduces loads of complications and dependencies, but maybe it'd be worth looking into. Or maybe that's something that could be provided by some other plugin that'd handle the HTTP heavy lifting? > > We'd want to take into account that most RESTful APIs worth pulling JSON from would require some form of authentication that we probably would not want to force users to store in their table definition. > > Kolbe > Olivier

1 0

[Maria-discuss] Mariadb cluster on windows
by vv2599 06 Sep '17

06 Sep '17

Hello Guys, I would like to know if there is a way to setup mariadb cluster on windows or is there any way that a high availability system can be setup on windows server 2008. Appreciate any response. Regards, Vino

4 7

[Maria-discuss] Issues with get SSL replication going (I.e. Encrypting Replication Traffic as well as Encrypting SST Traffic)
by Brent Clark 30 Aug '17

30 Aug '17

Good day Guys Im trying to get SSL replication going (I.e. Encrypting Replication Traffic as well as Encrypting SST Traffic). For the likes of me I just cant get it working. If I set the variable, encrypt = 0 (i.e. encryption off) replication works. Please can I ask if someone could please review my logs / setup are see where my issue lays. Here is my configuration setup https://pastebin.com/9JDP4LCr This is the /var/log/mysql/error.log of First node (i.e. Donor) https://pastebin.com/MrWDcECA This is the /var/log/mysql/error.log of 2nd node (i.e. joiner) https://pastebin.com/wZiNDP4P If anyone can assist, it would most appreciated. Kind Regards Brent Clark

1 0

Re: [Maria-discuss] Pacemaker and mariadb semi-sync
by Pavel Ivanov 22 Aug '17

22 Aug '17

Yes, having processlist while it's hung might be handy. On Tue, Aug 22, 2017 at 3:45 PM, Nils Carlson <nils.carlson(a)ludd.ltu.se> wrote: > On 08/22/2017 10:42 PM, Pavel Ivanov wrote: > >> Can you clarify what SHOW SLAVE STATUS blocks on for you? > > Not really. Basically, just after performing a failover, I run SHOW SLAVE > STATUS on the slave and that can take up to 30 seconds sometimes before the > query returns. Once it does return everything looks like normal. I can try > to dump the thread status maybe. > > /Nils > > > >> On Sun, Aug 20, 2017 at 9:47 AM, Nils Carlson <nils.carlson(a)ludd.ltu.se> >> wrote: >>> >>> Hi Pavel and Kristian, >>> >>> On 08/10/2017 10:58 PM, Pavel Ivanov wrote: >>>> >>>> Note also that you don't want to set rpl_semi_sync_master_enabled='ON' >>>> on all your slaves, it should be set only on the master. With the >>>> setting your slaves' SQL threads will hang waiting for semi-sync ack >>>> as well, and they will hang forever if >>>> rpl_semi_sync_master_wait_no_slave is set to ON too. >>>> >>> Thank you. >>> >>>> On Wed, Aug 9, 2017 at 2:30 AM, Kristian Nielsen >>>> <knielsen(a)knielsen-hq.org> wrote: >>>>> >>>>> Hope this helps, >>> >>> >>> And thank you for all this! >>> >>> I have updated the resource-agent based on this and run some light >>> testing. >>> I will try to write automated tests soon. >>> >>> I was also wondering about one thing, the block SHOW SLAVE STATUS >>> command. >>> Is there any way to ensure this doesn't block? Maybe this is something to >>> suggest to the development mailing list? >>> >>> Thanks again. >>> >>> Cheers, >>> Nils >>> >>> >>>>> - Kristian. >>>>> >>>>> _______________________________________________ >>>>> Mailing list: https://launchpad.net/~maria-discuss >>>>> Post to : maria-discuss(a)lists.launchpad.net >>>>> Unsubscribe : https://launchpad.net/~maria-discuss >>>>> More help : https://help.launchpad.net/ListHelp >>> >>> >

1 0

Re: [Maria-discuss] Pacemaker and mariadb semi-sync
by Pavel Ivanov 22 Aug '17

22 Aug '17

Can you clarify what SHOW SLAVE STATUS blocks on for you? On Sun, Aug 20, 2017 at 9:47 AM, Nils Carlson <nils.carlson(a)ludd.ltu.se> wrote: > Hi Pavel and Kristian, > > On 08/10/2017 10:58 PM, Pavel Ivanov wrote: >> >> Note also that you don't want to set rpl_semi_sync_master_enabled='ON' >> on all your slaves, it should be set only on the master. With the >> setting your slaves' SQL threads will hang waiting for semi-sync ack >> as well, and they will hang forever if >> rpl_semi_sync_master_wait_no_slave is set to ON too. >> > Thank you. > >> On Wed, Aug 9, 2017 at 2:30 AM, Kristian Nielsen >> <knielsen(a)knielsen-hq.org> wrote: >>> >>> Hope this helps, > > > And thank you for all this! > > I have updated the resource-agent based on this and run some light testing. > I will try to write automated tests soon. > > I was also wondering about one thing, the block SHOW SLAVE STATUS command. > Is there any way to ensure this doesn't block? Maybe this is something to > suggest to the development mailing list? > > Thanks again. > > Cheers, > Nils > > >>> >>> - Kristian. >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~maria-discuss >>> Post to : maria-discuss(a)lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~maria-discuss >>> More help : https://help.launchpad.net/ListHelp > >

1 0

[Maria-discuss] connection handling is buggy (HY000/2002): Resource temporarily unavailable)
by Reindl Harald 19 Aug '17

19 Aug '17

i started to play around with "thread_handling = pool-of-threads" with 10.2.7 and removed at that time the @mysqli_real_connect() error supression of my database-layer which also has a usleep() and retry-loop in case connection failed on so completly burried the issue PHP Warning: mysqli_real_connect() [<a href='http://at.php.net/manual/de/function.mysqli-real-connect.php'>function.mysqli-real-connect.php</a>]: (HY000/2002): Resource temporarily unavailable you should not see such messages when run a "ab -c 200 -n 500000 -k http://corecms/show_content.php?sid=2" with "max_connections = 300" _____________________________________ thread_handling = one-thread-per-connection [root@srv-rhsoft:~]$ cat php_error.log | wc -l 52596 thread_handling = pool-of-threads thread_pool_idle_timeout = 900 [root@srv-rhsoft:~]$ cat php_error.log | wc -l 39282 thread_handling = pool-of-threads thread_pool_oversubscribe = 10 thread_pool_idle_timeout = 900 thread_pool_priority = high [root@srv-rhsoft:~]$ cat php_error.log | wc -l 24849 since my database-layer makes a usleep(100000) before each retry and the retry-lop still has error-supression that means the cms waits 10% of all requests at least 0.1 seconds for the mariadb server which means the 4300 Requests/Second could be much higher if every connection suceeds at the first try (at least the thread pool seems to work slightly better then without) _____________________________________ what makes me really worry here is while the load is running (mysqld each time restartet before start apache-benchmark) +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Threadpool_idle_threads | 181 | | Threadpool_threads | 189 | +-------------------------+-------+ after the benchmark has finished and the machine is idle: +-------------------------+-------+ | Variable_name | Value | +-------------------------+-------+ | Threadpool_idle_threads | 207 | | Threadpool_threads | 208 | +-------------------------+-------+ frankly i would expect at least that this numbers are going up while the load is running to at least 200 or not going up that high at all but don't refuse conncetions which is IMHO the point of a pool _____________________________________ the core-cms itself makes exactly two queries per request over 3 MyISAM tables, one cache-table with a pirmary key and the second one is a simple join on two tables with only 2 records, so not really something one should call real load select SQL_NO_CACHE * from cms1_cache where `hash`='fullmenu_1_2_0de0_0' select SQL_NO_CACHE * from `cms1_sub` join `cms1_haupt` on sid=2 and hid=shid mysqld as well as httpd had "LimitNOFILE=infinity" in the systemd-unit, the connection type is unix socket, so that all should not be a problem on a i7-3770 CPU @ 3.40GHz with 32 GB RAM it takes some time until the errors start to appear in the log, likely after httpd (mod_prefork) had forked enough worker to introduce real concurrency to the database

3 15

[Maria-discuss] Pacemaker and mariadb semi-sync
by Nils Carlson 10 Aug '17

10 Aug '17

Hi, I've been working on developing a pacemaker resource-agent for mariadb semi-sync replication. There is a pull request here on github: https://github.com/ClusterLabs/resource-agents/pull/929 I would be very happy for some review (and even testing) of this resource-agent from somebody with expertise in mariadb replication. The general idea is to select the master at startup and failure as the node with the highest GTID. AFTER_SYNC is used to ensure at least one slave will have all the updates. mariadb is started with --log-slave-updates to ensure that slaves log all events, so the binary log on each node should always be complete. The parameter set on each node is as follows: SET GLOBAL rpl_semi_sync_slave_enabled='ON', \ rpl_semi_sync_master_enabled='ON', \ rpl_semi_sync_master_wait_point='AFTER_SYNC', \ gtid_strict_mode='ON', \ sync_binlog=1, \ sync_master_info=1, \ sync_relay_log=1, \ sync_relay_log_info=1; I suspect this may be overkill, but I don't have the competence to judge. I have also found that calling "SHOW SLAVE STATUS;" may take a long time to display data when the slave is very busy (typically replicating after a failure). Is there any way to make sure it doesn't block? All feedback very welcome. Best Regards, Nils Carlson

3 2

[Maria-discuss] question about fast path for TRUNCATE TABLE
by MARK CALLAGHAN 06 Aug '17

06 Aug '17

This started as a question on a MyRocks list. MyRocks comes from MariaDB in this case and the code that determines whether the truncate table fast path is used looks different in MariaDB than in FB MySQL. By "fast path" for truncate I mean the use of drop/recreate for truncate. The slow path is delete one row at a time. In this case, truncate is doing delete one row at a time for MyRocks in MariaDB but drop/recreate in FB MySQL. https://groups.google.com/forum/#!topic/myrocks-dev/dhweTwN-9xg -- Mark Callaghan mdcallag(a)gmail.com

3 6

[Maria-discuss] Debian 9 support for MaxScale
by Martin Toth 03 Aug '17

03 Aug '17

Hi all, I would like to ask if there is some release date for fixing https://jira.mariadb.org/browse/MXS-1292 . Debian 9 should be included as a build target ASAP. I am installing only D9 systems on new servers and I am unable to use builds for MaxScale, so its unusable in D9. Thanks. Martin

2 4

[Maria-discuss] MariaDb 10.2 in RHEL 5.3
by Karthick Subramanian 03 Aug '17

03 Aug '17

Did anyone install the Maria DB 10.2 in RHEL Red Hat Enterprise Linux Server release 5.3 (Tikanga). I am planning to install this in Dev env, its not prod, Shall I try this. Regards, Karthick

3 2

[Maria-discuss] 2nd 2017 Developers Unconference
by Ian Gilfillan 03 Aug '17

03 Aug '17

The 2017 MariaDB Developers Unconference will be our first in Asia, and will be held in Shenzhen, China from 13 November - 17 November. There are 3 related events: 13 November - new contributor day 14-15 November - traditional developers unconference 16-17 November - patch days As always it's free to attend, and open to anyone interested in MariaDB development. Details at https://mariadb.org/2017-2-developers-unconference-and-related-events-shenz…

1 0

[Maria-discuss] Tokudb 5.7.18-16 fixes in Mariadb 10.2.8
by Reinis Rozitis 02 Aug '17

02 Aug '17

Hello, is there any chance/possibility for these fixes from Percona Server 5.7.18-16 to land in 10.2.8 release? Row counts in TokuDB could be lost intermittently after restarts ( https://jira.percona.com/browse/TDB-2 ) In TokuDB, two races in the fractal tree lock manager .. ( https://jira.percona.com/browse/TDB-3 ) rr

3 4

[Maria-discuss] 10.2.7 - Specified key was too long; max key length is 1000 bytes
by Reindl Harald 31 Jul '17

31 Jul '17

what the hell is this when the MYISAM database has a utf8 charset while this don't happen with latin1_german1_ci - this seems to be a regression in 10.2 and wasted an hour of time to realize what is going on just because anotehr guy did not take care of the database charset create table `cms1_formmailer_generic_cc` (`fg_key` mediumint(7) unsigned not null auto_increment, `fg_form` varchar(255) not null default '', `fg_email` varchar(255) not null default '', primary key(`fg_key`), key`fg_key` (`fg_form`, `fg_email`)) - Specified key was too long; max key length is 1000 bytes

2 3

[Maria-discuss] MariaDB unable to read the /etc/krb5.keytab
by Ali, Saqib 24 Jul '17

24 Jul '17

I am trying to setup MariaDB 10 with GSSAPI support. I following the instructions here: https://mariadb.com/kb/en/mariadb/gssapi-authentication-plugin/ However, whenever I try to start Maria DB I get the following [Warning] mysqld: GSSAPI plugin : default principal 'mariadb/hostname.tld@REALM' not found in keytab [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure. Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty. [ERROR] Plugin 'gssapi' init function returned error. Sincerely, Saqib http://saqib.org

2 3

[Maria-discuss] TokuDB performance hit after 10.0.25
by Alessandro Ren 24 Jul '17

24 Jul '17

Hello, I've noticed a great performance hit after I upgraded my MariaDB install to 10.0.28, 10.0.29, 10.0.30 and 10.0.31. I even tried upgrading to MariaDB 10.2.7 and had the same problem. Bellow de details. MariaDB 10.0.25 - 13 rows in set (1.67 sec) MariaDB 10.0.31 - 13 rows in set (29.06 sec) The query: SELECT metric_id,date_format(entry_time, '%m:%Y') as date_group, unix_timestamp(entry_time) as entry_time, entry_time as datetime, avg(perf_value) as perf_value, warning, critical, baseline, lower_limit, upper_limit from service_perf_651 where service_id='56551' and metric_id='90183701' and entry_time>='2016-07-24 09:41:42' and entry_time<='2017-07-24 09:41:42' and ( (date_format(entry_time,'%w')=0 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H') < 24))) or (date_format(entry_time,'%w')=1 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=2 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=3 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=4 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=5 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) or (date_format(entry_time,'%w')=6 and ((date_format(entry_time,'%H')>=0 and date_format(entry_time,'%H')<24) )) ) group by date_group order by entry_time Explain query: +------+-------------+------------------+-------+----------------------------+---------+---------+------+------+----------------------------------------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +------+-------------+------------------+-------+----------------------------+---------+---------+------+------+----------------------------------------------+ | 1 | SIMPLE | service_perf_651 | range | PRIMARY,service_perf_1_idx | PRIMARY | 16 | NULL | 1 | Using where; Using temporary; Using filesort | +------+-------------+------------------+-------+----------------------------+---------+---------+------+------+----------------------------------------------+ 1 row in set (0.06 sec) The table: CREATE TABLE `service_perf_651` ( `entry_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `service_id` int(11) unsigned NOT NULL DEFAULT '0', `metric_id` int(11) unsigned NOT NULL DEFAULT '0', `perf_value` float(13,3) DEFAULT NULL, `warning` float(13,3) DEFAULT NULL, `critical` float(13,3) DEFAULT NULL, `baseline` float(13,3) DEFAULT NULL, `lower_limit` float(13,3) DEFAULT NULL, `upper_limit` float(13,3) DEFAULT NULL, `reserved0` float(13,3) DEFAULT NULL, `reserved1` float(13,3) DEFAULT NULL, `reserved2` float(13,3) DEFAULT NULL, PRIMARY KEY (`entry_time`,`service_id`,`metric_id`), KEY `service_perf_1_idx` (`service_id`,`metric_id`,`entry_time`) ) ENGINE=TokuDB DEFAULT CHARSET=utf8 `compression`='tokudb_snappy' The size: 32497415 records Any idea what could be wrong? I even tried everything above on a different HW where the databse fit in memory in TokuDB, with the same performance hit. Tks for the help Alessandro Ren

6 8

[Maria-discuss] How spy database alterations
by lemmel 21 Jul '17

21 Jul '17

Hi. Working with a web application (PHP, Nginx, MariaDB) that doesn't really work as expected, I'm looking for a way to monitor/spy database alterations done when some action is performed on the FrontEnd. It would be faster by far than to read the application's source code. So is there a non-invasive way to monitor/spy database alterations performed after a given time, or triggered manually ? Thanks ! P.S. : I know that I could add triggers on all database operation, but that would require adding a awful quantity of triggers and would not be easy to realize.

4 6

[Maria-discuss] -DWITH_SYSTEMD=ON is the same as -DWITH_SYSTEMD=OFF
by Reindl Harald 14 Jul '17

14 Jul '17

previously i had -DWITH_SYSTEMD=OFF and while trying to switch to Type=notify i switched that to -DWITH_SYSTEMD=ON - well, nothing mentions systemd (yes, systemd-devel is installed) remove the option completly and oh look: -- Looking for include file systemd/sd-daemon.h -- Looking for include file systemd/sd-daemon.h - found did i say that cmake is a bunch of crap already? a sane buildsystem won't need ON/OFF at all with params started by "WITH" or "WITHOUT".... like the old ./configure where on some projects like PHP you just start with --dsiable-all followed by --enable-x, --enable-y and all is fine and clear

3 6

[Maria-discuss] MariaDB 10.2.7 and libmysql compatibility
by Reindl Harald 13 Jul '17

13 Jul '17

i am missing something (probably simple like symbol versioning however done with some hack) or is it really not possible by providing symlinks to avoid "libmysqlclient.so.18 => not found" and all clients linked against 10.1.x failing? attached my current rpm-spec - the server itself works fine and i really want to avoid building a "server-only" package for the whole lifetime of Fedora25/26 as well as not wait for Fedora 27 to get 10.2.x [root@testserver:/usr/lib64/mysql]$ ls insgesamt 308K lrwxrwxrwx 1 root root 13 2017-07-13 13:15 libmysqlclient.so.18.0.0 -> libmariadb.so lrwxrwxrwx 1 root root 13 2017-07-13 13:15 libmysqlclient.so.18 -> libmariadb.so -rwxr-xr-x 1 root root 305K 2017-07-13 13:15 libmariadb.so.3 lrwxrwxrwx 1 root root 15 2017-07-13 13:15 libmariadb.so -> libmariadb.so.3 lrwxrwxrwx 1 root root 17 2017-07-13 13:15 libmysqlclient_r.so -> libmysqlclient.so lrwxrwxrwx 1 root root 13 2017-07-13 13:15 libmysqlclient.so -> libmariadb.so [root@testserver:/usr/lib64/mysql]$ ldd /usr/sbin/dbmail-imapd linux-vdso.so.1 (0x00007fff2fdfd000) libgmime-2.6.so.0 => /lib64/libgmime-2.6.so.0 (0x00007f0b0fd94000) libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f0b0fb42000) libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f0b0f82f000) libevent-2.0.so.5 => /lib64/libevent-2.0.so.5 (0x00007f0b0f7e5000) libzdb.so.11 => /lib64/libzdb.so.11 (0x00007f0b0f7d0000) libdbmail.so.0 => /usr/lib64/dbmail/libdbmail.so.0 (0x00007f0b0f759000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0b0f53b000) libc.so.6 => /lib64/libc.so.6 (0x00007f0b0f175000) libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007f0b0ede2000) libz.so.1 => /lib64/libz.so.1 (0x00007f0b0ebcc000) libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f0b0e95a000) libffi.so.6 => /lib64/libffi.so.6 (0x00007f0b0e750000) libmysqlclient.so.18 => not found libm.so.6 => /lib64/libm.so.6 (0x00007f0b0e447000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f0b0e243000) libssl.so.10 => /lib64/libssl.so.10 (0x00007f0b0dfd1000) libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f0b0db70000) libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f0b0d96a000) libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f0b0d768000) libmhash.so.2 => /lib64/libmhash.so.2 (0x00007f0b0d53c000) libevent_pthreads-2.0.so.5 => /lib64/libevent_pthreads-2.0.so.5 (0x00007f0b0d538000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f0b0d302000) /lib64/ld-linux-x86-64.so.2 (0x0000559e18ffe000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f0b0d0db000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f0b0cebe000) libmount.so.1 => /lib64/libmount.so.1 (0x00007f0b0cc74000) libgomp.so.1 => /lib64/libgomp.so.1 (0x00007f0b0ca46000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f0b0c7f9000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f0b0c513000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f0b0c30f000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f0b0c0dc000) libfreebl3.so => /lib64/libfreebl3.so (0x00007f0b0bed9000) libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f0b0bc96000) libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f0b0ba91000) librt.so.1 => /lib64/librt.so.1 (0x00007f0b0b889000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f0b0b678000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f0b0b474000)

2 3

[Maria-discuss] 10.2.7: main.subselect_no_opts fails
by Reindl Harald 13 Jul '17

13 Jul '17

Completed: Failed 1/1865 tests, 99.95% were successful _________________________________________ [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=4 --max-test-fail=0 --mysqld=--binlog-format=row --force --suites="main-,binlog-,csv-,funcs_1-,funcs_2-,handler-,heap-,maria-,optimizer_unfixed_bugs-,parts-,percona-,roles-,rpl-,sys_vars-,unit-,vcol-" --skip-test-list=/var/lib/mysql/skip-tests.txt' mysql rm -rf /usr/share/mysql-test/var/* _________________________________________ CURRENT_TEST: main.subselect_no_opts /usr/bin/mysqltest: Error on delete of '/usr/share/mysql-test/var/4/tmp/subselect.out.file.1' (Errcode: 2 "No such file or directory") mysqltest: In included file "/usr/share/mysql-test/t/subselect.test": included from /usr/share/mysql-test/t/subselect_no_opts.test at line 12: At line 5903: query 'Select (Select Sum(`TestCase`.Revenue) From mysql.slow_log E Where TestCase.TemplateID not in (Select 1 from mysql.slow_log where 2=2) ) As `ControlRev` From (Select 3 as Revenue, 4 as TemplateID) As `TestCase` Group By TestCase.Revenue, TestCase.TemplateID' failed: 1242: Subquery returns more than 1 row The result from queries just before the failure was: < snip > 2 SUBQUERY t2 ref b b 5 test.t1.a 2 Using index DROP TABLE t1,t2; # # MDEV-5991: crash in Item_field::used_tables # create table t1 (c int); select exists(select 1 from t1 group by `c` in (select `c` from t1)); exists(select 1 from t1 group by `c` in (select `c` from t1)) 0 drop table t1; # # MDEV-7565: Server crash with Signal 6 (part 2) # Select (Select Sum(`TestCase`.Revenue) From mysql.slow_log E Where TestCase.TemplateID not in (Select 1 from mysql.slow_log where 2=2) ) As `ControlRev` From (Select 3 as Revenue, 4 as TemplateID) As `TestCase` Group By TestCase.Revenue, TestCase.TemplateID; More results from queries before failure can be found in /usr/share/mysql-test/var/4/log/subselect_no_opts.log - saving '/usr/share/mysql-test/var/4/log/main.subselect_no_opts/' to '/usr/share/mysql-test/var/log/main.subselect_no_opts/' ***Warnings generated in error logs during shutdown after running tests: main.grant main.subselect3_jcl6 main.subselect_mat main.strict_autoinc_3heap main.func_time_hires main.failed_auth_3909 main.subselect_extra main.gis-json main.gis main.gis-precise main.subselect_no_opts main.explain main.get_diagnostics main.str_to_datetime_457 main.function_defaults main.execution_constants main.func_weight_string main.empty_server_name-8224 main.func_timestamp main.subselect_cache main.subselect_gis main.gcc296 main.flush_table 2017-07-13 15:35:31 140219388360448 [Warning] Sort aborted, host: localhost, user: root, thread: 164, query: select numeropost as a FROM t1 ORDER BY (SELECT 1 FROM t1 HAVING a=1) 2017-07-13 15:35:31 140219388360448 [Warning] Sort aborted, host: localhost, user: root, thread: 164, query: SELECT a FROM t1 GROUP BY a 2017-07-13 15:35:31 140219388360448 [Warning] Sort aborted, host: localhost, user: root, thread: 164, query: SELECT a FROM t1 GROUP BY a 2017-07-13 15:35:31 140219388360448 [Warning] Sort aborted, host: localhost, user: root, thread: 164, query: SELECT a FROM t1 2017-07-13 15:35:31 140219388360448 [Warning] Sort aborted, host: localhost, user: root, thread: 164, query: SELECT a FROM t1

1 0

Re: [Maria-discuss] 10.2.7 and xtradb in changelog
by Federico Razzoli 13 Jul '17

13 Jul '17

I don't find this extremely confusing (if it's a change to the code, it's not weird to see it in the changelog; filtering out things exposes us to bugs in the filtering process, which may hide important information) but I think that there is another confusing part. In this page: https://mariadb.com/kb/en/mariadb/why-does-mariadb-102-use-innodb-instead-o… I read: "Note, we still consider incorporating XtraDB optimizations, but as patches, rather than XtraDB as a whole" But then, it is not clear what exactly is or is not in MariaDB's InnoDB. Percona has a nice list of features: https://www.percona.com/doc/percona-server/LATEST/index.html It would be useful to have a list of which changes are applied to MariaDB's InnoDB. Hope it is not too hard to maintain. Cheers, Federico -------------------------------------------- Gio 13/7/17, Sergei Golubchik <serg(a)mariadb.org> ha scritto: Oggetto: Re: [Maria-discuss] 10.2.7 and xtradb in changelog A: "Reindl Harald" <h.reindl(a)thelounge.net> Cc: "Mailing-List mariadb" <maria-discuss(a)lists.launchpad.net> Data: Giovedì 13 luglio 2017, 12:35 Hi, Reindl! On Jul 13, Reindl Harald wrote: > Am 13.07.2017 um 11:55 schrieb Sergei Golubchik: > > On Jul 13, Reindl Harald wrote: > >> https://mariadb.com/kb/en/mariadb/mariadb-1027-changelog/ > >> > >> i thought xtradb is gone in 10.2.x > >> > >> is it back now with 10.2.7 or is the changelog a random wild mix of > >> commits with no context to the version of the release? > > > > Neither. Changelog is generated as "all commits that are present in the > > 10.2.7 history, but were not present in the 10.2.6 history". And all > > commits in 10.1 are merged into 10.2 eventually (because many 10.1 > > bugfixes apply to 10.2 too). > > > > So whatever was done to XtraDB in 10.1 it will be part of 10.2 revision > > history, even though XtraDB itself is disabled in 10.2 (and does not > > even compile there). > > > > I agree that it's confusing, but what can we do? Manually filter out all > > commits that contain the string "xtradb" from the changelog? > > well, at least some filters make sense because things like "Update > xtradb and innodb version to 5.6.36" are pure nonsense when innodb in > 10.2 AFAIK is 5.7 and so the complete changelog feels very useless and > instead beeing helpful it spreads doubt how that whole stuff works at > all when random pieces seems to get merged bewteen versions or at least > the changelog says so Okay. https://jira.mariadb.org/browse/MDEV-13312 Regards, Sergei Chief Architect MariaDB and security(a)mariadb.org _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp

4 3

[Maria-discuss] mariadb-covscan-stroverflow.patch (Fedora)
by Reindl Harald 13 Jul '17

13 Jul '17

how long does Fedora need to ship that patch which seems to apply still to 10.2.7 where i am asking mysqlf for years if i should include it in my own builds or trust upstream

2 1

[Maria-discuss] 10.2.7: innodb_flush_method = ALL_O_DIRECT
by Reindl Harald 13 Jul '17

13 Jul '17

it's one thing that xtradb is gone but when the server refuses to start instead just warn about no longer supported options this is *very bad* 2017-07-13 12:22:57 140560655323200 [ERROR] InnoDB: Unrecognized value ALL_O_DIRECT for innodb_flush_method 2017-07-13 12:22:57 140560655323200 [Note] InnoDB: Number of pools: 1 2017-07-13 12:22:57 140560655323200 [Note] InnoDB: Using SSE2 crc32 instructions 2017-07-13 12:22:57 140560655323200 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2017-07-13 12:22:57 140560655323200 [Note] InnoDB: Starting shutdown... 2017-07-13 12:22:57 140560655323200 [ERROR] Plugin 'InnoDB' init function returned error. 2017-07-13 12:22:57 140560655323200 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2017-07-13 12:22:57 140560655323200 [ERROR] Unknown/unsupported storage engine: innodb _______________________________ BTW: "InnoDB: Cannot open '/Volumes/dune/mysql_dbmail/ib_buffer_pool' for reading: No such file or directory" - who cares when "innodb_buffer_pool_dump_at_shutdown = 0" is set on purpose because writing some GB buffer_pool at shutdown takes longer than the whole reboot of a typical server these days

1 0

[Maria-discuss] JSON in MariaDB 10.2.7 and MySQL
by Peter Laursen 13 Jul '17

13 Jul '17

-- MariaDB 10.2.7 CREATE TABLE `jsontst`( `id` INT NOT NULL AUTO_INCREMENT, `str` JSON, PRIMARY KEY (`id`) ) ENGINE=Aria CHARSET=latin1; SHOW CREATE TABLE `jsontst`; /* returns CREATE TABLE `jsontst2` ( `id` int(11) NOT NULL AUTO_INCREMENT, `str` text DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=Aria DEFAULT CHARSET=latin1 PAGE_CHECKSUM=1 */ readings: https://jira.mariadb.org/browse/MDEV-9144 https://bugs.mysql.com/bug.php?id=86875 As you see except for JSON in MariaDB just being a synonym of TEXT there are two more significant differences 1) length: in MySQL JSON has the lenght of a LONGTEXT - in MariaDB it is a (plain) TEXT 2) encoding: in MySQL the utf8mb4 character set is enforced for JSON data - in MariaDB you may specify any character set. I think in particular 2nd point could cause problems (unicode garbling) when loading a dump with JSON data from MySQL. Basically because latin1 is still default character set in MariaDB. Are you aware of the 2 differences? I think the major reason for introducing JSON in MariaDB is compability concerns with MySQL. But the 2 points here are IMO incompabilites that could have been avoided?

2 4

[Maria-discuss] 10.2.7 and xtradb in changelog
by Reindl Harald 13 Jul '17

13 Jul '17

https://mariadb.com/kb/en/mariadb/mariadb-1027-changelog/ i thought xtradb is gone in 10.2.x is it back now with 10.2.7 or is the changelog a random wild mix of commits with no context to the version of the release? ______________________________ Revision #546a89ca58 2017-05-18 16:16:18 +0300 Update xtradb and innodb version to 5.6.36 Revision #f880200974 2017-05-20 17:47:07 +0300 After-merge fix: Correct the 32-bit XtraDB result diff. Revision #fe291c687d 2017-05-20 08:43:25 +0300 After-merge fix: Correct the XtraDB result diff. Revision #4df726e180 2017-07-10 00:05:06 +0300 storage_engine subsuites should also be disabled for XtraDB

3 5