oli's blog

How can I search the following string in a text field: ‘%newline,tabluator,b)%’?

Hello all, on some Linux systems I get the following warning during my MySQL database start-up:

Hello all,

I am getting some MySQL warnings in the error log during the start-up:

In Percona Server we have a STATUS variable indicating roughly possible recovery time:

Table of Contents

• MariaDB Lifetime Support Matrix for MariaDB Releases
• MariaDB Corp Enterprise Support Subscriptions
• MySQL Lifetime Support Matrix for MySQL Releases
• Oracle Corp Enterprise Support Subscriptions for MySQL

Lifetime Support Matrix for MariaDB Releases

¹ MariaDB Announces New Innovation Release Model

Overview

FromDual provides software repositories for their MariaDB/MySQL related software:

A test page in English…

dpkg --force-all -i socat_1.7.2.3-1_amd64.deb

I wanted to install MySQL Galera Cluster 5.6 on the new Ubuntu 14.04 with provided packages. It was a bit tricky to make it work.

We found that there were similar problems with table names with a dash/minus in the name (e.g. `table-name`).
This seems to be fixed in MySQL 5.6.9 and 5.7.0. See bugs #55556, #62237 and #64821.

Hello poorx7,

I see, that you are using an old version of mpm: 0.9.2 the current version is 0.9.3 which you can download from here.

Can you repeat this at the command line? This is such a basic problem that I expect that it has nothing to do with MySQL but with your environment/application/set-up or testing method…

An mpm agent run should not be started before the previous has ended. To make this sure we have some internal checks (and a kill). So the interval should be bigger than the duration of a (the longest) run. Typically we run mpm every 10 seconds and that is fine in most of the cases. But our biggest DB is around 250 Gbyte. So I am wondering why your runs take much longer. Should be visible by the timestamps of the log (debug) file where most of the time is spent.

As mentioned earlier (now with a nicer error message) somebody or something is killing the actual mpm agent job. This is typically a next mpm agent job who has to wait too long for the actual one. The question is more: Why is the first one lasting for so long…

It is done: v0.9.3.

The following fixes in the file lib/FromDualMySQLmaster.pm should do the job:

Thanks, got it:

hostnameX FromDual.MySQL.master.Binlog_ignore_filter 1400661892

I think I see what went wrong. Can you please send me the first 10 lines of the file /tmp/FromDualAgentCache.hostnameX.cache:

I see… The only part in the code where exit code 1 can be reached is the signal TERM trap. Either somebody killed the process or mpm killed a long running former mpm process automatically. How do you start mpm agent?