On Thursday, February 21, 2013 11:08:18 AM UTC-6, Aaron Grewell wrote: > > I've checked, but there's only one set of RPMs installed and the facter > binary points to those. > > # rpm -qa | grep puppet > pe-puppet-enterprise-release-2.0.3-0.pe.el6.noarch > pe-puppet-2.7.9-3.pe.el6.noarch > pe-rubygem-puppet-module-0.3.4-2.pe.el6.noarch > > rpm -qa | grep facter > pe-facter-1.6.4-2.pe.el6.noarch > > # which facter > /usr/local/bin/facter > > # which puppet > /usr/local/bin/puppet > > > There's nothing installed from tarball or gem, this is a newly built box > with just our standard RPM setup on it. > > And I suppose "rpm -q -f /usr/local/bin/facter" tells you "pe-facter-1.6.4-2.pe.el6.noarch"?
And "find / -name 'facter.rb'" doesn't turn up any duplicates? Since Puppet and / or Facter are behaving abnormally, it is not safe to assume anything about the state of the box, particularly with regard to those components. Especially so if the Puppet and Facter RPMs you are using are part of your "standard RPM setup", such that you know they work correctly on others of your systems. You could consider installing custom facts with which to probe Facter's own operating environment in the two cases. You should also snoop the agent's catalog requests to compare the facts it sends with the ones command-line Facter reports. I think it's likely that the problem is on the agent end, but this way you can verify that its not the master somehow mixing things up. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
