On a Ubuntu system which was updated today to facter (diretly via apt.puppetlabs.com) I also see exactly the same error.

Transcription

1 Facter - Bug #17383 Could not retrieve local facts: undefined method `kernel_fact_value' for Facter::Util::Processor:Module 11/01/ :31 pm - Anand Kumria Status: Re-opened Start date: Priority: Normal Due date: Assignee: % Done: 0% Category: Estimated time: 0.00 hour Target version: Keywords: undefined, method Affected Facter version: Branch: Description With facter installed, I receive the following messages: Nov 2 05:43:09 xxx puppet-agent[4012]: Could not retrieve local facts: undefined method kernel_fact_value' for Facter::Util::Processor:ModuleNov 2 05:43:09 xxx puppet-agent[4012]: Failed to apply catalog: Could not retrieve local facts: undefined methodkernel_fact_value' for Facter::Util::Processor:Module This message does not occur with facter dpkg -l grep puppet ii facter puppetlabs1 Ruby module for collecting simple facts abouii hiera puppetlabs1 A simple pluggable Hierarchical Database.ii puppet puppetlabs1 Centralized configuration management agentii puppet-common puppetlabs1 Centralized configuration management History #1-11/02/ :16 am - Andreas Sieferlinger On a Ubuntu system which was updated today to facter (diretly via apt.puppetlabs.com) I also see exactly the same error. #2-11/02/ :32 am - Adam Bishop Seeing this issue on CentOS 6. Pushed the update out to my testing hosts, they re now all in a failed state on the dashboard. I think the update should be pulled. Nov 02 05:37:11 Updated: hiera el6.noarch Nov 02 05:37:11 Updated: 1:facter el6.x86_64 #3-11/02/ :19 am - Loïc Latreille I had the same issue.i just restarted my puppet daemon on my Debian and now is Ok : /etc/init.d/puppet restart. Maybe the deb packet could include a hook to restart the daemon at the end of the upgrade? #4-11/02/ :10 am - Felix Barbeira 05/01/2016 1/6

2 Same issue in a Ubuntu LTS after upgrade the package facter from: puppetlabs1 everything works fine. to: facter puppetlabs1 Returns this error: err Could not retrieve local facts: undefined method `kernel_fact_value' for Facter::Util::Processor:Module err Failed to apply catalog: Could not retrieve local facts: undefined method `kernel_fact_value' for Facter::Util::Processor:Module If I execute the puppet agent manually in a console of the host that is reporting a failure seems like everything works correctly: root@host:~# puppet agent -t Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/iptables.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Caching catalog for vls100.dinaserver.com Info: Applying configuration version ' ' Finished catalog run in 2.70 seconds root@host:~# It looks like it only affects executing the manifests through a puppetmaster, not in local. #5-11/02/ :13 am - Loïc Latreille Have you try to restart your puppetmaster puppet daemon after upgrade? #6-11/02/ :34 am - Felix Barbeira Ok, after restarting the daemon everything works fine. #7-11/02/ :09 am - Anonymous - Description updated - Status changed from Unreviewed to Closed Based on the descriptions of the problem and the resolutions, this is most likely an issue with the agent loading new facter code which is not compatible with older facter code that is already loaded into the process. If the program on disk is going to change and we are going to load in code lazily (which is how facter loads facts), then this will occur. What that means is that updating facter necessitates a restart of a running puppet daemon. The package can t do that restart since this is an issue of the facter code changing and that package should restart the puppet daemon. #8-11/02/ :11 pm - Adam Bishop That s fair enough I can t help wondering if there is a better way though. 05/01/2016 2/6

