Feed Aggregator

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

Global Transaction ID (GTID) is a new feature coming with MySQL 5.6 which introduced a new MySQL replication method called Transaction-based Replication that is depend on GTID.

In a few weeks, I will be speaking at Percona Live London 2014 (November 3-4) about “Transaction-based REPLICATION (GTID) - IMPLEMENTATION AND TROUBLESHOOTING”. I’ll talk about how to implement GTID replication in different scenarios and how to troubleshoot most of the common issues in GTID replication.

Anyone interested in learning more about GTID replication or planing to go with GTID replication in production should attend this talk.

Face-to-face meetings are very welcome, please let me know if you are interested so we can schedule a meeting.

Looking forward to seeing you there!!

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.

apt-get update
apt-get install mysql-server   # this is still 5.5
# from universe
apt-get install mysql-server-5.6 mysql-client-5.6 mysql-client-core-5.6

So far so good. Everything works fine as MySQL 5.6.

Now we have to download Galera 5.6 from Coderships website:

wget https://launchpad.net/galera/3.x/25.3.5/+download/galera-25.3.5-amd64.deb
wget https://launchpad.net/codership-mysql/5.6/5.6.16-25.5/+download/mysql-server-wsrep-5.6.16-25.5-amd64.deb

apt-get install libssl0.9.8   # Should be resolved by the package?
dpkg -i galera-25.3.5-amd64.deb

And then the ugly part:

dpkg --force-all -i mysql-server-wsrep-5.6.16-25.5-amd64.deb

Finally:

 # /etc/mysql/conf.d/wsrep.cnf

[mysqld]
wsrep_provider        = /usr/lib/galera/libgalera_smm.so
wsrep_cluster_address = "gcomm://"

And to activate the changes:

service mysql restart

If you find a better way, please let me …

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.
Taxonomy upgrade extras: 

We have been asked several times by MySQL users about how to install multiple MySQL instances on a single host.
Typically, this is required when testing different MySQL versions or MySQL servers (MySQL server, Percona server and MariaDB server) while no available resources are available.
Sometimes, it is even required to install multiple MySQL instances on a single production server.

In this article, I’ll go through the steps needed to install multiple MySQL instances on a single host (using the tar balls binaries) and how our popular tool MyEnv can make such process so easy.

Prepare MySQL environment

[root@centos-temp ~]# groupadd mysql
[root@centos-temp ~]# useradd -g mysql mysql
[root@centos-temp ~]# su - mysql
[mysql@centos-temp:~]$ mkdir ~/product
[mysql@centos-temp:~]$ mkdir ~/data
[mysql@centos-temp ~]$ cd /downloads
[mysql@centos-temp ~]$ wget http://dev.mysql.com/get/Downloads/MySQL-5.6/mysql-5.6.21-linux-glibc2.5-x86_64.tar.gz
[mysql@centos-temp ~]$ cd ~/product
[mysql@centos-temp ~]$ tar xf …

This week, we did some migrations from MariaDB 10.0 to Percona Server 5.6 at the IT department of a big German bank.

We were perfectly aware that since version 10.0 the MariaDB code base started to diverge slightly away from the MySQL and Percona Server code base which are still pretty close to each other.

Because of the Percona Server option enforce_storage_engine we wanted to do this migration.

We stopped the MariaDB 10.0 server, replaced the binaries by the Percona Server 5.6 binaries, and started the Percona 5.6 server again. After successfully starting the instance we found some error messages in the MySQL error log. By running the mysql_upgrade command some of the problems were fixed but not all of them. Still left problems were:

