- 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

[Maria-discuss] incomplete provide of symlinks with 10.2.7
by Reindl Harald 13 Jul '17

13 Jul '17

Fedora just started to work on MariaDB 10.2 packaging they create compat symlinks for a sane transition and i try to backport that to my F25 builds with change as less as possible on my existing "mariadb.spec" 10.2.7 seems to do the same now (Fedora last night was still on 10.2.6) well, "libmysqlclient.so.18" is missing in your upstream compat links while "libmysqlclient.so" and "libmysqlclient_r.so" gave an error "ln: failed to create symbolic link 'libmysqlclient.so': File exists" within rpmbuild https://koji.fedoraproject.org/koji/buildinfo?buildID=918138 ___________________________________________ pushd %{buildroot}%{_libdir}/mysql/ ln -s libmariadb.so libmysqlclient.so ln -s libmariadb.so libmysqlclient.so.18 ln -s libmariadb.so libmysqlclient_r.so popd ___________________________________________ + pushd /home/builduser/rpmbuild/BUILDROOT/mariadb-10.2.7-3.fc25.20170713.rh.x86_64/usr/lib64/mysql/ ~/rpmbuild/BUILDROOT/mariadb-10.2.7-3.fc25.20170713.rh.x86_64/usr/lib64/mysql ~/rpmbuild/BUILD/mariadb-10.2.7 + ln -s libmariadb.so libmysqlclient.so.18 + popd ~/rpmbuild/BUILD/

2 2

[Maria-discuss] MariaDB 10.2.7 now available
by Daniel Bartholomew 12 Jul '17

12 Jul '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.7. This is a stable (GA) release. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.7 - Release Notes: https://mariadb.com/kb/en/mdb-1027-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1027-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.7 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - 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://mariadb.org/jira - - 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 - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Galera cluster for databases replication over three servers
by Martin LEUSCH 11 Jul '17

11 Jul '17

Hi, I'm setting up a new mail infrastructure withe 3 servers running Debian Jessie, data can be read or write from these 3 servers at any time. I chosed Galera with with MariaDB 10.2 to share databases between servers for services like AMAVIS, dovecot, ... I had a lot of errors in my logs (almost each time a service access to a DB), for example: Jul 11 07:00:01 mail mysqld[1302]: 2017-07-11 7:00:01 140256990783232 [Warning] Aborted connection 14812 to db: 'sogo' user: 'sogo' host: 'localhost' (Got an error reading communication packets) Jul 11 10:15:17 mailfilter mysqld[3714]: 2017-07-11 10:15:17 139644624377600 [Warning] Aborted connection 399 to db: 'amavisd' user: 'amavisd' host: 'localhost' (Got timeout reading communication packets) I wonder if in this case Galera is a good choice for databases replication and if there is a way to avoid this kind of errors. Thanks -- Martin LEUSCH <martin.leusch(a)imrcom.fr>

1 0

[Maria-discuss] TRIGGERing on new users
by Curtis Brown 07 Jul '17

07 Jul '17

I apologize in advance if this is the wrong venue; please point me in a more correct direction if that's the case. I want to perform some extra database functions when a new user is created in our MariaDB installation. What I am learning though is that I can't CREATE TRIGGERs against system tables like the user table in the mysql database. I am using MariaDB v10.1.24 in an Ubuntu 16.04.2 environment Have others run across a similar situation? Are there techniques to work around this? One thought I had was to enable general query log and either monitor the file output or TRIGGER on the general_log table. Are there any better suggestions? Thanks in advance. -- Curtis Brown, unix system administrator For general PC questions, Academic Computing and Networking Services call: 970-491-7276 Colorado State University email: help(a)colostate.edu curtis.brown(a)colostate.edu http://lib.colostate.edu/helpdesk/

2 4

[Maria-discuss] Broken MariaDB client ARGGG!!!
by Jon Foster 06 Jul '17

06 Jul '17

I'm constantly astounded at the extreme cavalier attitude that MySQL/MariaDB has had towards backwards compatibility for the nearly two decades I've worked with it. Its like you hate the developers that use your stuff. What's up with this?!?! I decided I better install the latest updates to my Deb7 64bit MariaDB install. WTF! Now all of my PHP apps are griping about: ---- symbol client_errors, version libmysqlclient_18 not defined in file libmysqlclient.so.18 ... ---- And it was working so well ten minutes ago. 10.2 even did away with the previous gripes from v10.1. :-/ But with the update to 10.2.6+maria~wheezy of the client libraries from your Debian repositories my clients' sites are down. Please fix. I'll find someway to install older functional code again. - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. jon(a)jfpossibilities.com 541-410-2760 Making computers work for you!

5 6

[Maria-discuss] How to deal with text pasted from Word?
by David Karr 06 Jul '17

06 Jul '17

I've inherited a small webapp that is using MariaDB for persistence. Some of the forms have textarea fields for extended text to be entered. Someone reported an issue saving a form with some text that they had pasted from an email. The message started with this: ------------------ Caused by: org.mariadb.jdbc.internal.util.dao.QueryException: Incorrect string value: '\xC2\x95\x09Onb...' for column 'ssimpact' at row 1 ---------------- I found where "Onb" is in the text, and right before it is a "bullet" character. So, this appeared to be a Unicode conversion issue. I tried pasting the same text after it had been passed to me, and it didn't fail. I'm pretty sure it didn't fail because that process of "passing it around" filtered the text to be all valid characters. The person who reported the problem said that when she just resubmitted it, it didn't fail. That might also point to a "cleansing" process that resulted in the submitted characters being legal. What are some reasonable strategies for getting this to work a little better?

1 1

[Maria-discuss] legacy InnoDB compressed tables using row_format=compressed
by Lukas Lehner 05 Jul '17

05 Jul '17

Hey Quote from https://mariadb.com/kb/en/mariadb/compression/ This approach differs significantly from legacy InnoDB compressed tables using row_format=compressed, where both uncompressed and compressed pages can be in the buffer pool. Any details why this is legacy? Should not be used? With a search engine I found a very old blog posting "InnoDB compression woes" from Percona. row_format=compressed is attractive when you pay your DBaaS per GB (storage based usage). Any insides? Lukas

2 1

[Maria-discuss] Best place to report RocksDB issues?
by jocelyn fournier 05 Jul '17

05 Jul '17

Hi all, Mark, What's the best place to report RocksDB issues? MariaDB/Percona JIRA, https://github.com/facebook/rocksdb/issues , any other places? Thanks! Jocelyn

2 1

[Maria-discuss] MariaDB 10.1.25 now available
by Daniel Bartholomew 04 Jul '17

04 Jul '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.25, MariaDB Connector/J 2.0.3, and MariaDB Connector/J 1.6.2. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.25 - Release Notes: https://mariadb.com/kb/en/mdb-10125-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10125-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.25 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.0.3 - Release Notes: https://mariadb.com/kb/en/mcj-203-rn/ - Changelog: https://mariadb.com/kb/en/mcj-203-cl/ - Downloads: https://downloads.mariadb.org/connector-java/2.0.3/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/J 1.6.2 - Release Notes: https://mariadb.com/kb/en/mcj-162-rn/ - Changelog: https://mariadb.com/kb/en/mcj-162-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.6.2/ About MariaDB Connector/J: - https://mariadb.com/kb/en/about-mariadb-connector-j/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - 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://mariadb.org/jira - - 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 - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] [MariaDB 10.2.6] [PHP 7.1.6] error: /usr/bin/ld: cannot find -lmysqlclient | wrong mysql library version or lib not found
by Guillermo Cespedes 04 Jul '17

04 Jul '17

Hi, I am compiling MariaDB 10.2.6 and PHP 7.1.6 I'm trying it on Debian 8.8 32x and x64 on DigitalOcean See the script: https://gist.github.com/dertin/8de14e458dd4f0d3acb5f0deff120951 <https://gist.github.com/dertin/8de14e458dd4f0d3acb5f0deff120951> But I have problems compiling PHP with MariaDB / MySQLi. Should I check something at the Mariadb installation? # grep 'mysql’ config.log $ ./configure --prefix=/usr/local/php7 --enable-huge-code-pages --with-config-file-scan-dir=/usr/local/php7/etc/conf.d --without-pear --enable-bcmath --with-bz2 --enable-calendar --enable-intl --enable-exif --enable-dba --enable-ftp --with-gettext --with-gd --with-jpeg-dir --enable-mbstring --with-mcrypt --with-mhash --enable-mysqlnd --with-mysql-sock=/var/run/mysqld/mysqld.sock --with-mysqli=/usr/local/mysql/bin/mariadb_config --with-pdo-mysql=/usr/local/mysql --with-openssl --enable-pcntl --with-pspell --enable-shmop --enable-soap --enable-sockets --enable-sysvmsg --enable-sysvsem --enable-sysvshm --enable-wddx --with-zlib --enable-zip --with-readline --with-curl --enable-simplexml --enable-xmlreader --enable-xmlwriter --enable-fpm --with-fpm-user=www-data --with-fpm-group=www-data ... configure:52615: result: /var/run/mysqld/mysqld.sock configure:52749: checking for mysql_set_server_option in -lmysqlclient configure:52774: cc -o conftest -I/usr/include -g -O2 -fvisibility=hidden -Wl,-rpath,/usr/local/mysql/lib/ -L/usr/local/mysql/lib/ -L/usr/lib -Wl,-rpath,/usr/local/lib -L/usr/local/lib -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -lmariadb -ldl -lm -lssl -lcrypto conftest.c -lmysqlclient -lmcrypt -lltdl -lstdc++ -lpng -lz -ljpeg -lcurl -lbz2 -lz -lrt -lm -ldl -lnsl -lxml2 -lz -lm -ldl -lssl -lcrypto -lcurl -lxml2 -lz -lm -ldl -lssl -lcrypto -licui18n -licuuc -licudata -licuio >&5 /usr/bin/ld: cannot find -lmysqlclient | char mysql_set_server_option (); | return mysql_set_server_option (); configure:53081: error: wrong mysql library version or lib not found. Check config.log for more information. ac_cv_lib_mysqlclient___mysql_set_server_option=no Tested with: --with-mysqli=/usr/local/mysql/bin/mysql_config --with-mysqli=/usr/local/mysql/bin/mariadb_config related to: https://lists.launchpad.net/maria-discuss/msg04668.html What do you think? Guillermo Céspedes Full Stack Developer

2 2

[Maria-discuss] I expected the same values for mariadb_config, mysql_config and my_print_defaults --mysqld
by Guillermo Cespedes 04 Jul '17

04 Jul '17

