ius-coredev team mailing list archive

[bharper <1221261@xxxxxxxxxxxxxxxxxx>]

Hello Sean,

On a test server, I was able to update mysql55 without any issues.

I got asking around some of the support teams here at Rackspace (heavy
users of IUS) to see if others ran into this issue.  I could not find
anyone that reported this issue last night.  One of our DBAs noticed
that it took several minutes for your MySQL to shutdown and the default
timeout within the initscript is 60 seconds:

https://github.com/iuscommunity-
pkg/mysql55/blob/master/SOURCES/mysql.init#L22-L24

This sparked some conversation about changing the default time out.  It
won't surprise me if you will see a pull request or bug about changing
the default time out soon.

-Ben

-- 
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/1221261

Title:
  CentOS/RedHat 6.4 MySQL Server update not starting the MySQL service

Status in IUS Community Project:
  New
Status in CentOS:
  New

Bug description:
  I have two RHEL 6.4 servers in a master slave setup and both
  successfully updated the MySQL Server package [
  mysql55-server-5.5.33-1.ius.el6.x86_64 ] and other MySQL packages and
  gracefully stopped the MySQL service but doesn't restart it.

  -------------------------
  Extract from [ /var/log/yum.log ]:
  Sep 05 04:06:01 Updated: mysql55-libs-5.5.33-1.ius.el6.x86_64
  Sep 05 04:06:03 Updated: mysqlclient16-5.1.61-2.ius.el6.x86_64
  Sep 05 04:06:07 Updated: mysql55-5.5.33-1.ius.el6.x86_64
  Sep 05 04:06:11 Updated: mysql55-server-5.5.33-1.ius.el6.x86_64
  Sep 05 04:06:12 Updated: mysql55-devel-5.5.33-1.ius.el6.x86_64

  -------------------------
  [ Extract from /var/log/mysqld.log ]:
  130905  4:06:12 [Note] /usr/libexec/mysqld: Normal shutdown
  130905  4:06:13 [Note] Event Scheduler: Purging the queue. 0 events
  130905 04:07:15 mysqld_safe A mysqld process already exists
  130905  4:07:37  InnoDB: Starting shutdown...
  130905  4:07:38  InnoDB: Waiting for 200 pages to be flushed
  130905  4:11:03  InnoDB: Shutdown completed; log sequence number 250713953621
  130905  4:11:03 [Note] /usr/libexec/mysqld: Shutdown complete
  130905 04:11:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
  #--Manually started by me hours later:
  130905 08:19:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

  -------------------------
  Both servers started up with no issues when I did it manually, but it just seems that the update never triggered a restart as it did in all other previous mysql55-server updates throughout the year.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/1221261/+subscriptions