December 2015 - discuss - lists.mariadb.org

[Maria-discuss] why stdout? -> [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096
by Reindl Harald 05 Jul '20

05 Jul '20

Aug 6 12:24:24 testserver mysqld: 150806 12:24:24 [Note] /usr/libexec/mysqld (mysqld 10.0.20-MariaDB) starting as process 115096 ... why is this now stdout instead mysql logs? on systemd based distributions that spits now to the global syslog and finally on machines restarting 2 instances every hour for backup reasons it annoys until 10.0.19 or 10.0.20 that was not this way

5 13

[Maria-discuss] More contributors welcome to MariaDB packaging in Debian
by Otto Kekäläinen 24 Jan '16

24 Jan '16

Hello! Do you want to improve MariaDB in Debian? Do you want to contribute to Debian packaging using modern git-buildpackage tools and state of the art QA tools? Do you want to see the result of your work in the hands of numerous of Linux users who run Debian and MariaDB? I am happy to mentor anybody who want's to start contributing to Debian packaging of MariaDB. I have created some items with priority "wishlist" and title prepended with "TODO" visible at https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mariadb-10.0#_0_6_4 These are all farily easy tasks that anybody interested in contributing could pick up and and start working on. If you want to contribute, please subscribe to the packaging teams list and show your interest there / ask questions to get directions and more help: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/ I promise to quickly review and respond to questions so that contributors feel welcomed! - Otto

3 4

[Maria-discuss] New Question: Upgrading from MariaDB 10.0 to 10.1 under Windows
by AskMonty KB 28 Dec '15

28 Dec '15

Hello, A new question has been asked in "Upgrading MariaDB" by wschwarz. Please answer it at http://mariadb.com/kb/en/upgrading-from-mariadb-100-to-101-under-windows/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- Upgrading from MariaDB 10.0 to 10.1 on a Windows System. Must i do some especial thing with a master slave replication system? Which one must I update first master or slave? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/upgrading-from-mariadb-100-to-101-under-windows/

1 0

[Maria-discuss] MariaDB init.d Script Probable Bug in wait_for_ready()
by Joy Bhattacherjee 27 Dec '15

27 Dec '15

Hi, Context: ----------- Version: MariaDB 10.0 Repo: http://yum.mariadb.org/10.0/centos7-amd64 OS: CentOS Linux release 7.2.1511 Kernel: 3.10.0-229.7.2.el7.x86_64 Cloud Provider: Windows Azure I run a three-node MariaDB-Galera cluster on production for my company. With the custom config file at: */etc/my.cnf.d/server.cnf* My datadisk is mounted over a lvm2 partition over two physical volumes, mounted on the path. */datadrive/galera/mysql* The logical volume only takes up 50% of the volume group as I leave the empty space for snapshot operations. This is reflected in my configuration as: *[mysqld]* *datadir = /datadrive/galera/mysql * *socket = /datadrive/galera/mysql/mysql.sock * Issue: -------- Coming to the issue at hand; When starting the primary component through: *$ sudo service mysql bootstrap* or, *$ sudo service mysqld start --wsrep-new-cluster* ( Essentially same, as bootstrap differs to *start --wsrep_new_cluster *) The bootstrap sequence correctly calls mysqldsafe, as below */usr/bin/mysqld_safe --datadir=/datadrive/galera/mysql --pid-file=/datadrive/galera/mysql/ciq-test-db01.pid --wsrep-new-cluster* However, it then gets stuck in the *wait_for_ready() function of /etc/init.d/mysql* The sequence tries to ping mysqladmin through: * if $bindir/mysqladmin ping >/dev/null 2>&1; then* *log_success_msg* * return 0* *elif kill -0 $! 2>/dev/null ; then* * : # mysqld_safe is still running* *else* * # mysqld_safe is no longer running, abort the wait loop* * break* It gets stuck here as the test: * if $bindir/mysqladmin ping >/dev/null 2>&1; then* Always fails and the counter keeps increasing till 900 and Error's out with the *log_failure_msg* *return 1* Test: I tested that line from the console as: *$mysqladmin ping >dev/null 2>&1* and, was thrown the following error: *mysqladmin: connect to server at 'localhost' failed* *error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "**No such file or directory")'* *Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!* Obviously, '*/var/lib/mysql' *does not exist in my setup, and the socket file was at *'/datadrive/galera/mysql/mysql.sock'* But, my socket can be passed explicitly to *mysqladmin *by doing, *$mysqladmin --socket=**/datadrive/galera/mysql/mysql.sock ping* This actually worked as expected and I got the desired output, *mysqld is alive* Solution: ----------- What I surmised through my novice abilities was that the init script was not passing the variables it read from */etc/my.cnf.d/server.cnf to mysqladmin* So, for now I have done a hackjob by altering the init script function wait_for_ready() with the test: *if $bindir/mysqladmin --socket=/datadrive/galera/mysql/mysql.sock ping >/dev/null 2>&1; then* * log_success_msg* * return 0* And voila, *$ sudo service mysql start* *$ sudo service mysql start --wsrep-new-cluster* *$ sudo service mysql bootstrap* All above works. It is evident that I should be passing all the variables from */etc/my.cnf.d/server.cnf *that *mysqladmin *needs to set it's environement correctly. However I think that this could be / should be done on the pre-distributed init script itself rather than a user-side hack. While I have tried to be thorough in my inspection of the issue, I may have missed either something very basic or inherently complex that's currently is inherent to the process of initializing the mysql service. Please redirect me to a corrected course if that is the case. P.S. First time post in the list, I may have stated things unacceptably P.P.S. Merry Christmas to you all. Thanks and regards, Joy Bhattacherjee Mob: +91-9011235028

3 3

[Maria-discuss] Weighted Quorum for Three Nodes
by Tom Worster 27 Dec '15

27 Dec '15

In the Galera docs <http://galeracluster.com/documentation-webpages/weightedquorum.html#weighte d-quorum-for-three-nodes> I read > When configuring quorum weights for three nodes, use the following pattern: > node1: pc.weight = 2 > node2: pc.weight = 1 > node3: pc.weight = 0 > Under this pattern, killing node2 and node3 simultaneously preserves the > Primary Component > <http://galeracluster.com/documentation-webpages/glossary.html#term-primary-… > mponent> on node1. Killing node1 causes node2 and node3 to become > non-primary components. The wording makes it sound as though this is a general recommendation. But, iiuc, this cluster of 3 nodes has a single point of failure: node1. How is this desirable? Tom

2 1

[Maria-discuss] R: CONNECT storage engine
by Federico Razzoli 24 Dec '15

24 Dec '15

A new version of CONNECT package was released, but you have still 10.1.9. The packages don't conflict, but versions are incompatible. Just run apt-get upgrade and CONNECT will work. Regards Federico -------------------------------------------- Gio 24/12/15, Karol Krasňan <karol(a)krasnan.eu> ha scritto: Oggetto: [Maria-discuss] CONNECT storage engine A: maria-discuss(a)lists.launchpad.net Data: Giovedì 24 dicembre 2015, 14:44 #yiv1836587082 blockquote.yiv1836587082cite {margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px solid #cccccc;} #yiv1836587082 blockquote.yiv1836587082cite2 {margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left:1px solid #cccccc;margin-top:3px;padding-top:0px;} #yiv1836587082 .yiv1836587082plain pre, #yiv1836587082 .yiv1836587082plain tt {font-family:monospace;font-size:100%;font-weight:normal;font-style:normal;white-space:pre-wrap;} #yiv1836587082 a img {border:0px;}#yiv1836587082 body {font-family:Tahoma;font-size:12pt;} #yiv1836587082 .yiv1836587082plain pre, #yiv1836587082 .yiv1836587082plain tt {font-family:Tahoma;font-size:12pt;} Hello all, I have problem with CONNECT storage engine. I am using MariaDB 10.1.9 on Debian Jessie, with actual version mariadb-connect-engine. But when ha_connect.so plugin is loaded, server show error and dont load engine. "Can't open shared library 'ha_connect.so' (errno: 8, API version for STORAGE ENGINE plugin CONNECT not supported by this version of the server)" I am not able find any solution of this problem. Thanks for help and Merry Christmas :) Karol -----Segue allegato----- _______________________________________________ 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] CONNECT storage engine
by Karol Krasňan 24 Dec '15

24 Dec '15

Hello all, I have problem with CONNECT storage engine. I am using MariaDB 10.1.9 on Debian Jessie, with actual version mariadb-connect-engine. But when ha_connect.so plugin is loaded, server show error and dont load engine. "Can't open shared library 'ha_connect.so' (errno: 8, API version for STORAGE ENGINE plugin CONNECT not supported by this version of the server)" I am not able find any solution of this problem. Thanks for help and Merry Christmas :) Karol