Hi, The values are not correct, they are even different, I expected the same values. See socket and version. # /usr/local/mysql/bin/mariadb_config Copyright 2011-2015 MariaDB Corporation AB Get compiler flags for using the MariaDB Connector/C. Usage: mariadb_config [OPTIONS] --cflags [-I/usr/local/mysql/include/mysql -I/usr/local/mysql/include/mysql/mysql] --include [-I/usr/local/mysql/include/mysql -I/usr/local/mysql/include/mysql/mysql] --libs [-L/usr/local/mysql/lib/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto] --libs_r [-L/usr/local/mysql/lib/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto] --libs_sys [-lpthread -ldl -lm -lssl -lcrypto] --version [10.2.5] --socket [/tmp/mysql.sock] --port [3306] --plugindir [/usr/local/mysql/lib/plugin] --tlsinfo [OpenSSL 1.1.0f] # /usr/local/mysql/bin/mysql_config Usage: /usr/local/mysql/bin/mysql_config [OPTIONS] Options: --cflags [-I/usr/local/mysql/include/mysql -I/usr/local/mysql/include/mysql/.. ] --include [-I/usr/local/mysql/include/mysql -I/usr/local/mysql/include/mysql/..] --libs [-L/usr/local/mysql/lib -lmariadb] --libs_r [-L/usr/local/mysql/lib -lmariadb] --plugindir [/usr/local/mysql/lib/plugin] --socket [/tmp/mysql.sock] --port [0] --version [10.2.6] --libmysqld-libs [-L/usr/local/mysql/lib -lmysqld -lpthread -lz -lm -ldl -lssl -lcrypto -lpcre -lcrypt -llz4 -laio] --variable=VAR VAR is one of: pkgincludedir [/usr/local/mysql/include/mysql] pkglibdir [/usr/local/mysql/lib] plugindir [/usr/local/mysql/lib/plugin] # my_print_defaults --mysqld --port=3306 --socket=/var/run/mysqld/mysqld.sock --skip-external-locking --key_buffer_size=16M --max_allowed_packet=1M --table_open_cache=64 --sort_buffer_size=512K --net_buffer_length=8K --read_buffer_size=256K --read_rnd_buffer_size=512K --myisam_sort_buffer_size=8M --log-bin=mysql-bin --binlog_format=mixed --server-id=1 --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --tmpdir=/tmp --lc-messages-dir=/usr/local/mysql/share --skip-external-locking --bind-address=127.0.0.1 --key_buffer=16M --max_allowed_packet=16M --thread_stack=192K --thread_cache_size=8 --myisam-recover=BACKUP --query_cache_limit=1M --query_cache_size=16M --log_error=/var/log/mysql/error.log --expire_logs_days=10 --max_binlog_size=100M Guillermo Céspedes Full Stack Developer

2 2

Re: [Maria-discuss] Can't open shared library '/usr/lib64/mysql/plugin/auth_socket.so'
by Daniel Black 04 Jul '17

04 Jul '17

On 03/07/17 22:54, Jonathan Gazeley wrote: > On 03/07/17 13:38, Ian Gilfillan wrote: >> On 03/07/2017 14:13, Jonathan Gazeley wrote: >>> >>> It fails to find auth_socket.so, but when I check in yum what >>> provides that file, only MariaDB 5.5 from the CentOS repo has it, but >>> not MariaDB 10.1 from the MariaDB repo. I read in the notes that >>> auth_socket is deprecated and going in 10.2. My config file specifies >>> 'loose-plugin-load=auth_socket'. If I just remove this line, will it >>> work? Will it break wsrep? >>> >> In which notes did you read about auth_socket being deprecated? > > In /etc/my.cnf.d/mariadb-enterprise.cnf: > > # This is to accommodate upgrades to MariaDB 10.2, which does not include > # the Unix socket plugin built into the server. > loose-plugin-load=auth_socket > > Makes it sound like auth_socket is going away - or at least is opt-in in > 10.2. Its built in to the 10.2 server rather than being a separate shared library like <10.2

1 0

[Maria-discuss] Duplication of documentation for binlog annotation and a question on replicate_annotate_row_events not being dynamic
by Jean-Francois B. Gagne 03 Jul '17

03 Jul '17

Hi all, This is a documentation organisation question and a technical question on replicate_annotate_row_events not being dynamic. In [1], we can find the documentation for the options binlog-annotate-row-events and replicate-annotate-row-events, and [2] points to [1]. However, there is a duplication of that documentation in [3] and [4], is there a reason for that (there is a risk of those 2 documentation diverging) ? [1]: https://mariadb.com/kb/en/mariadb/annotate_rows_log_event/ [2]: https://mariadb.com/kb/en/mariadb/mysqld-options/ [3]: https://mariadb.com/kb/en/mariadb/replication-and-binary-log-server-system-… [4]: https://mariadb.com/kb/en/mariadb/replication-and-binary-log-server-system-… And the technical question about replicate_annotate_row_events: this variable is not dynamic, is there a reason for that ? I understand that this variable could/should only be modifiable while the slave is stopped, but not being dynamic is not very DBA/SysAdmin/Operator friendly. Many thanks, Jean-François Gagné

3 2

[Maria-discuss] how to build MariaDB from source
by Reindl Harald 03 Jul '17

03 Jul '17

i get tired - "-DPLUGIN_INNODB=YES" leads to failures at configure time - each time the same dance when the version changes well, when remove that thinking since xtradb is now dead it will be default enabled leads finally still to a build-failure with not mentioning really where and why - can we please have back "configure && make && make install" with "./configure --help" back for peace of mind _______________________________ [ 53%] Linking CXX static library libmyisammrg.a *why* at all when i say "-DPLUGIN_MYISAMMRG=NO" but remove it does still make no difference _______________________________ cmake . \ -DFEATURE_SET="large" \ -DCMAKE_INSTALL_PREFIX="%{_prefix}" \ -DINSTALL_INCLUDEDIR=include/mysql \ -DINSTALL_LAYOUT=RPM \ -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_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 \ -DSECURITY_HARDENED=OFF \ -DWITH_LIBWRAP=OFF \ -DWITH_MARIABACKUP=OFF \ -DWITH_PIC=NO \ -DWITH_READLINE=OFF \ -DWITH_SAFEMALLOC=OFF \ -DWITH_SYSTEMD=OFF \ -DWITH_VALGRIND=OFF \ -DWITH_WSREP=OFF \ -DWITH_JEMALLOC=system \ -DWITH_SSL=system \ -DWITH_ZLIB=system \ -DCOMPILATION_COMMENT="thelounge" cd /home/builduser/rpmbuild/BUILD/mariadb-10.2.6/storage/myisam && /usr/bin/cmake -P CMakeFiles/myisam.dir/cmake_clean_target.cmake cd /home/builduser/rpmbuild/BUILD/mariadb-10.2.6/storage/myisam && /usr/bin/cmake -E cmake_link_script CMakeFiles/myisam.dir/link.txt --verbose=1 /usr/bin/ar qc libmyisam.a CMakeFiles/myisam.dir/ft_boolean_search.c.o CMakeFiles/myisam.dir/ft_nlq_search.c.o CMakeFiles/myisam.dir/ft_parser.c.o CMakeFiles/myisam.dir/ft_static.c.o CMakeFiles/myisam.dir/ha_myisam.cc.o CMakeFiles/myisam.dir/ft_myisam.c.o CMakeFiles/myisam.dir/ft_stopwords.c.o CMakeFiles/myisam.dir/ft_update.c.o CMakeFiles/myisam.dir/mi_cache.c.o CMakeFiles/myisam.dir/mi_changed.c.o CMakeFiles/myisam.dir/mi_check.c.o CMakeFiles/myisam.dir/mi_checksum.c.o CMakeFiles/myisam.dir/mi_close.c.o CMakeFiles/myisam.dir/mi_create.c.o CMakeFiles/myisam.dir/mi_dbug.c.o CMakeFiles/myisam.dir/mi_delete.c.o CMakeFiles/myisam.dir/mi_delete_all.c.o CMakeFiles/myisam.dir/mi_delete_table.c.o CMakeFiles/myisam.dir/mi_dynrec.c.o CMakeFiles/myisam.dir/mi_extra.c.o CMakeFiles/myisam.dir/mi_info.c.o CMakeFiles/myisam.dir/mi_key.c.o CMakeFiles/myisam.dir/mi_keycache.c.o CMakeFiles/myisam.dir/mi_locking.c.o CMakeFiles/myisam.dir/mi_log.c.o CMakeFiles/myisam.dir/mi_open.c.o CMakeFiles/myisam.dir/mi_packrec.c.o CMakeFiles/myisam.dir/mi_page.c.o CMakeFiles/myisam.dir/mi_panic.c.o CMakeFiles/myisam.dir/mi_preload.c.o CMakeFiles/myisam.dir/mi_range.c.o CMakeFiles/myisam.dir/mi_rename.c.o CMakeFiles/myisam.dir/mi_rfirst.c.o CMakeFiles/myisam.dir/mi_rlast.c.o CMakeFiles/myisam.dir/mi_rnext.c.o CMakeFiles/myisam.dir/mi_rnext_same.c.o CMakeFiles/myisam.dir/mi_rprev.c.o CMakeFiles/myisam.dir/mi_rrnd.c.o CMakeFiles/myisam.dir/mi_rsame.c.o CMakeFiles/myisam.dir/mi_rsamepos.c.o CMakeFiles/myisam.dir/mi_scan.c.o CMakeFiles/myisam.dir/mi_search.c.o CMakeFiles/myisam.dir/mi_static.c.o CMakeFiles/myisam.dir/mi_statrec.c.o CMakeFiles/myisam.dir/mi_unique.c.o CMakeFiles/myisam.dir/mi_update.c.o CMakeFiles/myisam.dir/mi_write.c.o CMakeFiles/myisam.dir/rt_index.c.o CMakeFiles/myisam.dir/rt_key.c.o CMakeFiles/myisam.dir/rt_mbr.c.o CMakeFiles/myisam.dir/rt_split.c.o CMakeFiles/myisam.dir/sort.c.o CMakeFiles/myisam.dir/sp_key.c.o CMakeFiles/myisam.dir/mi_rkey.c.o /usr/bin/ranlib libmyisam.a make[2]: Leaving directory '/home/builduser/rpmbuild/BUILD/mariadb-10.2.6' [ 52%] Built target myisam make[1]: Leaving directory '/home/builduser/rpmbuild/BUILD/mariadb-10.2.6' Makefile:162: recipe for target 'all' failed make: *** [all] Error 2 Fehler: Fehler-Status beim Beenden von /var/tmp/rpm-tmp.Qwgvnq (%build) Fehler beim Bauen des RPM: Fehler-Status beim Beenden von /var/tmp/rpm-tmp.Qwgvnq (%build)

