- discuss - lists.mariadb.org

[Maria-discuss] Heartbleed (OpenSSL) -bug and MariaDB
by Peter Laursen 10 Apr '14

10 Apr '14

A far as I understand MariaDB uses OpenSSL (unlike Oracle-MySQL that uses YaSSL). Now what about the heartbleed bug: http://heartbleed.com/ Will all still suported MariaDB versions (5.1, 5.2, 5.3, 5.5 and 10.0 are all still suported I think?) need a release for this bug in OpenSSL? -- Peter -- Webyog

3 6

[Maria-discuss] New Question: Problem with multi master replication and a trigger with mariadb 10.0.10.
by AskMonty KB 10 Apr '14

10 Apr '14

Hello, A new question has been asked in "Triggers" by wschwauer: -------------------------------- I have a problem with multi master replication and a trigger with mariadb 10.0.10. First. I have installed master db with name DB1 on a Windows system 1 master1 with a table m1, m2, m3, mg Second, I have install “slave” db with name DB1 on a Windows system 2 slave1 with a table s1, s2 Now I setup a row based replication with the table m1 from master1 to slave1. Next I setup a row based replication with the table s1 from slave1 to master1. Now I have a master with table m1, m2, m3, mg and s1 and a slave with table s1, s2 and m1. All replications work well. Ad next I create a trigger on master to manipulate and copy the data from table s1 to mg, but it do not work. I found this information (https://mariadb.atlassian.net/browse/MDEV-5095) but I have not the variable slave_run_triggers_for_rbr or slave_run_triggers. When I create the same trigger on master with table m1 and mg, it still works. But it not work with the replication table s1. I think it is a problem with the replication table s1. Can anyone help me? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/problem-with-multi-master-replication-and-a-trigge…

1 0

[Maria-discuss] Backup locks in MariaDB
by Colin Charles 09 Apr '14

09 Apr '14

Hi! Percona Server 5.6 includes backup locks that work with xtrabackup 2.2 MariaDB 10 might want this feature as well. More information: http://www.mysqlperformanceblog.com/2014/03/11/introducing-backup-locks-per… Thoughts? -- Colin Charles, Chief Evangelist, SkySQL - The MariaDB Company blog: http://bytebot.net/blog/| t: +6-012-204-3201 | Skype: colincharles

1 0

[Maria-discuss] New Question: Connecting issues
by AskMonty KB 09 Apr '14

09 Apr '14

Hello, A new question has been asked in "MariaDB ODBC Driver" by openiduser41: -------------------------------- Hi I have en application written in Visual Studio 2008 where I use CDatabase to connect to MariaDB via ODBC. When I try and connect I get an exception with the text "Invalid information type" I have tried alot of ODBC connect strings for instance: DRIVER={MariaDB ODBC 1.0 Driver};SERVER=localhost;DATABASE=mydb;UID=test;PWD= or DSN=mydb When I create the DSN every think looks ok. If I change to use {MySQL ODBC 3.51 Driver} it works fine. Another thing is that even though I use the noOdbcDialog option, it still show an ODBC dialog. Also if I create a new Project with database support in VS2008 and select a mariaDB DSN Visual studio crashes. Thanks for your help. /Kennet -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/connecting-issues/

1 0

[Maria-discuss] locking on endpoints of range deletes
by Daniel Black 09 Apr '14

09 Apr '14

Anyone see why tx_isolation=REPEATABLE-READ should have a next-record lock on record 3 rather than a record lock? SESSION 1: MariaDB [drupal_test]> create table x ( x bigint unsigned not null auto_increment, PRIMARY KEY x) ); Query OK, 0 rows affected (0.02 sec) MariaDB [drupal_test]> select @@tx_isolation; +-----------------+ | @@tx_isolation | +-----------------+ | REPEATABLE-READ | +-----------------+ 1 row in set (0.00 sec) MariaDB [drupal_test]> insert into x values (1),(2),(3); Query OK, 3 rows affected (0.00 sec) Records: 3 Duplicates: 0 Warnings: 0 MariaDB [drupal_test]> begin -> ; Query OK, 0 rows affected (0.00 sec) MariaDB [drupal_test]> delete from x where x <= 3; Query OK, 3 rows affected (0.00 sec) ---TRANSACTION 290E30, ACTIVE 12 sec 2 lock struct(s), heap size 376, 4 row lock(s), undo log entries 3 MySQL thread id 7437, OS thread handle 0x7f37307f5700, query id 3298653 localhost debian-sys-maint sleeping TABLE LOCK table `drupal_test`.`x` trx id 290E30 lock mode IX RECORD LOCKS space id 82547 page no 3 n bits 72 index `PRIMARY` of table `drupal_test`.`x` trx id 290E30 lock_mode X SESSION 2: MariaDB [drupal_test]> insert into x values (DEFAULT); ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction And it works in READ-COMMITTED SESSION 1: MariaDB [drupal_test]> set tx_isolation='READ-COMMITTED'; begin; delete from x where x <= 3; Query OK, 0 rows affected (0.00 sec) Query OK, 0 rows affected (0.00 sec) Query OK, 3 rows affected (0.00 sec) SESSION 2: ---TRANSACTION 290E33, ACTIVE 44 sec 2 lock struct(s), heap size 376, 3 row lock(s), undo log entries 3 MySQL thread id 7437, OS thread handle 0x7f37307f5700, query id 3298661 localhost debian-sys-maint sleeping TABLE LOCK table `drupal_test`.`x` trx id 290E33 lock mode IX RECORD LOCKS space id 82547 page no 3 n bits 72 index `PRIMARY` of table `drupal_test`.`x` trx id 290E33 lock_mode X locks rec but not gap MariaDB [drupal_test]> insert into x values (DEFAULT); Query OK, 1 row affected (0.00 sec) -- -- Daniel Black, Engineer @ Open Query (http://openquery.com.au) Remote expertise & maintenance for MySQL/MariaDB server environments.

1 0

[Maria-discuss] Trouble getting MariaDB to start up
by Jonathan Gazeley 07 Apr '14

07 Apr '14

Hi folks, I'm reasonably experienced with MySQL and MMM for cluster management but now I am working on a project to replace this with a MariaDB Galera cluster. Basic system info: [jg4461@db3 ~]$ uname -a Linux db3.resnet.bris.ac.uk 2.6.32-431.11.2.el6.x86_64 #1 SMP Tue Mar 25 19:59:55 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [jg4461@db3 ~]$ cat /etc/redhat-release CentOS release 6.5 (Final) [jg4461@db3 ~]$ mysql -V mysql Ver 15.1 Distrib 5.5.36-MariaDB, for Linux (x86_64) using readline 5.1 I've set up a Galera prototype with two nodes and I got the clustering working. Then I decided to add a load of config options from my old MySQL install to the MariaDB install, and now it fails to start up, but doesn't give an obvious error message. The options were mostly to do with InnoDB buffers etc. This is the output in the log file /var/lib/mysql/db3.resnet.bris.ac.uk.err, the init script hangs for ages after this without giving any further output. 140331 15:07:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 140331 15:07:49 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.mlbT89' --pid-file='/var/lib/mysql/db3.resnet.bris.ac.uk-recover.pid' 140331 15:07:51 mysqld_safe WSREP: Failed to recover position: '140331 15:07:49 InnoDB: The InnoDB memory heap is disabled 140331 15:07:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140331 15:07:49 InnoDB: Compressed tables use zlib 1.2.3 140331 15:07:49 InnoDB: Using Linux native AIO 140331 15:07:49 InnoDB: Initializing buffer pool, size = 1.5G 140331 15:07:49 InnoDB: Completed initialization of buffer pool 140331 15:07:49 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 140331 15:07:49 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 140331 15:07:49 InnoDB: Waiting for the background threads to start 140331 15:07:50 Percona XtraDB (http://www.percona.com) 5.5.36-MariaDB-33.0 started; log sequence number 1607692 140331 15:07:50 [Note] Plugin 'FEEDBACK' is disabled.' My MariaDB config file is attached. Please could someone point me in the right direction of where to go with debugging this. I can't find any other error message so I'm struggling to track down why the server can't start. Any advice gratefully accepted! Thanks, Jonathan

4 6

[Maria-discuss] New Question: upgraded to MariaDB 10.0 but the systemctl status mariadb.service is not working? mysql command works instead?
by AskMonty KB 06 Apr '14

06 Apr '14

Hello, A new question has been asked in "MariaDB community" by cyberdomecyberdome: -------------------------------- Have the MariaDB programmers taken out the systemctl status mariadb.service command from the MariaDB 10.0 server. the command was working on my mariadb 5.5 server. can someone help shed some light Server: MariaDB Server version: 10.0.10-MariaDB MariaDB Server Protocol version: 10 Connection: Localhost via UNIX socket Server characterset: latin1 Db characterset: latin1 Client characterset: utf8 Conn. characterset: utf8 UNIX socket: /var/lib/mysql/mysql.sock Uptime: 1 day 14 hours 11 min 29 sec Threads: 1 Questions: 143 Slow queries: 0 Opens: 31 Flush tables: 1 Open tables: 57 Queries per second avg: 0.001 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/upgraded-to-mariadb-100-but-the-systemctl-status-m…

1 0

[Maria-discuss] Building on Windows with cmake 2.8.12.2 and Visul Studio 2012
by Wes Bullard 03 Apr '14

03 Apr '14

I've been trying for a few days now first with 10.0.9 and now with 10.0.10 to build on windows x64 both by command line and in visual studio 2012. Straight building seems to go fine but if I try and build --target package or even --target msi I get errors about missing pdb files. This is both in RelWithDebInfo and Release configuration. The following are outputs from the builds RelWithDebInfo - http://paste.chainscriptz.net/?paste=5 Release - http://paste.chainscriptz.net/?paste=6 This is in Visual Studio 2012 Ultimate update 4. Sorry if this is in the wrong format first time using a mailing list.

2 1

[Maria-discuss] New Question: Circular Dependency on 5.5.36
by AskMonty KB 03 Apr '14

03 Apr '14

Hello, A new question has been asked in "Installing MariaDB RPM Files" by peter-mclarty: -------------------------------- Does anyone have a clever solution to installing 5.5.36 when compat and common rpms have a circular dependency, Since the contents appear to be needed do we need them packaged separately? [root@faws01_dbs itadmin]# yum install MariaDB-5.5.36-centos6-x86_64-compat.rpm Loaded plugins: product-id, subscription-manager Updating certificate-based repositories. Setting up Install Process Examining MariaDB-5.5.36-centos6-x86_64-compat.rpm: MariaDB-compat-5.5.36-1.el6.x86_64 Marking MariaDB-5.5.36-centos6-x86_64-compat.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package MariaDB-compat.x86_64 0:5.5.36-1.el6 will be installed --> Processing Dependency: MariaDB-common for package: MariaDB-compat-5.5.36-1.el6.x86_64 --> Finished Dependency Resolution Error: Package: MariaDB-compat-5.5.36-1.el6.x86_64 (/MariaDB-5.5.36-centos6-x86_64-compat) Requires: MariaDB-common You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@faws01_dbs itadmin]# yum install MariaDB-5.5.36-centos6-x86_64-common.rpm Loaded plugins: product-id, subscription-manager Updating certificate-based repositories. Setting up Install Process Examining MariaDB-5.5.36-centos6-x86_64-common.rpm: MariaDB-common-5.5.36-1.el6.x86_64 Marking MariaDB-5.5.36-centos6-x86_64-common.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package MariaDB-common.x86_64 0:5.5.36-1.el6 will be installed --> Processing Dependency: MariaDB-compat for package: MariaDB-common-5.5.36-1.el6.x86_64 --> Finished Dependency Resolution Error: Package: MariaDB-common-5.5.36-1.el6.x86_64 (/MariaDB-5.5.36-centos6-x86_64-common) Requires: MariaDB-compat You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest As you can see one is dependent on the other, that is not a smart approach Any thoughts Peter -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/circular-dependency-on-5536/

1 0

[Maria-discuss] New Question: unable to upgrade from MariaDB 5.5 to MariaDB 10.0 using YUM
by AskMonty KB 01 Apr '14

01 Apr '14

Hello, A new question has been asked in "MariaDB community" by cyberdomecyberdome: -------------------------------- I created a file mariadb.repo and put in info for mariadb 10.0, when I run the command yum -y update or yum -y upgrade mariadb-server mariadb-client, Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package MariaDB-server.x86_64 0:10.0.10-1.fc20 will be obsoleting ---> Package mariadb-server.x86_64 1:5.5.36-1.fc20 will be obsoleted --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: MariaDB-server x86_64 10.0.10-1.fc20 mariadb 49 M replacing mariadb-server.x86_64 1:5.5.36-1.fc20 Transaction Summary ================================================================================ Install 1 Package Total download size: 49 M Downloading packages: MariaDB-10.0.10-fedora20-x86_64-server.rpm | 49 MB 00:00:10 Running transaction check Running transaction test Transaction test succeeded Running transaction sed: invalid option -- '1' Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]... -n, --quiet, --silent suppress automatic printing of pattern space -e script, --expression=script add the script to the commands to be executed -f script-file, --file=script-file add the contents of script-file to the commands to be executed --follow-symlinks follow symlinks when processing in place -i[SUFFIX], --in-place[=SUFFIX] edit files in place (makes backup if SUFFIX supplied) -c, --copy use copy instead of rename when shuffling files in -i mode -b, --binary does nothing; for compatibility with WIN32/CYGWIN/MSDOS/EMX ( open files in binary mode (CR+LFs are not treated specially)) -l N, --line-length=N specify the desired line-wrap length for the `l' command --posix disable all GNU extensions. -r, --regexp-extended use extended regular expressions in the script. -s, --separate consider files as separate rather than as a single continuous long stream. -u, --unbuffered load minimal amounts of data from the input files and flush the output buffers more often -z, --null-data separate lines by NUL characters --help display this help and exit --version output version information and exit If no -e, --expression, -f, or --file option is given, then the first non-option argument is taken as the sed script to interpret. All remaining arguments are names of input files; if no input files are specified, then the standard input is read. GNU sed home page: <http://www.gnu.org/software/sed/>. General help using GNU software: <http://www.gnu.org/gethelp/>. ****************************************************************** A MySQL or MariaDB server package () is installed. The current MariaDB server package is provided by a different vendor (package is not installed) than Monty Program AB. Some files may be installed to different locations, including log files and the service startup script in /etc/init.d/. Upgrading directly from MySQL <unrecognized version package is not installed> to MariaDB 10.0 may not be safe in all cases. A manual dump and restore using mysqldump is recommended. It is important to review the MariaDB manual's Upgrading section for version-specific incompatibilities. A manual upgrade is required. - Ensure that you have a complete, working backup of your data and my.cnf files - Shut down the MySQL server cleanly - Remove the existing MySQL packages. Usually this command will list the packages you should remove: rpm -qa | grep -i '^mysql-' You may choose to use 'rpm --nodeps -ev <package-name>' to remove the package which contains the mysqlclient shared library. The library will be reinstalled by the MariaDB-shared package. - Install the new MariaDB packages supplied by Monty Program AB - Ensure that the MariaDB server is started - Run the 'mysql_upgrade' program This is a brief description of the upgrade process. Important details can be found in the MariaDB manual, in the Upgrading section. ****************************************************************** error: %pre(MariaDB-server-10.0.10-1.fc20.x86_64) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package MariaDB-server-10.0.10-1.fc20.x86_64 Verifying : MariaDB-server-10.0.10-1.fc20.x86_64 1/2 1:mariadb-server-5.5.36-1.fc20.x86_64 was supposed to be removed but is not! Verifying : 1:mariadb-server-5.5.36-1.fc20.x86_64 2/2 Failed: MariaDB-server.x86_64 0:10.0.10-1.fc20 -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/unable-to-upgrade-from-mariadb-55-to-mariadb-100-u…

1 0