• The MariaDB binary logs provoked some error messages for the Percona Server:

  [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 25, event_type: -93
  [Warning] Error reading GTIDs from binary log: -1
  [ERROR] Incorrect definition of …

FromDual has the pleasure to announce the release of the new version 1.1.1 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.1.0 to 1.1.1

# cd ${HOME}/product
# tar xf /download/myenv-1.1.1.tar.gz
# rm -f myenv
# ln -s myenv-1.1.1 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv
ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Upgrade from 1.0.5 to 1.1.1

# cd ${HOME}/product
# tar xf /download/myenv-1.1.1.tar.gz
# rm -f myenv
# ln -s myenv-1.1.1 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory …

FromDual has the pleasure to announce the release of the new version 1.1.0 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.0.5 to 1.1.0

# cd ${HOME}/product
# tar xf /download/myenv-1.1.0.tar.gz
# rm -f myenv
# ln -s myenv-1.1.0 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv
ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Replace the following files:

• cp ${HOME}/product/myenv/etc/variables.conf.template /etc/myenv/variables.conf
• cp ${HOME}/product/myenv/bin/myenv.server /etc/init.d/myenv

Changes in MyEnv 1.1.0

MyEnv

• Error with …

Hello earl86

can you please set Debug = 4 in the mpm.conf and send us the output?

The failing code is this:

my $cmd = "$exe --zabbix-server $pServer --port $pPort --input-file $main::gParameter{'CacheFile'} --with-timestamps";

So zabbix_sender cannot send the data to the server. Either IP and port are wrong or there is a Firewall or similar stuff...

Regards,
Oli

I used mpm to monitor a server which having 3 mysql database instance.I keep getting the below errors in the FromDual log file: 30666:2014-08-18 19:24:50.378 - INFO: FromDual Performance Monitor for MySQL (0.9.3) run started. 30666:2014-08-18 19:24:50.378 - INFO: FromDualMySQLagent::setAgentLock 30666:2014-08-18 19:24:50.378 - WARN: Agent Lock file /tmp/FromDualMySQLagent.lock already exists. 30666:2014-08-18 19:24:50.378 - WARN: Another agent with PID 30625 (our PID is 30666) is running. We will abort now. 30666:2014-08-18 19:24:50.378 - INFO: gRemoveLockFile is not set. 30666:2014-08-18 19:24:50.378 - INFO: FromDual Performance Monitor for MySQL run finshed (rc=1316). 711:2014-08-18 18:32:10.461 - INFO: writeDataToCacheFile::writeDataToCacheFile 712:2014-08-18 18:32:10.461 - INFO: FromDualMySQLagent::clearCacheFile 712:2014-08-18 18:32:10.461 - INFO: sendData::sendData 712:2014-08-18 18:32:10.461 - INFO: writeDataToCacheFile::writeDataToCacheFile 711:2014-08-18 18:32:10.462 - INFO: …

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.

0.9.3 has some fixes in the area you are currently struggling... See the Release Notes.

And here it looks like something is wrong with your mpm configuration:

5738:2014-08-06 15:05:51.379 - DBG : /usr/bin/zabbix_sender --zabbix-server --port 10051 --host 'debug' --key FromDual.server.check --value '1' -vv
zabbix_sender [5742]: DEBUG: send value error: gethostbyname() failed for '--port': [3] Unknown server error
Sending failed.

host is missing or is wrong. Can you please send me your mpm configuration file so I can see if our error catching is not good enough?

Thanks,
Oli

It is not clear for many MySQL users that Percona XtraDB Cluster (PXC) and MariaDB Galera Cluster depend on the same Galera library i.e used in Galera Cluster for MySQL which is provided by Codership team:

• Galera Cluster: MySQL Server (by Oracle) + Galera library.
• Percona XtraDB Cluster: Percona Server + Galera library.
• MariaDB Galera Cluster: MariaDB Server + Galera library.

But the question is, are there any performance differences between the three of them ?

Let’s discover that by doing some simple benchmark to test MySQL write performance in Galera Cluster, PXC and MariaDB Galera Cluster installations.

System Information:

HW configurations (AWS Servers):

Nodes Servers HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 8,
  # of threads 16, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 120GB/ 5400RPM.

Load balancer Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2651 v2 @ 1.80GHz (# of cores 4,
  # of threads 8, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 10GB/ …

FromDual holds its annual company meeting this year in Barcelona, Spain.

We are pleased to invite everybody interested in MySQL technologies (MySQL, Galera Cluster, FromDual Tools, Percona Cluster, MariaDB, etc.) to participate on Thursday evening September 11 at the HCC MONTBLANC, Via Laietana 61, to meet, exchange ideas and discuss MySQL related topics.

The event starts at 18:00, we will meet in the hotel lobby. The planned schedule is:

• How to Implement GTID Replication in MySQL 5.6 (25’) and 5’ Questions and Answers.
• MySQL backup/restore for anonymized exports (25’) and 5’ Questions and Answers.
• Break 15 min
• Quick presentation (15’) of YOUR project or company.
• Quick presentation (15’) of YOUR project or company.
• Break 15 min
• Quick presentation (15’) of YOUR project or company.
• Quick presentation (15’) of YOUR project or company.

Please feel free to send us your suggestion about your presentation. Any technical or non-technical MySQL related topic is …

I use the debug.conf is : [debug] Debug = 4 Type = mysqld Modules = server LogFile = /usr/local/mpm/FromDualMySQLagent.log

Try it and result is this: [root@DB22484 mpm]# ./FromDualMySQLagent.pl debug.conf
1

[root@DB22484 mpm]# more /var/log/zabbix/FromDualMySQLagent.log 5738:2014-08-06 15:05:50.345 - INFO: FromDual Performance Monitor for MySQL (0.9.2) run started.

[root@DB22484 mpm]# more FromDualMySQLagent.log 5738:2014-08-06 15:05:50.346 - DBG : The combined (default + section) parameters for section debug are: 5738:2014-08-06 15:05:50.346 - DBG : ZabbixServer - 5738:2014-08-06 15:05:50.346 - DBG : Modules - server 5738:2014-08-06 15:05:50.346 - DBG : LogFile - /usr/local/mpm/FromDualMySQLagent.log 5738:2014-08-06 15:05:50.346 - DBG : Type - mysqld 5738:2014-08-06 15:05:50.346 - DBG : Password - ******** 5738:2014-08-06 15:05:50.346 - DBG : Disabled - false 5738:2014-08-06 15:05:50.346 - DBG : Username - root 5738:2014-08-06 15:05:50.346 - …

Hello poorx7,

The got TERM signal means that the process was hanging too long somewhere and the next start of mpm killed this one.

If I interpret your Chinese output correctly the last message comes from the server module.

Can you please try to just run server manually as follows: FromDualMySQLagent.pl debug.conf with this configuration:

#
# debug.conf
#
[debug]

Debug        = 4
Type         = mysqld
Modules      = server
LogFile      = /tmp/mpm_debug.log

and send us the log file. I heavily assume that mpm is not capable to handle Chinese Linux because we are parsing output and are not expecting some of these characters.
An other approach to narrow down would be to set the locales to LANG=en_US.UTF-8. Maybe then the problem goes away. But just as a work-around. We have to fix it...

Regards,
Oli

If I chose full Modules for MPM,FromDualMySQLagent.log will post this error

28287:2014-08-06 09:06:33.183 - INFO: FromDual Performance Monitor for MySQL (0.9.2) run started. 28287:2014-08-06 09:06:35.862 - INFO: 文件系统 1K-块 已用 可用 已用% 挂载点 28287:2014-08-06 09:06:36.133 - INFO: FromDualMySQLagent::removeAgentLock 28287:2014-08-06 09:06:36.133 - INFO: FromDual Performance Monitor for MySQL run finshed (rc=1).

24689:2014-08-06 09:07:53.250 - INFO: FromDual Performance Monitor for MySQL (0.9.3) run started. 24689:2014-08-06 09:07:55.928 - INFO: 文件系统 1K-块 已用 可用 已用% 挂载点 24689:2014-08-06 09:07:56.201 - ERR : got TERM signal. Cleaning up stuff an exit (rc=1). 24689:2014-08-06 09:07:56.201 - INFO: FromDualMySQLagent::removeAgentLock 24689:2014-08-06 09:07:56.201 - INFO: FromDual Performance Monitor for MySQL run finshed (rc=1).

If I chose only 4 modules in config file like this(can’t choose server and proess): Modules = mpm mysql slave innodb …

FromDual tools provide valuable additional functionality which facilitate and optimize daily operations of your MySQL databases. Since our last newsletter a lot of things have changed in the FromDual tools.

To the MySQL Environment (MyEnv) numerous improvements and suggestions of our customers were added. The most important changes were introduced to the MySQL Backup Manager (mysql_bman).

With the MySQL Ops Center we meet the wishes of our numerous customers, which desire a graphical user interface for operating complex MySQL environments. These users are often little used in handling MySQL but want nevertheless operate more complex MySQL installations as Master/Slave- or Master/Master-replications.

In the MySQL Performance Monitor (mpm) numerous little bugs have been fixed which were reported to us by our customers.

Note: In our MySQL Service Contracts, Business Hour (5x9) and All around the Clock (7x24) the usage and support of our tools is included. If you would like to know more about our service prices, …

FromDual has the pleasure to announce the release of the new version 0.9.3 of its popular Database Performance Monitor for MySQL, Galera Cluster, MariaDB and Percona Server fpmmm.

This release contains various minor bug fixes and improvements.

You can download fpmmm from here.

In the inconceivable case that you find a bug in fpmmm please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

New installation of fpmmm v0.9.3

Please follow our fpmmm installation guide.

Upgrade from 0.x to 0.9.3

# cd /download
# tar xf mysql_performance_monitor-0.9.3.tar.gz
# cd /opt
# tar xf /download/mysql_performance_monitor_agent-0.9.3.tar.gz
# rm -f mpm
# ln -s mysql_performance_monitor_agent-0.9.3 mpm

No other upgrade requirements are known.

Changes in fpmmm v0.9.3

fpmmm agent

• Typos fixed.
• Kill trap reports to the log file as well now.

fpmmm agent and MaaS

• Example for timeshift feature added to configuration template.

MySQL module

• DB down …

If you used the combination of Percona tools (pt-table-checksum and pt-table-sync) - as I mentioned - to get the data synchronized after injecting an empty transaction and starting the slave you won’t face that problem. Otherwise, yes this could be dangerous if that slave promoted to be master AND the other slaves didn’t replicate that transaction yet or when you take a database backup from that slave as well.