2 5

[Maria-discuss] Can't open shared library '/usr/lib64/mysql/plugin/auth_socket.so'
by Jonathan Gazeley 03 Jul '17

03 Jul '17

Hi folks, I did a routine reboot on one of my database nodes and it was unable to start up wsrep afterwards. I'm running MariaDB 10.1.24 with Galera 25.3.20 on CentOS 7.3.1611 (latest). Jul 03 09:53:07 db2.example.com sh[14400]: WSREP: Failed to start mysqld for wsrep recovery: '2017-07-03 9:50:49 139825954236672 [ERROR] Can't open shared library '/usr/lib64/mysql/plugin/auth_socket.so' (errno: 0, cannot open shared object file: No such file or directory) Jul 03 09:53:07 db2.example.com sh[14400]: 2017-07-03 9:50:49 139825954236672 [ERROR] Couldn't load plugins from 'auth_socket.so'. It fails to find auth_socket.so, but when I check in yum what provides that file, only MariaDB 5.5 from the CentOS repo has it, but not MariaDB 10.1 from the MariaDB repo. I read in the notes that auth_socket is deprecated and going in 10.2. My config file specifies 'loose-plugin-load=auth_socket'. If I just remove this line, will it work? Will it break wsrep? Can someone explain this to me? Right now I am nervous because if the other nodes also can't start up wsrep after rebooting then I will lose my cluster. I'm looking for ways to resolve the problem and get the node back online. I'm happy to upgrade to 10.2 if necessary. Thanks, Jonathan

3 3

[Maria-discuss] R: Can't open shared library '/usr/lib64/mysql/plugin/auth_socket.so'
by Federico Razzoli 03 Jul '17

03 Jul '17

It is just a simpler way to do authentication: https://mariadb.com/kb/en/mariadb/unix_socket-authentication-plugin/ Unless you use it intentionally, I don't think it can break anything. I'd just comment the line and then, for consistency, I'd uninstall that plugin in other nodes in case it is installed. Federico -------------------------------------------- Lun 3/7/17, Jonathan Gazeley <Jonathan.Gazeley(a)bristol.ac.uk> ha scritto: Oggetto: [Maria-discuss] Can't open shared library '/usr/lib64/mysql/plugin/auth_socket.so' A: maria-discuss(a)lists.launchpad.net Data: Lunedì 3 luglio 2017, 14:13 Hi folks, I did a routine reboot on one of my database nodes and it was unable to start up wsrep afterwards. I'm running MariaDB 10.1.24 with Galera 25.3.20 on CentOS 7.3.1611 (latest). Jul 03 09:53:07 db2.example.com sh[14400]: WSREP: Failed to start mysqld for wsrep recovery: '2017-07-03 9:50:49 139825954236672 [ERROR] Can't open shared library '/usr/lib64/mysql/plugin/auth_socket.so' (errno: 0, cannot open shared object file: No such file or directory) Jul 03 09:53:07 db2.example.com sh[14400]: 2017-07-03 9:50:49 139825954236672 [ERROR] Couldn't load plugins from 'auth_socket.so'. It fails to find auth_socket.so, but when I check in yum what provides that file, only MariaDB 5.5 from the CentOS repo has it, but not MariaDB 10.1 from the MariaDB repo. I read in the notes that auth_socket is deprecated and going in 10.2. My config file specifies 'loose-plugin-load=auth_socket'. If I just remove this line, will it work? Will it break wsrep? Can someone explain this to me? Right now I am nervous because if the other nodes also can't start up wsrep after rebooting then I will lose my cluster. I'm looking for ways to resolve the problem and get the node back online. I'm happy to upgrade to 10.2 if necessary. Thanks, Jonathan _______________________________________________ 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] [mysqld] Can't find messagefile '/usr/share/mysql/errmsg.sys'
by Guillermo Cespedes 30 Jun '17

30 Jun '17

Hi, Compilation Instructions: # uname -a Linux framework 3.16.0-4-686-pae #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) i686 GNU/Linux # groupadd mysql # useradd -c "MySQL Server" -g mysql -s /bin/false mysql # cmake . -DBUILD_CONFIG=mysql_release \ -DCMAKE_C_FLAGS="-I/usr/local/include -I/usr/include/i386-linux-gnu" \ -DWITH_INNODB_LZ4=ON -DWITH_INNODB_LZMA=OFF -DWITH_INNODB_LZO=OFF \ -DWITH_ZLIB=system -DWITH_SSL=system \ -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_spanish_ci \ -DWITH_DEBUG=0 -DWITH_VALGRIND=0 # make # make install # export PATH=$PATH:/usr/local/mysql/bin # echo "export PATH=$PATH:/usr/local/mysql/bin" >> /etc/profile # source /etc/profile # cd /usr/local/mysql # chown -R root . # chown -R mysql data # cp ./support-files/my-medium.cnf /etc/my.cnf # ./scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --verbose # cp ./support-files/mysql.server /etc/init.d/mysql # chmod +x /etc/init.d/mysql # update-rc.d mysql defaults # service mysql start # ./bin/mysql_secure_installation # ./bin/mysqladmin -u root password Error: # mysqld 2017-06-28 21:37:24 3071039232 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead. 2017-06-28 21:37:24 3071039232 [Note] mysqld (mysqld 10.2.6-MariaDB-log) starting as process 2600 ... 2017-06-28 21:37:24 3071039232 [ERROR] Can't find messagefile '/usr/share/mysql/errmsg.sys' 2017-06-28 21:37:24 3071039232 [ERROR] Aborting # ls -l /usr/share/mysql ls: cannot access /usr/share/mysql: No such file or directory How to indicate the correct directory permanently ? /usr/share/mysql to /usr/local/mysql/share # ls /usr/local/mysql/share aclocal german mysql_performance_tables.sql romanian charsets greek mysql_system_tables_data.sql russian czech hungarian mysql_system_tables.sql serbian danish install_spider.sql mysql_test_data_timezone.sql slovak dutch italian mysql_to_mariadb.sql spanish english japanese norwegian swedish errmsg-utf8.txt korean norwegian-ny ukrainian estonian maria_add_gis_sp_bootstrap.sql pkgconfig fill_help_tables.sql maria_add_gis_sp.sql polish french mroonga portuguese Guillermo Céspedes Full Stack Developer

2 5

[Maria-discuss] Parser language
by Roberto Spadim 28 Jun '17

28 Jun '17

Hi guys, sometime ago i asked if we could select what parser we are using, with an example with nosql (handler socket) or sql, without new socket connection Show we consider this as something we will need? Check that new query ideas are next door: http://probcomp.csail.mit.edu/bayesdb/ -- Roberto Spadim SPAEmpresarial - Software ERP Eng. Automação e Controle

1 0

[Maria-discuss] MariaDB 10.2 innodb page_clean question ?
by Ljr Yang 26 Jun '17

26 Jun '17

Hi, Recently, we upgrade 8 MariaDB slaves from MariaDB 10.1.22 to MariaDB 10.2.6. In error log, it frequent occurrence some innodb Note: ............. 2017-06-26 9:01:03 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 6142ms. The settings might not be optimal. (flushed=16 and evicted =0, during the time.) 2017-06-26 9:03:54 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4584ms. The settings might not be optimal. (flushed=8 and evicted= 0, during the time.) 2017-06-26 9:05:58 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4728ms. The settings might not be optimal. (flushed=8 and evicted= 0, during the time.) 2017-06-26 9:08:49 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 5016ms. The settings might not be optimal. (flushed=8 and evicted= 0, during the time.) 2017-06-26 9:09:12 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4990ms. The settings might not be optimal. (flushed=8 and evicted= 0, during the time.) 2017-06-26 9:11:27 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 5387ms. The settings might not be optimal. (flushed=8 and evicted= 0, during the time.) 2017-06-26 9:14:43 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 6463ms. The settings might not be optimal. (flushed=0 and evicted= 0, during the time.) 2017-06-26 9:16:27 140022654363392 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4031ms. The settings might not be optimal. (flushed=40 and evicted =0, during the time.) ............ Now, It have not affect the normal use, but we could not confirm, it is our config problem or other reasons? Please help confirm, thanks.

1 0

[Maria-discuss] MariaDB and Intel TSX
by Reindl Harald 25 Jun '17

25 Jun '17

does MariaDB make usage of TSX on newer hardware or at least using glibc for the query cache mutex which would implicit benfit form it? just curious because next year we replace our cluster nodes and put them in a EVC mode where TSX instrcutions are supported https://en.wikipedia.org/wiki/Transactional_Synchronization_Extensions https://www.flamingspork.com/blog/2014/06/05/performance-impact-of-mysql-qu… https://lwn.net/Articles/534758/

2 2

[Maria-discuss] Help to compile MariaDB 10.2.6 - Debian 8.8
by Guillermo Céspedes Tabárez 23 Jun '17

23 Jun '17

