On Sun, 25 Oct 2009, Douglas Garstang wrote: > I'm using the RPM from the MySQL web site, and the packagers of this > RPM in their infinite wisdom decided that the mysql service should be > automatically started when the RPM was installed.
MySQL installs and upgrades are hard to get right, and may need to do version updateing, or DB recovery, and such -- it is not an atomic operation and frankly cannot ever be. a PGSQL backend would be even harder ;) > This confuses > puppet. The RPM is installed, and the service is started in quick > succession. When puppet runs a 'service check mysql', since mysql > hasn't fully completed it's startup yet, the service script returns > that MySQL isn't running, and puppet goes ahead and starts a second > copy. seems to me like puppet needs to have a better retry mechanism to confirm a failure of a running database, rather than some hubris of 'infinite wisdom' on a condrestart decsion in a server package install. Fixing the problem in puppet's check by adding a backoff and retry a time or two on an asserted non-presence of the DB comes to mind. -- Russ herrold --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