3 How about if puppetd were to monitor critical files (with inotify or similar) for changes, then reload itself after the catalog run is complete if it detects changes? #9-11/02/ :25 pm - Anand Kumria - Status changed from Closed to Re-opened I m re-opening this because restarting the puppetmaster does not work. As soon as I saw this error occurring, I placed a hold on facter. On my puppetmaster, I have facter (which is the working one). On various client machines, I have facter (which is the one that causes this error). No matter how many times I restart the puppetmaster, the error still occurs. It seems that facter now has to be the same version (or better) than clients; which is a new change to me. #10-11/05/ :03 am - Loïc Latreille Have you try to restart your puppet daemon?not the puppetmaster daemon but the puppet deamon on each client. #11-11/05/ :02 am - Taciano Tres Same problem here, using local Puppet (no daemon, nor PuppetMaster), Ubuntu , Puppet 3.0.1, facter puppetlabs1. It was ok on facter puppetlabs1. #12-11/05/ :06 am - Loïc Latreille You have no puppet daemon to check your system every X minutes? You launch by hand the puppet agent? #13-11/05/ :25 am - Taciano Tres Loïc Latreille wrote: You have no puppet daemon to check your system every X minutes? You launch by hand the puppet agent? Yes, that s right. I m using Puppet to config localhost. #14-11/05/ :34 am - Anand Kumria Hmm. OK yes, restarting each of the puppet agent daemon on each client machine does work. 05/01/2016 3/6

4 This problem; where the facter code update needs to also be noticed by the locally running puppet agent is something that DpkgTriggers (there is an RPM equivalent but the name escapes me) is designed for. See for further details. I personally consider this closed; but it really is sub-optimal having to restart each client machine puppet agent daemon when a facter update occurs. #15-11/07/ :33 am - Konstantin Makarov Hello. I have this problem too. uname -a Linux uno generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux I ve installed facter through apt-get like sudo su - echo " # Puppetlabs products deb precise main deb-src precise main " >> sources.list.d/puppetlabs.list apt-key adv --keyserver keyserver.ubuntu.com --recv 4BD6EC30 apt-get update apt-get install puppetmaster puppet dpkg -s facter Package: facter Status: install ok installed Priority: optional Section: ruby Installed-Size: 158 Maintainer: Puppet Labs <info@puppetlabs.com> Architecture: all Version: puppetlabs1 facter --version ## WHAT? O_o which facter /usr/bin/facter /usr/bin/facter --trace /usr/lib/ruby/vendor_ruby/facter/processor.rb:27: undefined method `kernel_fact_value' for Facter::Util::Processor:Module (NoMethodError) from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:81:in `load' from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:81:in `load_file' from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:43:in `load_all' from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `each' from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all' from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:35:in `each' from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:35:in `load_all' from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:93:in `load_all' 05/01/2016 4/6

5 from /usr/local/lib/site_ruby/1.8/facter.rb:104:in `to_hash' from /usr/local/lib/site_ruby/1.8/facter/application.rb:26:in `run' from /usr/bin/facter:71 And I ve installed facter through gem too: sudo gem install facter Fetching: facter gem (100%) Successfully installed facter gem installed Installing ri documentation for facter Installing RDoc documentation for facter which facter /usr/local/bin/facter /usr/local/bin/facter --version /usr/local/bin/facter --trace /usr/local/lib/site_ruby/1.8/facter/processor.rb:84: undefined method `enum_lsdev' for Facter::Util::Processor:Module (NoMethodError) from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:81:in `load' from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:81:in `load_file' from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:43:in `load_all' from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:38:in `each' from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:38:in `load_all' from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:35:in `each' from /var/lib/gems/1.8/gems/facter /lib/facter/util/loader.rb:35:in `load_all' from /var/lib/gems/1.8/gems/facter /lib/facter/util/collection.rb:93:in `load_all' from /var/lib/gems/1.8/gems/facter /lib/facter.rb:100:in `to_hash' from /var/lib/gems/1.8/gems/facter /lib/facter/application.rb:26:in `run' from /var/lib/gems/1.8/gems/facter /bin/facter:71 from /usr/local/bin/facter:19:in `load' from /usr/local/bin/facter:19 #16-11/07/ :59 pm - Konstantin Makarov I resolved my problem. sudo su - apt-get remove puppetmaster puppet gem uninstall facter apt-get remove rubygem # these files are unnecessary sudo rm -rf /usr/local/lib/site_ruby/1.8/facter* apt-get install puppetmaster puppet which facter /usr/bin/facter facter --version facter --trace 05/01/2016 5/6

6 architecture => amd64 augeasversion => That s OK. 05/01/2016 6/6

7