Hello I need help to add in my script ( https://gist.github.com/dertin/8de14e458dd4f0d3acb5f0deff120951#file-instal… ) the compilation of "MariaDB 10.2.6" from its source code. Must work for Debian 8.8 32bit and 64bit Thank you

4 16

[Maria-discuss] memory allocators and MariaDB
by MARK CALLAGHAN 20 Jun '17

20 Jun '17

Do MariaDB 10.2 binaries use glibc malloc or get built with one of tcmalloc or jemalloc? Sorry for being lazy, as I have yet to install it. -- Mark Callaghan mdcallag(a)gmail.com

3 8

[Maria-discuss] mariadb 10.2.6 make test failures
by Bruce Dubbs 20 Jun '17

20 Jun '17

I am trying to build mariadb from source on a linux system. I used this procedure: mkdir build cd build cmake -DTOKUDB_OK=0 .. make make test The build goes fine, but the output of make test gives: 74% tests passed, 21 tests failed out of 81 Total Test time (real) = 42.80 sec The following tests FAILED: 23 - bulk1 (Failed) 24 - performance (Failed) 25 - basic-t (Failed) 26 - fetch (Failed) 27 - charset (Failed) 28 - logs (Failed) 29 - cursor (Failed) 30 - errors (Failed) 31 - view (Failed) 32 - ps (Failed) 33 - ps_bugs (Failed) 34 - sp (Failed) 35 - result (Failed) 36 - connection (Failed) 37 - misc (Failed) 38 - ps_new (Failed) 39 - sqlite3 (Failed) 40 - thread (Failed) 41 - features-10_2 (Failed) 42 - dyncol (Failed) 43 - async (Failed) Errors while running CTest All the failing tests have messages in the log like: # Couldn't establish connection to server (null). Error (2002): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) Bail out! Can't connect to a server. Aborting.... All the above tests appear to be new to version 10.2. I used the asme build procedure for version 10.1.23 and all tests pass, but none of the above tests show up on the earlier version either. What am I missing? If the tests need a server running, shouldn't the tests start the server? -- Bruce

3 4

[Maria-discuss] MariaDB new installation on Centos 6
by romeo kalebic 18 Jun '17

18 Jun '17

Hi everyone, I'm new user of MariaDB, and I install it on Centos 6.8 64bit. I install it using yum utility , according instruction on MariaDB site: https://mariadb.com/kb/en/mariadb/yum/. yum install MariaDB-server MariaDB-client finished without any problem. I can use mysql client to connect to databases without any problems. Then I try to compile some of my applications. To find out what library to use and where include files are I use mysql_config and mariadb_config. mysql_config output: [root@xms tests]# mysql_config Usage: /usr/bin/mysql_config [OPTIONS] Options: --cflags [-I/usr/include/mysql ] --include [-I/usr/include/mysql] --libs [-L/usr/lib64 -lmariadb] --libs_r [-L/usr/lib64 -lmariadb] --plugindir [/usr/lib64/mysql/plugin] --socket [/var/lib/mysql/mysql.sock] --port [0] --version [10.2.6] --libmysqld-libs [-L/usr/lib64 -lmysqld -lpthread -lz -lm -lrt -ldl -lssl -lcrypto -lcrypt -laio] --variable=VAR VAR is one of: pkgincludedir [/usr/include/mysql] pkglibdir [/usr/lib64] plugindir [/usr/lib64/mysql/plugin] [root@xms tests]# And mariadb_config returns: [root@xms tests]# mariadb_config Copyright 2011-2015 MariaDB Corporation AB Get compiler flags for using the MariaDB Connector/C. Usage: mariadb_config [OPTIONS] --cflags [-I/usr/include/mysql -I/usr/include/mysql/mysql] --include [-I/usr/include/mysql -I/usr/include/mysql/mysql] --libs [-L/usr/lib64/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto] --libs_r [-L/usr/lib64/ -lmariadb -lpthread -ldl -lm -lssl -lcrypto] --libs_sys [-lpthread -ldl -lm -lssl -lcrypto] --version [10.2.5] --socket [/var/lib/mysql/mysql.sock] --port [3306] --plugindir [/usr/lib64/mysql/plugin] --tlsinfo [OpenSSL 1.0.1e] [root@xms tests]# First question is why these two outputs are different? I wrote Makefile and use -I and -L like this in mysql_config. gcc compiler finish with error that there is no mariadb library. What I have missed? Where is libmariadb located? Best Regards, Romeo <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

3 3

[Maria-discuss] Question about mariadb 10.2 "rows" keyword
by Rod Bio 14 Jun '17

14 Jun '17

Hi everyone, Apologies I am not a native english speaker so my english will be weird and database is not my specialty, but I would just like to ask something about mariadb specifically version 10.2 I just recently upgraded to 10.2 from 5.5 and somewhat we had problem displaying our data. Anyway we've traced the issue, after trying to replicate the database, to a specific table. What we found is that when we create a table with a column named "rows" it would return an error. e.g. MariaDB [test]> create table test (rows int); ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'rows int)' at line 1 Only by using `` as in `rows` to create the column would we be able to do it successfully. e.g. MariaDB [test]> create table test (`rows` int); Query OK, 0 rows affected (0.02 sec) I haven't had any other issue but just this specific keyword and we have not successfully seen any documentation regarding this. Thank you everyone in advance. -- Rod

3 2

Re: [Maria-discuss] Deadlocks in R/W phase of Sysbench
by J. Cassidy 10 Jun '17

10 Jun '17

All, as discussed yesterday, here is my setup and configuration. ************************************************************* 16 VCPU 64GB Memory, DB size 12 GB (In RAM), MariaDB 10.1.24* Single Image. No clustering or outside network interaction * SuSE SLES 12 SP2 using a 4.4.49-92 kernel * ************************************************************* ### Sysbench R/W - 64 Threads sysbench 0.5: multi-threaded system evaluation benchmark Running the test with following options: Number of threads: 64 Report intermediate results every 2 second(s) Initializing random number generator from seed (42). Threads started! [ 2s] threads: 64, tps: 51141.62, reads: 717023.15, writes: 204757.48, response time: 4.72ms (99%), errors: 54.00, reconnects: 0.00 [ 4s] threads: 64, tps: 47938.19, reads: 671195.72, writes: 191759.28, response time: 4.65ms (99%), errors: 5.00, reconnects: 0.00 [ 6s] threads: 64, tps: 46908.41, reads: 656790.25, writes: 187640.64, response time: 4.65ms (99%), errors: 2.50, reconnects: 0.00 [ 8s] threads: 64, tps: 45940.12, reads: 643191.64, writes: 183781.47, response time: 4.44ms (99%), errors: 3.00, reconnects: 0.00 [ 10s] threads: 64, tps: 45789.91, reads: 641083.20, writes: 183161.13, response time: 4.77ms (99%), errors: 2.00, reconnects: 0.00 [ 12s] threads: 64, tps: 45408.37, reads: 635825.16, writes: 181672.97, response time: 4.80ms (99%), errors: 1.50, reconnects: 0.00 [ 14s] threads: 64, tps: 44319.93, reads: 620440.07, writes: 177262.74, response time: 4.50ms (99%), errors: 0.50, reconnects: 0.00 [ 16s] threads: 64, tps: 44634.78, reads: 624843.97, writes: 178523.13, response time: 4.71ms (99%), errors: 0.50, reconnects: 0.00 . . . [ 572s] threads: 64, tps: 24980.71, reads: 349707.39, writes: 99924.32, response time: 5.92ms (99%), errors: 0.00, reconnects: 0.00 [ 574s] threads: 64, tps: 25337.03, reads: 354796.98, writes: 101355.13, response time: 6.19ms (99%), errors: 0.00, reconnects: 0.00 [ 576s] threads: 64, tps: 25196.31, reads: 352683.33, writes: 100777.24, response time: 6.49ms (99%), errors: 0.00, reconnects: 0.00 [ 578s] threads: 64, tps: 25235.61, reads: 353317.05, writes: 100941.94, response time: 5.94ms (99%), errors: 0.00, reconnects: 0.00 [ 580s] threads: 64, tps: 25241.11, reads: 353395.59, writes: 100956.96, response time: 6.09ms (99%), errors: 0.00, reconnects: 0.00 [ 582s] threads: 64, tps: 25146.18, reads: 352056.04, writes: 100599.73, response time: 5.96ms (99%), errors: 0.00, reconnects: 0.00 [ 584s] threads: 64, tps: 25242.59, reads: 353362.72, writes: 100978.85, response time: 6.21ms (99%), errors: 0.00, reconnects: 0.00 [ 586s] threads: 64, tps: 25297.02, reads: 354187.80, writes: 101166.58, response time: 5.89ms (99%), errors: 0.00, reconnects: 0.00 [ 588s] threads: 64, tps: 25070.60, reads: 350944.86, writes: 100283.39, response time: 6.33ms (99%), errors: 0.00, reconnects: 0.00 [ 590s] threads: 64, tps: 25115.20, reads: 351666.84, writes: 100466.81, response time: 6.21ms (99%), errors: 0.00, reconnects: 0.00 [ 592s] threads: 64, tps: 25165.11, reads: 352314.52, writes: 100668.94, response time: 5.98ms (99%), errors: 0.00, reconnects: 0.00 [ 594s] threads: 64, tps: 25165.99, reads: 352322.89, writes: 100703.97, response time: 6.30ms (99%), errors: 0.00, reconnects: 0.00 [ 596s] threads: 64, tps: 24854.73, reads: 347945.66, writes: 99370.90, response time: 6.17ms (99%), errors: 0.00, reconnects: 0.00 [ 598s] threads: 64, tps: 24888.16, reads: 348463.80, writes: 99556.16, response time: 6.21ms (99%), errors: 0.00, reconnects: 0.00 [ 600s] threads: 64, tps: 25158.22, reads: 352195.58, writes: 100633.38, response time: 5.94ms (99%), errors: 0.00, reconnects: 0.00 OLTP test statistics: queries performed: read: 256244548 write: 73212536 other: 36606172 total: 366063256 transactions: 18302990 (30454.11 per sec.) read/write requests: 329457084 (548179.44 per sec.) other operations: 36606172 (60908.54 per sec.) ignored errors: 192 (0.32 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 601.0023s total number of events: 18302990 total time taken by event execution: 38450.5507s response time: min: 0.42ms avg: 2.10ms max: 62.26ms approx. 99 percentile: 5.62ms Threads fairness: events (avg/stddev): 285984.2188/3788.79 execution time (avg/stddev): 600.7899/0.00 ================================================================================================================= ### Excerpt from MariaDB Error Log (Thousands of similiar messages). . . . 2017-06-08 8:10:44 4395980287248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4353081699600 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4353087458576 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4360227998992 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4353073515792 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4390705949968 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4360227392784 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4353087458576 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4353073515792 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction 2017-06-08 8:10:44 4353087458576 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction . . . =================================================================================================================== The configuration below has been tried and tested and works across on different architectures e.g. S390X and S390X. [mysqld_safe] user=root password='' [mysqld] symbolic-links=0 open_files_limit = 65535 # was 102400 max_allowed_packet = 16M # was 768M max-connect-errors = 1000000 connect_timeout = 120 # was 60 performance-schema = false net_read_timeout = 720 log-warnings=2 #####files and sockets # innodb_log_group_home_dir= /data-lun22/logs pid-file=/tmp/mysqld.pid.sysbench port = 3306 # log-error=/var/log/mariadb/mariadb-error-john.log log-error=/var/log/mariadb/mariadb-error-john.log general_log_file=/var/log/mariadb/mariadb-john.log long_query_time = 0 slow_query_log = 0 # slow_query_log_file = /var/log/mariadb/mariadb-slowquery.log # general-log # general_log_file=/var/log/mariadb/mariadb-general.log ##### MariaDB temporary tables # tmpdir in RAM tmpdir = /mnt/tmpdir #####non innodb options (fixed) max_connections = 4000 back_log = 150 table_open_cache = 8000 # was 2048 # was 4000 # was 8000 key_buffer_size = 16M query_cache_type = 0 #was 1 # was 0 join_buffer_size = 32K sort_buffer_size = 32K autocommit = 0 thread-cache-size = 50 table-definition-cache = 1024 table-open-cache = 2048 ####fixed innodb options innodb_file_per_table = true innodb_open_files = 4096 # was 8192 # was 4096 innodb_data_file_path = ibdata1:250M:autoextend innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DIRECT_NO_FSYNC innodb_log_buffer_size = 256M innodb_log_file_size = 4G # was 14G # was 4G innodb_log_files_in_group = 2 innodb_buffer_pool_size = 36G #was 8G # was 48G innodb_buffer_pool_instances = 8 # 16 # was 6 # was 32 innodb_adaptive_hash_index_partitions = 32 innodb_thread_concurrency = 0 ####tuning for RAM disk innodb_adaptive_flushing = 1 innodb_flush_neighbors = 0 innodb_io_capacity = 8000 # was 20000 innodb_io_capacity_max = 40000 innodb_lru_scan_depth = 4096 innodb_purge_threads = 2 innodb_read_io_threads = 2 innodb_write_io_threads = 2 <*> Note NMON reports 35% memory usage in the middle of the abovementioned Banchmark ergo the DB is in cache. No paging. ++ Note The R/W TPS rate are "respectable" based on observations from countless other runs ran on other configurations/architecture. The TPS rates would obviously improve if the deadlock situation outlined above was resolved. So there you have it. Any tips / pointers that would enlighten me are much appreciated. Regards, JC Privet Sergey, do not think I have a problem with my config(s). I am not on the machine at the moment. >From memory, with 16 Cores / 32 VCPU, 64 GB memory, buffer pools, logs etc. tailored to this configuration, the TPS rate is 64 threads - R/O 73K R/W 26K 128 threads - R/O 71K R/W 23K. I am putting the DB in RAM of course to obviate I/O issues. I am interested in seeing what is happening with the CPU caches and nest.. NMON tells me that for the R/O runs I have approximately 85% User, 12-14% System and the rest Idle - this stays consistent throughout the run (300 seconds R/O, 600 seconds R/W) which is reasonable. On the R/W runs, NMONs CPU usage display shows that some CPUs are barely firing, or only intermittently and the granularity I had with R/O is gone. This would seem to tie in with what I see in the MariaDB log - headwinds, violent storms and deadlocks. Any further information you require, please let me know. Regards, JC Hi! I just tried this on x86: 40 threads against single table having 10k rows. No deadlocks, "tps: 12372.40, reads: 173219.52, writes: 49490.51". This is with latest snapshot of 10.1 and sysbench 1.0. I believe you shouldn't see deadlocks on such a big data set. Probably something is wrong with your configs? Regards, Sergey On Thu, Jun 08, 2017 at 04:51:31PM +0200, J. Cassidy wrote: > > > Hello Mark, > > appreciate the reply. > > The OLTP table size and > OLTP size give me a DB size of appx 12GB. This is what I want. I have in the > meantime, looked at some older logs and see that whatever amount of threads I > specify (8, 16,32, 64 or 128), the deadlock messages are still surfacing in the > R/W phase > of Sysbench. I even dropped in two different MariaDB release levels > (10.0.19, 10.1.24) to see whether it would make a difference, deadlock still > there. I am using Sysbench 0.5 for these tests. > I am currently using MariaDB > 10.1.24 - built directly on the machine. S390x by the way, but the problem is > also > occuring on an X86-64 box. > > Regards, > > > JC > > > > I run sysbench frequently with MySQL > (not MariaDB yet) and don't recall ever seeing this error. But I use much > larger values for --oltp-table-size. You used 85937 and I use 1M or larger. > Maybe > there is too much data contention with smaller tables, even if a large number of > tables is used (128 in your case). I use a smaller number of tables - between 4 > and 20. On Thu, Jun 8, 2017 at 12:48 AM, J. Cassidy sean(a)jdcassidy.eu> wrote: > Hello all, > > > have used Sysbench extensively to test MariaDB CPU load factors between various > architectures. > > I am noticing massive amounts of "[ERROR] mysqld: > Deadlock found when trying to get lock; try restarting transaction" in the > MariaDB error log during the R/W phase. The Sysbench R/W TPS rates are still > respectable for my purposes, but how do I > correct this condition?? Can I > ignore this / must live with it? > I have tried three different MariaDB > releases (10.0.19, 10.1.12, 10.1.24) to narrow things down, but this message (x > 1000's) is happening across all releases in the Sysbench R/W phase. > > Here is the Sysbench command that drives the workload against MariaDB - > > sysbench --test=lua/oltp.lua --oltp_tables_count=128 --oltp-table-size=85937 > --rand-seed=42 --rand-type=uniform --num-threads=128 --oltp-read-only=off > --report-interval=2 --mysql-socket=/var/lib/mysql/mysql.sock --max-time=201 > --max-requests=0 --mysql-user=root --percentile=99 run > > Would anyone > have a tip / idea /pointer? > > > Regards, > > > JC > > > John Cassidy > > Obere Bühlstrasse 21 > 8700 Küsnacht > (ZH) > Switzerland / Suisse / Schweiz > > > Mobile: +49 152 58961601 (Germany) > Mobile: +352 621 577 149 (Luxembourg) > Mobile: +41 78 769 17 97 (CH) > Landline: +41 44 509 1957 > > http://www.jdcassidy.eu > > "Aut viam inveniam aut > faciam" - Hannibal. > _______________________________________________ > 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 > --Mark Callaghan > mdcallag(a)gmail.com > > John Cassidy > > Obere Bühlstrasse 21 > 8700 > Küsnacht (ZH) > Switzerland / Suisse / Schweiz > > > Mobile: > +49 152 58961601 (Germany) > Mobile: +352 621 577 149 (Luxembourg) > Mobile: > +41 78 769 17 97 (CH) > Landline: +41 44 509 1957 > > http://www.jdcassidy.eu > > "Aut viam inveniam aut faciam" - > Hannibal. > _______________________________________________ > 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 John Cassidy Obere Bühlstrasse 21 8700 Küsnacht (ZH) Switzerland / Suisse / Schweiz Mobile: +49 152 58961601 (Germany) Mobile: +352 621 577 149 (Luxembourg) Mobile: +41 78 769 17 97 (CH) Landline: +41 44 509 1957 http://www.jdcassidy.eu "Aut viam inveniam aut faciam" - Hannibal. John Cassidy Obere Bühlstrasse 21 8700 Küsnacht (ZH) Switzerland / Suisse / Schweiz Mobile: +49 152 58961601 (Germany) Mobile: +352 621 577 149 (Luxembourg) Mobile: +41 78 769 17 97 (CH) Landline: +41 44 509 1957 http://www.jdcassidy.eu "Aut viam inveniam aut faciam" - Hannibal.

