Hi Nan, people! On Tue, 12 Oct 2010 11:31:07 -0700, Nan Liu <[email protected]> wrote: > On Fri, Oct 8, 2010 at 12:27 AM, David Schmitt <[email protected]> wrote: >> Yes, it's the http://github.com/DavidS/puppet-mysql/ module. I overlooked >> that Spenser wrote about ralsh. I'm seeing that message also at puppetd >> runtime. > > There's several puppet mysql modules on github. Looks like this one > have my.instances implemented. This should resolve the error at > runtime. > > http://github.com/camptocamp/puppet-mysql/blob/master/lib/puppet/provider/mysql_database/mysql.rb
I had time to investigate this properly. The actual version I'm using does have a self.instances method. I've managed to capture two --debug logs which show the problem: --- working.log +++ failing.log @@ -90,10 +258,8 @@ debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist debug: Creating default schedules -debug: Finishing transaction -605428148 with 0 changes -debug: Loaded state in 0.09 seconds -debug: Prefetching mysql resources for mysql_database -debug: Puppet::Type::Mysql_database::ProviderMysql: Executing '/usr/bin/mysql mysql -NBe 'show databases'' +debug: Finishing transaction -614993188 with 0 changes +debug: Loaded state in 0.02 seconds debug: Prefetching crontab resources for cron debug: Prefetching parsed resources for mount debug: Prefetching parsed resources for sshkey The only difference between the two runs is only a chmod g-x on the plugin destination to cause a reload. This is still 0.25.5. Best Regards, David -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
