In our last 5.5 series release of Percona Server, we included a regression in the RPM packaging that prevented the server from restarting following an upgrade — instead, the server would remain stopped after the upgrade was completed regardless of its state before updating. This caused some problems for some users, especially if automatic upgrading was configured [...]
Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
Percona is glad to announce the release of Percona Server for MySQL 5.5.30-30.2 on April 10, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.30, including all the bug fixes in it, Percona Server 5.5.30-30.2 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of [...]
How Percona does a MySQL Performance Audit
November 24, 2008 By 17 Comments
Our customers or prospective customers often ask us how we do a performance audit (it’s our most popular service). I thought I should write a blog post that will both answer their question, so I can just reply “read all about it at this URL” and share our methodology with readers a little bit. This [...]
Confusing MySQL Replication Error Message
June 4, 2008 By 11 Comments
I already wrote about some MySQL Error Messages which are confusing, here is one more:
1 2 3 4 5 6 7 8 9 10 | 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444286437 080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown: 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444292333 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444292333 080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown: 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444294573 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444294573 080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown: 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444298239 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444298239 |
After setting up new slave Server I’m getting error log file flooded with messages like this and there is no hint in the message what would explain what is wrong. In fact the issue in this case is (because [...]