4 11

[Maria-discuss] logging original SQL statement along with ROW events
by Justin Swanhart 09 Jun '17

09 Jun '17

Hi, I seem to recall reading that MariaDB can annotate the binary log with the original SQL statement for a given set of ROW changes in the binary log, but I can't seem to find documentation on this on the wiki. Can MariaDB log the original STATEMENT along with the ROW changeset? If so, can you point me to the relevant documentation, or better yet the patch itself that makes this possible? Thanks, --Justin

3 3

[Maria-discuss] Deadlocks in R/W phase of Sysbench
by J. Cassidy 08 Jun '17

08 Jun '17

Hello all, have used Sysbench extensively to test MariaDB CPU load factors between various architectures. I am noticing massive amounts of "[ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction" in the MariaDB error log during the R/W phase. The Sysbench R/W TPS rates are still respectable for my purposes, but how do I correct this condition?? Can I ignore this / must live with it? I have tried three different MariaDB releases (10.0.19, 10.1.12, 10.1.24) to narrow things down, but this message (x 1000's) is happening across all releases in the Sysbench R/W phase. Here is the Sysbench command that drives the workload against MariaDB - sysbench --test=lua/oltp.lua --oltp_tables_count=128 --oltp-table-size=85937 --rand-seed=42 --rand-type=uniform --num-threads=128 --oltp-read-only=off --report-interval=2 --mysql-socket=/var/lib/mysql/mysql.sock --max-time=201 --max-requests=0 --mysql-user=root --percentile=99 run Would anyone have a tip / idea /pointer? Regards, JC John Cassidy Obere Bühlstrasse 21 8700 Küsnacht (ZH) Switzerland / Suisse / Schweiz Mobile: +49 152 58961601 (Germany) Mobile: +352 621 577 149 (Luxembourg) Mobile: +41 78 769 17 97 (CH) Landline: +41 44 509 1957 http://www.jdcassidy.eu "Aut viam inveniam aut faciam" - Hannibal.

3 6

[Maria-discuss] libmariadb.so.3 compatibility
by Michal Schorm 08 Jun '17

08 Jun '17

Hello, I'm currently quite confused about the *libmariadb* library. In MariaDB 10.1.24 there are: " libmysqlclient_r.so -> libmysqlclient.so " " libmysqlclient.so -> libmysqlclient.so.18 " " libmysqlclient.so.18 -> libmysqlclient.so.18.0.0 " " libmysqlclient.so.18.0.0 " In MariaDB 10.2.6 there are: " libmariadb.so -> libmariadb.so.3 " In MariaDB-connector-c v2.3.3 there are: " libmysqlclient.so -> libmariadb.so " " libmysqlclient_r.so -> libmariadb.so " " libmariadb.so -> libmariadb.so.2 " " libmariadb.so.2 " -- 1) is "libmariadb.so.2" compatibile with "libmysqlclient.so.18.0.0"? Both API and ABI? 2) is "libmariadb.so.3" compatibile with "libmysqlclient.so.18.0.0"? Both API and ABI? 3) is "libmariadb.so.2" compatibile with "libmariadb.so.3"? Both API and ABI? Many packages in Fedora depends on "libmysqlclient.so". I would like to pack 10.2 to Fedora, but I can't before all those packages move to the libmariadb library. It would be considerably easier transfer for me, if all those libraries were compatibile, so I could provide symlinks (simmilar as in the connector C), and provide time for all those packages in Fedora to move safely. -- Michal Schorm Associate Software Engineer Core Services - Databases Team Red Hat

2 2

[Maria-discuss] MariaDB Galera Cluster 10.0.31 and Connector/Java 2.0.2 now available
by Daniel Bartholomew 07 Jun '17

07 Jun '17

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 10.0.31 and MariaDB Connector/J 2.0.2 and 1.6.1. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB Galera Cluster 10.0.31 - Release Notes: https://mariadb.com/kb/en/mgc-10031-rn/ - Changelog: https://mariadb.com/kb/en/mgc-10031-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.31 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/J 2.0.2 - Release Notes: https://mariadb.com/kb/en/mcj-202-rn/ - Changelog: https://mariadb.com/kb/en/mcj-202-cl/ - Downloads: https://downloads.mariadb.org/connector-java/2.0.2/ About MariaDB Connector/ODBC: - https://mariadb.com/kb/en/about-mariadb-connector-j/ MariaDB Connector/J 1.6.1 - Release Notes: https://mariadb.com/kb/en/mcj-161-rn/ - Changelog: https://mariadb.com/kb/en/mcj-161-cl/ - Downloads: https://downloads.mariadb.org/connector-java/1.6.1/ About MariaDB Connector/ODBC: - https://mariadb.com/kb/en/about-mariadb-connector-j/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - 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://mariadb.org/jira - - 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 - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Time Zone help
by Karthick Subramanian 07 Jun '17

07 Jun '17

All, I am facing some strange issue, I believe its due to my ignorant, would appreciate if you can help me out on this: DB Server system OS CentOS. I have loaded the timezone tables in mysql using: mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql After loading, I have restrated the DB using systemctl restart mariadb: Then I have tried below in DB: select @@global.time_zone,@@system_time_zone; [image: Inline image 1] SELECT CONVERT_TZ( NOW(), @@global.time_zone , 'UTC' ), UTC_TIMESTAMP; [image: Inline image 3] SELECT CONVERT_TZ( NOW(), @@system_time_zone , 'UTC' ), UTC_TIMESTAMP; [image: Inline image 4] SELECT CONVERT_TZ( NOW(), 'EDT' , 'UTC' ), UTC_TIMESTAMP; [image: Inline image 2] For some reason, If I use named TZ in CONVERT_TZ function for FROM_TZ, its always showing NULL. Can anyone help me out what else i can do so I can pass the abbreviation or named TZ in FROM_TZ. Regards, Karthick

2 2

[Maria-discuss] Failure upon startup due to changes in /var/lib/mysql/databasename/
by Timothy D. Legg 07 Jun '17

07 Jun '17

Hello, Thanks for the prior suggestions, they ended well. I found a behavior that I found a slight bit confounding. While I tested the server, one of the wikis I host was modified by a friend of mine. When I broke MariaDB, it was no longer feasible to start it, (to the degree that it could have taken days of tinkering), With MariaDB verified to be not running, I tarred the directory /var/lib/mysql/mywiki/ into a file mywiki_with_new_data.tar. I reinstalled MariaDB thoroughly to force the creation of a new /var/lib/mysql/ and /etc/mysql/ . I felt it was safe to recover the databases from the backup SQL file I had created on the currently running machine. Everything now works great, but the mywiki database doesn't reflect the changes anymore. So I stop the mysql process and then for the sake of recoverability, I tar up /var/lib/mysql/mywiki into a file called mywiki_without_new_data.tar. I then rm -rf /var/lib/mysql/mywiki and then untar the mywiki_with_new_data.tar in it's place. MariaDB will no longer start. If I again rm -rf /var/lib/mysql/mywiki and then untar mywiki_without_new_data.tar into the location, MariaDB starts without error. This isn't a code blue situation, my friend can recreate the change he made and that is the easiest solution, but others reading this might not have that luxury. I am also quite curious about what went wrong and how to repair the problem. I didn't think this was possible to fail. There is an interesting except from the errors described below. I'm not certain what exactly this means, or how to correct it. Given that MariaDB could have failed uncleanly when the mysql database was imported, recovery may be infeasible. (the wiki connected to MariaDB as root, it's bad, I know) <excerpt /var/lib/mysql/altdorf.err> InnoDB: Error: tablespace id is 235 in the data dictionary InnoDB: but in file ./mywiki/objectcache.ibd it is 254! 2017-06-07 11:45:08 5c7ff420 InnoDB: Assertion failure in thread 1551889440 in file fil0fil.cc line 638 InnoDB: We intentionally generate a memory trap. </excerpt> # service mysql start Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details. # systemctl -l status mysql.service * mysql.service - LSB: Start and stop the mysql database server daemon Loaded: loaded (/etc/init.d/mysql) Active: failed (Result: exit-code) since Wed 2017-06-07 11:45:40 CEST; 1min 16s ago Process: 1692 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS) Process: 1753 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE) Jun 07 11:45:08 altdorf mysql[1753]: /etc/init.d/mysql: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz ... (warning). Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: [61B blob data] Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")' Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: Jun 07 11:45:40 altdorf mysql[1753]: Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed! Jun 07 11:45:40 altdorf systemd[1]: mysql.service: control process exited, code=exited status=1 Jun 07 11:45:40 altdorf systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon. Jun 07 11:45:40 altdorf systemd[1]: Unit mysql.service entered failed state. # journalctl -xn -- Logs begin at Wed 2017-05-24 10:06:00 CEST, end at Wed 2017-06-07 11:45:40 CEST. -- Jun 07 11:45:08 altdorf /etc/init.d/mysql[1764]: WARNING: /etc/mysql/my.cnf cannot be read. See Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: 0 processes alive and '/usr/bin/mysqladmin --de Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: [61B blob data] Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: error: 'Can't connect to local MySQL server thr Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: Check that mysqld is running and that the socke Jun 07 11:45:40 altdorf /etc/init.d/mysql[2152]: Jun 07 11:45:40 altdorf mysql[1753]: Starting MariaDB database server: mysqld . . . . . . . . . Jun 07 11:45:40 altdorf systemd[1]: mysql.service: control process exited, code=exited status=1 Jun 07 11:45:40 altdorf systemd[1]: Failed to start LSB: Start and stop the mysql database serve -- Subject: Unit mysql.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mysql.service has failed. -- -- The result is failed. Jun 07 11:45:40 altdorf systemd[1]: Unit mysql.service entered failed state. # cat /var/lib/mysql/aldorf.err (excerpts from file with a database name changed to protect user privacy) 170607 11:45:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 170607 11:45:08 [Note] /usr/sbin/mysqld (mysqld 10.0.30-MariaDB-0+deb8u2) starting as process 1851 ... 170607 11:45:08 [Note] InnoDB: Using mutexes to ref count buffer pool pages 170607 11:45:08 [Note] InnoDB: The InnoDB memory heap is disabled 170607 11:45:08 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 170607 11:45:08 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 170607 11:45:08 [Note] InnoDB: Compressed tables use zlib 1.2.8 170607 11:45:08 [Note] InnoDB: Using Linux native AIO 170607 11:45:08 [Note] InnoDB: Not using CPU crc32 instructions 170607 11:45:08 [Note] InnoDB: Initializing buffer pool, size = 128.0M 170607 11:45:08 [Note] InnoDB: Completed initialization of buffer pool 170607 11:45:08 [Note] InnoDB: Highest supported file format is Barracuda. 170607 11:45:08 [Note] InnoDB: 128 rollback segment(s) are active. 170607 11:45:08 [Note] InnoDB: Waiting for purge to start InnoDB: Error: tablespace id is 235 in the data dictionary InnoDB: but in file ./mywiki/objectcache.ibd it is 254! 2017-06-07 11:45:08 5c7ff420 InnoDB: Assertion failure in thread 1551889440 in file fil0fil.cc line 638 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 170607 11:45:08 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.0.30-MariaDB-0+deb8u2 key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=153 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 465934 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x48000 The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 170607 11:45:08 mysqld_safe mysqld from pid file /var/lib/mysql/altdorf.pid ended

