Comment 10 for bug 1311840

Revision history for this message
Tomislav Plavcic (tplavcic) wrote :

@monty,

I have tried to reproduce with the same setup and it works for me. Can you check if the service was running before the upgrade?

Here's my log:

Centos 6.5-64, PS 5.5.39-36.0 -> 5.5.40-36.1

=== INSTALLED PACKAGES
[vagrant@t-centos6-64 ~]$ rpm -qa | grep Percona
Percona-Server-shared-55-5.5.39-rel36.0.el6.x86_64
Percona-Server-server-55-5.5.39-rel36.0.el6.x86_64
Percona-Server-client-55-5.5.39-rel36.0.el6.x86_64

=== STATUS BEFORE UPGRADE
[vagrant@t-centos6-64 ~]$ sudo service mysql status
 SUCCESS! MySQL (Percona Server) running (2791)

=== UPGRADE
Running Transaction
  Updating : Percona-Server-shared-55-5.5.40-rel36.1.el6.x86_64 1/6
  Updating : Percona-Server-client-55-5.5.40-rel36.1.el6.x86_64 2/6
  Updating : Percona-Server-server-55-5.5.40-rel36.1.el6.x86_64 3/6
...
Giving mysqld 5 seconds to exit nicely
Starting MySQL (Percona Server).. SUCCESS!
Giving mysqld 5 seconds to start

=== STATUS AFTER UPGRADE
[vagrant@t-centos6-64 ~]$ sudo service mysql status
 SUCCESS! MySQL (Percona Server) running (3098)