1 0

[Maria-discuss] MariaDB 10.1.10 and MariaDB Galera Cluster 10.0.23 & 5.5.47 now available
by Daniel Bartholomew 24 Dec '15

24 Dec '15

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.10, MariaDB Galera Cluster 5.5.47, and MariaDB Galera Cluster 10.0.23. These are all Stable (GA) releases. See the Release Notes and Changelogs for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB 10.1.10 - https://mariadb.com/kb/en/mdb-10110-rn/ - https://mariadb.com/kb/en/mdb-10110-cl/ - Downloads: https://downloads.mariadb.org/mariadb/10.1.10 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 Galera Cluster 5.5.47 - https://mariadb.com/kb/en/mgc-5547-rn/ - https://mariadb.com/kb/en/mgc-5547-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/5.5.47 MariaDB Galera Cluster 10.0.23 - https://mariadb.com/kb/en/mgc-10023-rn/ - https://mariadb.com/kb/en/mgc-10023-cl/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.23 About MariaDB Galera Cluster: https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ - - 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/en/donate/ We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - 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] New Question: Maria db with ssrs reports using Microsoft Report Builder
by AskMonty KB 23 Dec '15

23 Dec '15

Hello, A new question has been asked in "MariaDB FAQ" by abin. Please answer it at http://mariadb.com/kb/en/maria-db-with-ssrs-reports-using-microsoft-report-… as the person asking the question may not be subscribed to the mailing list. -------------------------------- I tried to use maria db with ssrs reports using ODBC in Microsoft sql report builder.I installed Mysql ODBC connector in my machine and was successful in connecting with maria db.But after saving the report and reopening the report in report builder ,its asking user login name and password. How can I remove the credentials, which is asked repeatedly while reopening the report? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/maria-db-with-ssrs-reports-using-microsoft-report-…