4 3

[Maria-discuss] Error when switching to MariaDB
by Timothy D. Legg 07 Jun '17

07 Jun '17

Hello, First of all, here is what I'm working with: Original machine: MySQL Server 5.7.18-0ubuntu0.16.04.1 Destination machine: MariaDB 10.0.30-MariaDB-0+deb8u2 These two machines have no filesystem or communication with with other. I am moving to MariaDB with about 10 to 15 databases that were created in MySQL and I have had a very odd problem with the destination machine running MariaDB where the applications using these databases were having connection errors with their databases. I looked very carefully at what I had done. I exported the databases from MySQL using: $ mysqldump --all-databases > all.sql and imported the collection on the new machine with $ mysql -u root -p < all.sql When I log in as root, all appears well when I inspect the databases, but all is not well. The applications the use these databases cannot connect. I enter the command line to connect using the SQL user accounts, and guess what, they don't log in with their respective passwords. I can log in on the MySQL server using the same account/password pairs. I think it might be a permissions issue. I log into the MariaDB server as root and flush privileges, just to make sure, and I get a terribly vague error message (with no details dropped off in /var/log/mysql/ either). MariaDB [(none)]> flush privileges; ERROR 1105 (HY000): Unknown error When I reach this point, I perform something akin to these steps: sudo su service stop mysql apt-get purge mariadb-server mariadb-server-10.0 mariabd-comon mariadb-client mariadb-client-10.0 mariadb-client-core-10.0 mariadb-server-core-10.0 rm -rf /etc/mysql rm -rf /var/lib/mysql apt-get install mariadb-server mariadb-client exit and I'm asked for root password, etc and also run mysql_secure_installation with all suggested values. Voila, flush privileges works again on the MariaDB server, at least until I attempt to reinsert the databases. Are these problems somewhat unique? Is there a way to pry additional detail from mariadb, such as launching the server in a debug mode? What scenarios have people seen cause this in the past? Where do I look for detailed symptoms? Timothy D. Legg

2 2

[Maria-discuss] Maxscale: qlafilter
by Atif Ghaffar 06 Jun '17

06 Jun '17

Hi all, I have setup a maxscale instance to proxy to the local mysql server running on a different port. All this is working fine. I have also setup a filter to catch deletes on a single table. I can see the deletes in the filter but only when I restart maxscale service. Is there something that I can set so that the log is flushed immediately to the flle. The filter definition is the following [WaCountriesDomainsDeleteFilter] type=filter module=qlafilter options=ignorecase,extended filebase=/tmp/maxscale.wa_countries_domains.delete match=DELETE.*wa_countries_domains.* log_type=unified append=true kind regards -- Atif Ghaffar

2 2

[Maria-discuss] MyRocks:recommended configuration for DB of several TB ?
by Julien Muchembled 01 Jun '17

01 Jun '17

Hello, We have started to evaluate MyRocks 3 months ago, our DBs were initially empty and now they have reached 500 GB on-disk. We experience severe performance issues, and we have the feelings it could be better. https://github.com/facebook/rocksdb/wiki/RocksDB-Tuning-Guide is interesting, especially the "Universal Compaction" section: « Universal compaction has a size limitation. Please be careful when your DB (or column family) size is over 100GB. » I don't think that write amplification is a bottleneck for our application, so my obvious first question is: What compaction style is used in MariaDB and how to make sure that Level Style Compaction is used ? Also, we haven't set any 'rocksdb_*' option. The default configuration may not be appropriate in our case. For example, rocksdb_block_cache_size (default: 512MB) seems to be one of the most important options, similarly to innodb_buffer_pool_size and tokudb_cache_size, although I have never understood why (see my unanswered question at https://lists.launchpad.net/maria-discuss/msg02683.html ). Although the DB is much bigger than RAM (128 GB), RAM should be big enough to contain the active working set. Julien

