- discuss - lists.mariadb.org

[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