1 0

Re: [Maria-discuss] enforce_storage_engine galera cluster
by Federico Razzoli 22 Dec '15

22 Dec '15

I didn't suggest to use MyISAM :) Now I understand your purpose. If you use MaxScale, you can use a filter and replace MyISAM with InnoDB. Something like: /engine( )*=( *)myisam/i And you can use similar regexps for each storage engine. The filter that you need is this one: https://github.com/mariadb-corporation/MaxScale/blob/master/Documentation/F… Hope that this helps. Federico -------------------------------------------- Mar 22/12/15, Michele Tota <michele.tota(a)lnf.infn.it> ha scritto: Oggetto: Re: [Maria-discuss] enforce_storage_engine galera cluster A: maria-discuss(a)lists.launchpad.net Data: Martedì 22 dicembre 2015, 14:29 Thank you all, we're going to open a bug as soon as possible; @Federico: Thanks for the suggestion, but we are interested in forcing engine substitution, because this way a table creation made by a generic user can be issued using both InnoDB and MyISAM (users can't be always aware of which engine is actually reported in a scripted creation) can produce only InnoDB tables that can be actually replicated on other nodes (as you stated previously). Anyway, this bug seems to break our plans, so we should report the bug and find another way in the meanwhile....in addition, MyISAM replication is described as experimental and we don't want to use it in such early development phase. Thank you very much again for the support. On 22/12/2015 13:03, Roberto Spadim wrote: in my opnion, itś a bug, report to jira issue tracker 2015-12-22 10:00 GMT-02:00 Federico Razzoli <federico_raz(a)yahoo.it>: Sounds like a bug. But, bug or not bug, I suggest you set sql_mode = 'NO_ENGINE_SUBSTITUTION'. Changes to non-InnoDB tables are NOT replicated. (There seems to be a sort of support for MyISAM, but it's unreliable and needs to be manually enabled on all nodes) Federico -------------------------------------------- Mar 22/12/15, Michele Tota <michele.tota(a)lnf.infn.it> ha scritto: Oggetto: Re: [Maria-discuss] enforce_storage_engine galera cluster A: maria-discuss(a)lists.launchpad.net Data: Martedì 22 dicembre 2015, 12:22 Thanks guys, as Ian has pointed out, in recent releases sql_mode contains by default NO_ENGINE_SUBSTITUTION so in our deployment we set sql_mode to blank to gracefully use InnoDB when MyISAM table creation is issued. To be clearer on the problem we're experiencing, I'll paste some console output. On the first node we have: MariaDB [galera_test]> SHOW VARIABLES WHERE Variable_name='enforce_storage_engine' OR Variable_name='sql_mode'; +------------------------+--------+ | Variable_name | Value | +------------------------+--------+ | enforce_storage_engine | InnoDB | | sql_mode | | +------------------------+--------+ 2 rows in set (0.00 sec) MariaDB [galera_test]> CREATE TABLE table_1(id INTEGER) ENGINE=InnoDB; Query OK, 0 rows affected (0.01 sec) MariaDB [galera_test]> CREATE TABLE table_2(id INTEGER) ENGINE=MyISAM; Query OK, 0 rows affected, 1 warning (0.00 sec) MariaDB [galera_test]> SHOW WARNINGS; +-------+------+-------------------------------------------------+ | Level | Code | Message | +-------+------+-------------------------------------------------+ | Note | 1266 | Using storage engine InnoDB for table 'table_2' | +-------+------+-------------------------------------------------+ 1 row in set (0.00 sec) MariaDB [galera_test]> SELECT TABLE_NAME, ENGINE FROM information_schema.TABLES where TABLE_SCHEMA = 'galera_test'; +------------+--------+ | TABLE_NAME | ENGINE | +------------+--------+ | table_1 | InnoDB | | table_2 | InnoDB | +------------+--------+ 2 rows in set (0.00 sec) Please note that in table_2 creation we obtain a warning (not an error), and table_2 is correctly created using InnoDB, and until this point, everything is working great. When we check the same table on another cluster node, we have: MariaDB [galera_test]> SHOW VARIABLES WHERE Variable_name='enforce_storage_engine' OR Variable_name='sql_mode'; +------------------------+--------+ | Variable_name | Value | +------------------------+--------+ | enforce_storage_engine | InnoDB | | sql_mode | | +------------------------+--------+ 2 rows in set (0.00 sec) MariaDB [galera_test]> SELECT TABLE_NAME, ENGINE FROM information_schema.TABLES where TABLE_SCHEMA = 'galera_test'; +------------+--------+ | TABLE_NAME | ENGINE | +------------+--------+ | table_1 | InnoDB | | table_2 | MyISAM | +------------+--------+ 2 rows in set (0.00 sec) MariaDB [galera_test]> SHOW TABLE STATUS WHERE Name = 'table_2'; +---------+--------+---------+------------+------+----------------+-------------+------------------+--------------+-----------+----------------+---------------------+---------------------+------------+-------------------+----------+----------------+---------+ | Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment | +---------+--------+---------+------------+------+----------------+-------------+------------------+--------------+-----------+----------------+---------------------+---------------------+------------+-------------------+----------+----------------+---------+ | table_2 | MyISAM | 10 | Fixed | 0 | 0 | 0 | 1970324836974591 | 1024 | 0 | NULL | 2015-12-22 11:08:34 | 2015-12-22 11:08:34 | NULL | latin1_swedish_ci | NULL | | | +---------+--------+---------+------------+------+----------------+-------------+------------------+--------------+-----------+----------------+---------------------+---------------------+------------+-------------------+----------+----------------+---------+ 1 row in set (0.00 sec) As you can note, creating a MyISAM table (table_2) on the first node produces a correct InnoDB table, but replication of the same table on the other cluster nodes happens using MyISAM engine. It seems like engine enforcing is used during creation but not during replication.... On 21/12/2015 20:34, Ian Gilfillan wrote: On 21/12/2015 20:10, Nirbhay Choubey wrote: On Mon, Dec 21, 2015 at 12:47 PM, Michele Tota <michele.tota(a)lnf.infn.it> wrote: Hello Nirbhay, thanks for your reply. We have the 10.1.9 mariadb version; the bug that your refers is similar but in our case the enforcing works properly on the node used for the initial write, while replicated writes on other nodes generate tables using another engine. I tried the following on 10.1.9 : Version: Server version: 10.1.9-MariaDB-debug-log Source distribution Node 1: MariaDB [test]> SET @@enforce_storage_engine=INNODB; Query OK, 0 rows affected (0.01 sec) MariaDB [test]> CREATE TABLE t1(i INT) ENGINE=INNODB; Query OK, 0 rows affected (0.07 sec) MariaDB [test]> CREATE TABLE t2(i INT) ENGINE=MYISAM; ERROR 1286 (42000): Unknown storage engine 'MyISAM' Node 2: MariaDB [test]> SHOW TABLES; +----------------+ | Tables_in_test | +----------------+ | t1 | +----------------+ 1 row in set (0.00 sec) Do you get different results? Or your's is a different scenario altogether? Best, Nirbhay From the sounds of it, the sql_mode option NO_ENGINE_SUBSTITUTION is set differently in Nirbhay and Michele's scenarios, so the MyISAM table is converted to InnoDB with a warning in one, and fails in the other. _______________________________________________ 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 -----Segue allegato----- _______________________________________________ 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 _______________________________________________ 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 -- Roberto Spadim SPAEmpresarial - Software ERP Eng. Automação e Controle _______________________________________________ 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 -----Segue allegato----- _______________________________________________ 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

2 1