2 1

[Maria-discuss] MariaDB 10.1.24 and Connector/C 2.3.3 now available
by Daniel Bartholomew 31 May '17

31 May '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.24 and MariaDB Connector/C 2.3.3. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.24 - Release Notes: https://mariadb.com/kb/en/mdb-10124-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10124-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.24 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/C 2.3.3 - Release Notes: https://mariadb.com/kb/en/mcc-233-rn/ - Changelog: https://mariadb.com/kb/en/mcc-233-cl/ - Downloads: https://downloads.mariadb.org/connector-c/2.3.3/ About MariaDB Connector/ODBC: - https://mariadb.com/kb/en/about-mariadb-connector-c/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - 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://mariadb.org/jira - - 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 - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Ubuntu 16.04, Accidentally installed mariadb-server on top of mysql-server
by rich.greder＠hushmail.com 29 May '17

29 May '17

Hello, Guys, I did a bad one. I only had one server remaining that still had mysql installed and thinking I was logged into my laptop's console, I executed apt-get install mariadb-server. I wasn't on my laptop. I was logged into a virtual hosting server and knocked eight sites offline including my wiki of all my HOWTO documents ironically, describing how to install mariadb-server on various platforms. I didn't notice anything was amiss until I saw a comment that it was uninstalling mysql (which I knew wasn't on my laptop) I was able to log in using my old root password, but all my databases were gone. Is there any hope for recovering the databases as they were earlier today? Rich

2 3

[Maria-discuss] thank you for getting MyRocks into MariaDB 10.2
by MARK CALLAGHAN 26 May '17

26 May '17

I look forward to trying it out. -- Mark Callaghan mdcallag(a)gmail.com

5 8

[Maria-discuss] MariaDB 10.2.6 Delay slave question?
by Ljr Yang 24 May '17

24 May '17

HI, Today, we upgrade a group MariaDB 10.1.22 to MariaDB 10.2.6, after upgade, start delay slave : change master to master_delay=86400 start slave and execute show all slaves status , Seconds_Behind_Master continue grow and Exec_Master_Log_Pos not change, please help confirm what cause lead this ? thanks. Slave_IO_Running: Yes Slave_SQL_Running: Yes * Exec_Master_Log_Pos: 367* Seconds_Behind_Master: 116072 Gtid_IO_Pos: 0-227-72846307321 Parallel_Mode: conservative SQL_Delay: 86400 SQL_Remaining_Delay: 83164 Slave_SQL_Running_State: Waiting until MASTER_DELAY seconds after master executed event after 5 minutes, Slave_IO_Running: Yes Slave_SQL_Running: Yes * Exec_Master_Log_Pos: 367* Seconds_Behind_Master: 116550 Gtid_IO_Pos: 0-227-72846546131 Parallel_Mode: conservative SQL_Delay: 86400 SQL_Remaining_Delay: 82686 Slave_SQL_Running_State: Waiting until MASTER_DELAY seconds after master executed event

1 0

[Maria-discuss] MariaDB 10.2.6 Stable (GA) now available
by Daniel Bartholomew 23 May '17

23 May '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.6 Stable (GA). This is the first stable release in the MariaDB 10.2 series. MariaDB 10.0.31 and MariaDB Connector/ODBC 2.0.15 have also been released. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.2.6 - Release Notes: https://mariadb.com/kb/en/mdb-1026-rn/ - Changelog: https://mariadb.com/kb/en/mdb-1026-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.2.6 About MariaDB 10.2: - https://mariadb.com/kb/en/what-is-mariadb-102/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB 10.0.31 - Release Notes: https://mariadb.com/kb/en/mdb-10031-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10031-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.0.31 About MariaDB 10.0: - https://mariadb.com/kb/en/what-is-mariadb-100/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Connector/ODBC 2.0.15 - Release Notes: https://mariadb.com/kb/en/mco-2015-rn/ - Changelog: https://mariadb.com/kb/en/mco-2015-cl/ - Downloads: https://downloads.mariadb.org/connector-odbc/2.0.15/ About MariaDB Connector/ODBC: - https://mariadb.com/kb/en/about-mariadb-connector-odbc/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - 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://mariadb.org/jira - - 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 - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] Connector Net Question
by ksubramanian＠paycommerce.com 17 May '17

17 May '17

All, We have set auto-commit=false at server level. But our .Net developers want to enable this auto-commit as true (default behaviour) that I hesitant to do that. Is there any connector (driver) properties that we can set at connection level for auto-commit. I know in JDBC driver, we have the properties that we can set at driver level when we establish connection to DB. But for connector/Net I am trying to find, couldn’t locate one. I noticed auto-enlist sett to true or false, not sure whether this will mimic the auto-commit functionality in a given connection. Can anyone using .Net and MariaDB combination help me to share your thought on this. Regards, Karthick Sent from Mail for Windows 10

2 3

Re: [Maria-discuss] Connector Net Question
by Federico Razzoli 17 May '17

17 May '17

Note that the auto commit was always enabled by default in MySQL. So, changing this default would probably break most existing applications. Running a multi-statement transaction in autocommit is possible by using START TRANSACTION explicitly. Applications can do this and just don't care about autocommit value, if they want. Cheers, Federico -------------------------------------------- Mer 17/5/17, <ksubramanian(a)paycommerce.com> ha scritto: Oggetto: Re: [Maria-discuss] Connector Net Question A: "Vladislav Vaintroub" <vvaintroub(a)gmail.com>, "Maria Discuss" <maria-discuss(a)lists.launchpad.net> Data: Mercoledì 17 maggio 2017, 16:36 #yiv0052539947 #yiv0052539947 -- _filtered #yiv0052539947 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv0052539947 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} #yiv0052539947 #yiv0052539947 p.yiv0052539947MsoNormal, #yiv0052539947 li.yiv0052539947MsoNormal, #yiv0052539947 div.yiv0052539947MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;color:windowtext;} #yiv0052539947 a:link, #yiv0052539947 span.yiv0052539947MsoHyperlink {color:blue;text-decoration:underline;} #yiv0052539947 a:visited, #yiv0052539947 span.yiv0052539947MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;} #yiv0052539947 pre {margin:0cm;margin-bottom:.0001pt;font-size:10.0pt;color:black;} #yiv0052539947 span.yiv0052539947HTMLPreformattedChar {color:black;} #yiv0052539947 .yiv0052539947MsoChpDefault {} _filtered #yiv0052539947 {margin:72.0pt 72.0pt 72.0pt 72.0pt;} #yiv0052539947 div.yiv0052539947WordSection1 {} #yiv0052539947 The reason for disable the auto-commit is to mimic more or less similar to oracle behaviour. Because our existing system was in oracle. Just asking out of curiosity – why we enable auto-commit by default in Maria DB. I felt that it wont give control on how we maintain the transaction. Can anyone provide some reasons for why we need to keep the auto-commit enabled at server level. Sent from Mail for Windows 10 From: Vladislav Vaintroub Sent: 17 May 2017 18:08 To: ksubramanian(a)paycommerce.com; Maria Discuss Subject: Re: [Maria-discuss] Connector Net Question On 17.05.2017 11:26, ksubramanian(a)paycommerce.com wrote:All, We have set auto-commit=false at server level. But our .Net developers want to enable this auto-commit as true (default behaviour) that I hesitant to do that. Is there any connector (driver) properties that we can set at connection level for auto-commit. I know in JDBC driver, we have the properties that we can set at driver level when we establish connection to DB. But for connector/Net I am trying to find, couldn’t locate one. I noticed auto-enlist sett to true or false, not sure whether this will mimic the auto-commit functionality in a given connection. Can anyone using .Net and MariaDB combination help me to share your thought on this. Out of curiosity, what is the reason for you to use the non-default behavior (global auto-commit=false)? As far as I know, you cannot set arbitrary session variable automatically with C/NET, and there is no property for autocommit. Thus this would need to be done in code, just after connecting, e.g command.executeNonQuery("set @@autocommit=1") Regards,Karthick Sent from Mail for Windows 10 _______________________________________________Mailing list: https://launchpad.net/~maria-discussPost to : maria-discuss(a)lists.launchpad.netUnsubscribe : https://launchpad.net/~maria-discussMore help : https://help.launchpad.net/ListHelp _______________________________________________ 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] Cross compile error
by Lucian Cristian 16 May '17

16 May '17

