Issue #21922 has been updated by Josh Cooper. Affected Puppet version changed from 3.3.2 to 3.2.3
We've been looking into this issue, and it is caused when **only** mtime `nsec` field changes on an ext4 filesystem. Puppet thinks the file was modified as part of the pluginsync, and tries to reload the file. However, that file is part of core puppet and should never be reloaded. We are not sure what is causing **only** the `nsec` field to change. James, thanks for attaching your facter output. We noticed two important differences: <pre> $ diff broken.txt works.txt | grep -e path -e kernelrelease < kernelrelease => 2.6.32-358.6.1.el6.x86_64 > kernelrelease => 2.6.32-358.14.1.el6.x86_64 < path => /usr/local/rvm/gems/ruby-1.9.3-p194/bin:/usr/local/rvm/gems/ruby-1.9.3-p194@global/bin:/usr/local/rvm/rubies/ruby-1.9.3-p194/bin:/usr/local/rvm/bin:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/drush:/root/bin > path => > /usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin </pre> The `path` fact returns `ENV['PATH']` so that may not be important. One interesting thing is that we're seeing ruby-193 in the path, but facter's rubyversion returns 1.8.7. The `kernelrelease` fact is interesting. Perhaps a kernel bug was fixed between those two versions? Also both systems report using an ext4 filesystem, and that selinux is disabled. James, could you try upgrading one of your `2.6.32-358.6.1.el6.x86_64` systems to `2.6.32-358.14.1.el6.x86_64`? For anyone else running into this issue, can you: * attach `facter` output, is there a correlation with `kernelversion`? * attach `ruby --version` output ---------------------------------------- Bug #21922: Forced to kill and restart Puppet demon after update to 3.2.3 https://projects.puppetlabs.com/issues/21922#change-101320 * Author: Vincent Gallissot * Status: Needs More Information * Priority: Normal * Assignee: Vincent Gallissot * Category: Red Hat * Target version: * Affected Puppet version: 3.2.3 * Keywords: fedora18 puppet3.2.3 class autoload * Branch: ---------------------------------------- I just updated to Puppet 3.2.3-1 using yum.puppetlabs.com as repo. It worked fine at the beginning but after a random time, each of my Fedora18 node became unworking. Here is the error I got in Puppet Dashboard 1.2.23 : <pre> err Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Puppet 2013-07-24 08:12 CEST err Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Puppet 2013-07-24 08:12 CEST </pre> It's the same error on every nodes. To repair it, I kill puppet process and start it again : "systemctl start puppet.service". The node packages : <pre> [root@node27 ~]# rpm -qa | egrep "(puppet|hiera|facter|ruby)" ruby-1.9.3.448-31.fc18.x86_64 ruby-irb-1.9.3.448-31.fc18.noarch rubygems-1.8.25-6.fc18.noarch ruby-libs-1.9.3.448-31.fc18.x86_64 hiera-1.2.1-1.fc18.noarch ruby-augeas-0.4.1-4.fc18.x86_64 rubygem-io-console-0.3-31.fc18.x86_64 facter-1.7.2-1.fc18.x86_64 libselinux-ruby-2.1.12-7.3.fc18.x86_64 rubygem-json-1.6.8-1.fc18.x86_64 rubygem-rdoc-3.12-6.fc18.noarch ruby-rgen-0.6.5-1.fc18.noarch puppet-3.2.3-1.fc18.noarch ruby-shadow-1.4.1-17.fc18.x86_64 rubygem-bigdecimal-1.1.0-31.fc18.x86_64 OS is Fedora Core 18 x86_64 : [root@node27 ~]# uname -r 3.9.6-200.fc18.x86_64 </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