Hi I'm trying to cross compile (any 10.* versions) using musl and uClibc++ for a LEDE/Openwrt system and I have problems with these errors: staging_dir/target-x86_64_musl/usr/include/uClibc++/associative_base:444:8: error: 'void std::__base_associative<Key, ValueType, Compare, Allocator>::swap(std::__base_associative<Key, ValueType, Compare, Allocator>&) [with Key = dict_foreign_t*; ValueType = dict_foreign_t*; Compare = dict_foreign_compare; Allocator = ut_allocator<dict_foreign_t*>]' is protected void __base_associative<Key, ValueType, Compare, Allocator>::swap(__base_associative<Key, ValueType, Compare, Allocator>& m) ^ build_dir/target-x86_64_musl/mariadb-10.2.4/storage/innobase/dict/dict0dict.cc:1996:32: error: within this context table->foreign_set.swap(fk_set); ^ storage/innobase/CMakeFiles/innobase.dir/build.make:542: recipe for target 'storage/innobase/CMakeFiles/innobase.dir/dict/dict0dict.cc.o' failed staging_dir/target-x86_64_musl/usr/include/uClibc++/map: In instantiation of 'std::map<Key, T, Compare, Allocator>::reference std::map<Key, T, Compare, Allocator>::operator[](const key_type&) [with Key = const char*; T = dict_index_t*; Compare = ut_strcmp_functor; Allocator = ut_allocator<std::pair<const char*, dict_index_t*> >; std::map<Key, T, Compare, Allocator>::reference = std::pair<const char*, dict_index_t*>&; std::map<Key, T, Compare, Allocator>::key_type = const char*]': build_dir/target-x86_64_musl/mariadb-10.2.4/storage/innobase/dict/dict0stats.cc:2518:22: required from here staging_dir/target-x86_64_musl/usr/include/uClibc++/map:143:13: error: invalid initialization of reference of type 'std::map<const char*, dict_index_t*, ut_strcmp_functor, ut_allocator<std::pair<const char*, dict_index_t*> > >::reference {aka std::pair<const char*, dict_index_t*>&}' from expression of type 'dict_index_t*' return i->second; ^ storage/innobase/CMakeFiles/innobase.dir/build.make:614: recipe for target 'storage/innobase/CMakeFiles/innobase.dir/dict/dict0stats.cc.o' failed build_dir/target-x86_64_musl/mariadb-10.2.4/plugin/handler_socket/handlersocket/hstcpsvr.cpp: In constructor 'dena::hstcpsvr::hstcpsvr(const dena::config&)': build_dir/target-x86_64_musl/mariadb-10.2.4/plugin/handler_socket/handlersocket/hstcpsvr.cpp:92:37: error: invalid initialization of non-const reference of type 'std::auto_ptr<volatile dena::database_i>&' from an rvalue of type 'dena::database_ptr {aka std::auto_ptr<volatile dena::database_i>}' cshared.dbptr = database_i::create(c); ^ In file included from staging_dir/target-x86_64_musl/usr/include/uClibc++/vector:22:0, from build_dir/target-x86_64_musl/mariadb-10.2.4/plugin/handler_socket/handlersocket/hstcpsvr.cpp:12: staging_dir/target-x86_64_musl/usr/include/uClibc++/memory:137:12: note: initializing argument 1 of 'std::auto_ptr<T>& std::auto_ptr<T>::operator=(std::auto_ptr<T>&) [with T = volatile dena::database_i]' auto_ptr& operator=(auto_ptr& p) throw(){ ^ plugin/handler_socket/CMakeFiles/handlersocket.dir/build.make:134: recipe for target 'plugin/handler_socket/CMakeFiles/handlersocket.dir/handlersocket/hstcpsvr.cpp.o' failed make[5]: *** [plugin/handler_socket/CMakeFiles/handlersocket.dir/handlersocket/hstcpsvr.cpp.o] Error 1 this is the command line (cd /build_dir/target-x86_64_musl/mariadb-10.2.4; CFLAGS="-Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -iremap/build_dir/target-x86_64_musl/mariadb-10.2.4:mariadb-10.2.4 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -fpic " CXXFLAGS="-Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -iremap/build_dir/target-x86_64_musl/mariadb-10.2.4:mariadb-10.2.4 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -fpic " LDFLAGS="-L/staging_dir/target-x86_64_musl/usr/lib -L/staging_dir/target-x86_64_musl/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro " cmake -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_VERSION=1 -DCMAKE_SYSTEM_PROCESSOR=x86_64 -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG" -DCMAKE_C_COMPILER="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc" -DCMAKE_C_COMPILER_ARG1="" -DCMAKE_CXX_COMPILER="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/g++-uc" -DCMAKE_CXX_COMPILER_ARG1="" -DCMAKE_ASM_COMPILER="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc" -DCMAKE_ASM_COMPILER_ARG1="" -DCMAKE_EXE_LINKER_FLAGS:STRING="-L/staging_dir/target-x86_64_musl/usr/lib -L/staging_dir/target-x86_64_musl/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro" -DCMAKE_MODULE_LINKER_FLAGS:STRING="-L/staging_dir/target-x86_64_musl/usr/lib -L/staging_dir/target-x86_64_musl/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro -Wl,-Bsymbolic-functions" -DCMAKE_SHARED_LINKER_FLAGS:STRING="-L/staging_dir/target-x86_64_musl/usr/lib -L/staging_dir/target-x86_64_musl/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib -L/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib -znow -zrelro -Wl,-Bsymbolic-functions" -DCMAKE_AR="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc-ar" -DCMAKE_NM="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc-nm" -DCMAKE_RANLIB="/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/bin/x86_64-openwrt-linux-musl-gcc-ranlib" -DCMAKE_FIND_ROOT_PATH="/staging_dir/target-x86_64_musl/usr;/staging_dir/toolchain-x86_64_gcc-5.4.0_musl" -DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM=BOTH -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=ONLY -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=ONLY -DCMAKE_STRIP=: -DCMAKE_INSTALL_PREFIX=/usr -DDL_LIBRARY=/staging_dir/target-x86_64_musl -DCMAKE_PREFIX_PATH=/staging_dir/target-x86_64_musl -DCMAKE_SKIP_RPATH=TRUE -DCMAKE_SYSTEM_NAME=Linux -DSTACK_DIRECTION=-1 -DWITH_WSREP=ON -DWITH_INNODB_DISALLOW_WRITES=1 -DCONNECT_WITH_JDBC=OFF -DWITHOUT_TOKUDB=1 -DIMPORT_EXECUTABLES=/build_dir/hostpkg/mariadb-10.2.4/host/import_executables.cmake /build_dir/target-x86_64_musl/mariadb-10.2.4 ) can someone give me an advice ? Regards

2 2

[Maria-discuss] AWS Key Management plugin
by Christopher Hendry 10 May '17

10 May '17

Currently configuring MariaDB for at rest encryption using Amazon key management. A few weeks ago, I setup our primary server with no problems (Centos 7). Recently, working on the same hardware/OS for slaves - when I do a yum install MariaDB-aws-key-management I get: "No package MariaDB-aws-key-management available." I did discover that since the first successful install, the RPM versions have changed from 10.1.22 to 10.1.23 (and have included some config options for 10.2 that need to be commented out). I also believe that originally I had to change plugin-maturity in config = alpha - but that makes no difference now. Anyone know what happened to the plugin? I can copy the original one from my primary server and all works fine - but I don't love that approach. Is aws-key-management plugin still supported? Thanks for any insight. C -- "When you do things right, people won't be sure you've done anything at all."

2 1

Re: [Maria-discuss] MySQL Workbench Fork?
by Federico Razzoli 07 May '17

07 May '17

Well, clicking around, selecting things, switching to keyboards, and so on, can hardly be faster than writing an SQL statement - provided that you learn ALTER TABLE syntax. But, apart from that, I think that we mostly agree on everything except one thing: the meaning of enterprise. In an enterprise environment a DBA needs to automate everything and write scripts. Also, as I wrote before and the author of that post also says, GUI's are not reliable, you never know exactly what they do. That said, I suppose that GUIs can be useful for someone, especially for developers and hobbyists. Cheers, Federico -------------------------------------------- Gio 27/4/17, <info(a)smallbusinessconsultingexperts.com> ha scritto: Oggetto: Re: [Maria-discuss] MySQL Workbench Fork? A: maria-discuss(a)lists.launchpad.net, "Federico Razzoli" <federico_raz(a)yahoo.it> Data: Giovedì 27 Aprile 2017, 20:34 Sure, but don't confuse a post with a fact either. That's great he has an opinion that you share, I am sure I can find many more that say the opposite. What I got from his post is there are some things a gui cannot do, which is of course the case. So? The opposite is true also, if you add the word quickly. That does not make a point as universal true or factual. Should we abandon SNMP and other standards type network consoles (gui) since obviously we can do the same thing without them? You don't see the value is the gui network view? So, workbench feature of showing you a refreshing graphical status of your server isn't useful? It's not complete by any means, but it is useful, just like the connections screen showing running queries. Those are just examples which some will desire to pick on. But I think it's a reasonable view. My point is not guis are (always) better, they each have a place. On Apr 27, 2017, 1:23 PM -0500, Federico Razzoli <federico_raz(a)yahoo.it>, wrote: I've just seen this Quora answer, which lists some good reasons to avoid GUIs. There are others. Again: my point is not "GUI's shouldn't exist", it's just "please don't call them an enterprise software, because they are not". https://www.quora.com/Do-database-administrators-actually-think-that-GUIs-a…

8 8

[Maria-discuss] MySQL Workbench Fork?
by Zach Lym 05 May '17

05 May '17

I convinced my boss to use MariaDB for a new project but it appears that the workbench is incompatible with new features of MariaDB. I've looked at the alternatives listed on the website, but they are all either proprietary or Windows only. I just can't sell my boss on switching to MariaDB without workbench. Free software isn't free, but I think Workbench is a big driver of commercial and enterprise use. It's easy to kvetch from the outside, but I feel as though MariaDB has just lost some ground. Has management considered forking Workbench? Thank you, -Zach Lym

9 12

[Maria-discuss] MariaDB 10.1.23 & 5.5.56 now available
by Daniel Bartholomew 03 May '17

03 May '17

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.23, MariaDB 5.5.56 and MariaDB Galera Cluster 5.5.56. All are Stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.23 - Release Notes: https://mariadb.com/kb/en/mdb-10123-rn/ - Changelog: https://mariadb.com/kb/en/mdb-10123-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.23 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 5.5.56 - Release Notes: https://mariadb.com/kb/en/mdb-5556-rn/ - Changelog: https://mariadb.com/kb/en/mdb-5556-cl/ - Downloads: https://downloads.mariadb.org/mariadb/5.5.56 About MariaDB 5.5: - https://mariadb.com/kb/en/what-is-mariadb-56/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ MariaDB Galera Cluster 5.5.56 - Release Notes: https://mariadb.com/kb/en/mgc-5556-rn/ - Changelog: https://mariadb.com/kb/en/mgc-5556-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/5.5.56 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - 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://mariadb.org/jira - - 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 - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] lz4 innodb compression
by Reinis Rozitis 28 Apr '17

28 Apr '17

Hello, is lz4 support not compiled in the Mariadb rpm (Opensuse) packages or are there some runtime requirements or you have to rebuild from source? MariaDB> set global innodb_compression_algorithm=lz4; ERROR 1231 (42000): Variable 'innodb_compression_algorithm' can't be set to the value of 'lz4' while MariaDB> set global innodb_compression_algorithm=lzo; Query OK, 0 rows affected (0.00 sec) Server version: 10.2.5-MariaDB-log MariaDB Server / OpenSUSE Leap 42.2 / on system: lz4-1.4.0+svn124-3.3.x86_64 liblz4-1_4-1.4.0+svn124-3.3.x86_64 rr

3 4

[Maria-discuss] howto debug “Slave SQL: Error executing row event” and “Node consistency compromized, aborting…” and “Failed to apply trx: source”
by Lukas Lehner 28 Apr '17

28 Apr '17

Hi https://dba.stackexchange.com/questions/172230/howto-debug-slave-sql-error-… any idea? Lukas

1 0

[Maria-discuss] M|17 MariaDB Conference 2017 videos
by Lukas Lehner 27 Apr '17

27 Apr '17

Hi where can I watch M|17 video recordings? Is this planned? Will it be free or only for customers? Lukas

2 1