similar to: Disable certain facter facts?

I''m trying to load custom facts via /etc/facter/facts.d/* according to instructions on http://docs.puppetlabs.com/guides/custom_facts.html#structured-data-facts I must have missed a setting somewhere because I get nothing. The first clue may be that /etc/facter didn''t exist. I had to create it manually. Is there a setting or search path I need to create? Details: puppet

I have a small environment with a single puppetmaster and puppetdb on the same node that I get sporadic "Failed to submit ''replace facts'' command" errors from nodes. It isn''t consistent about which nodes are causing the error and I can''t find anything else going on at the same time on either the master or the agent that these errors happen. Here

I have written a custom puppet fact using a ruby script. It is very simple - it just adds a string to a fact. However I have written a module but it appears to me that the custom fact has been applied to all my machines without me specifying any node definitions. When I run a puppet agent --test --noop, I see the custom fact appear in /var/lib/puppet/lib/facter. Info: Loading facts in

Hi, I''ve noticed that defining multiple facts in one file is possible, and puppet can make use of them correctly, but when trying to call with facter --puppet they are not shown, do I need something special to make them work as any other single custom fact? Master is running 2.6.7 This is a custom fact with two facts in it: [modules/foobar/lib/facter/foobar.rb ] require

I have successfully updated puppet clients from my master using the built-in WEBrick server. When I updated my setup to using Apache2+passenger, my clients get this error message: err: Could not retrieve catalog from remote server: Error 400 on SERVER: You cannot save facts to the code store; it is only used for getting facts from Facter warning: Not using cache on failed catalog err: Could not

Facter 2.0.0rc1 is a feature release candidate with bug fixes, features and other improvements. Facter 2.0 is designed to accompany the upcoming Puppet 3.0 release and has breaking changes from Facter 1.6.x. Facter 2.0 is not backwards compatible with Puppet 2.6 or 2.7. It includes contributions from the following people: Chris Price, Daniel Black, Daniel Pittman, Garrett Honeycutt, Gary Larizza,

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

Quick and dirty: --- lib/facter.rb (revision 203) +++ lib/facter.rb (working copy) @@ -989,6 +989,18 @@ %x{/usr/sbin/scutil --get LocalHostName} end end + Facter.add(:interfaces) do + confine :kernel => :linux + setcode do + %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|

Hi everyone, I have a fact which looks like that: drbdconnectionstate0. You see the "0" at the end... Now I''d like to access this fact in a "dynamic" way, the "0" should be variable. I''m thinking of something like that: if ${drbdconnectionstate0}${drbddevice} == ''Unconfigured''. But as you may guess, this does not work... Has

My install was working for a couple of months until I rebooted my puppet server. The clients do not report an error when I run puppet agent -t. I''ve attempted to remove certificates and renew. The clients get new certificates, but the console still does not update. Even the puppet server itself is not updating as a client. After reboot the only thing I have noticed that changed

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hi all, first post here... reposting this from Stack Overflow as it didn''t get much traction there... I am using puppet to read a fact from facter, and based on that I apply a different configuration to my modules. Problem: the puppet agent isn''t seeing this fact. Running puppet agent --test interactively works as expected. Even running it non-interactively from a script

Dear All, I''m very new to Puppet Enterprise.... I have the following setup so far: 1. Puppet Master (Puppet Ent) on Ubuntu with its own Agent 2. Puppet Agent on MAC Mountain Lion Everything looked ok but then I noticed this on the MAC (below), which suggested to me I had the wrong Agent? I''m a little confused on how to get the Puppet Ent Agent for MAC? Info: Retrieving

Hello All, I wanted to create two two MySQL database with same user credential using Puppet-MySQL. How can I achieve this? Please find my script below. class mysql::vsdatabase { include mysql mysql::db { ''vidispine'': user => ''user'', password => ''user123'', host => ''db.<hostname>.com'', } } How can I add

When I deploy a module I wrote with couple of custom facts, those facts do not show up in factor. But when I point FACTORLIB to the directory with those factor, they work just fine. I am running a masterless puppet version 2.7.22 and factor 1.7.1 The module structure looks like so: -license ---lib -----facter -------license.rb -------hardware_serial.rb -----puppet Any idea what is causing

I see the instructions for creating custom facter recipes here: http://projects.reductivelabs.com/projects/puppet/wiki/Adding_Facts and in this thread, James Turnbull suggests that Facter might some day support other languages besides ruby: http://groups.google.com/group/puppet-users/browse_thread/thread/8c127ae8898d3bcf/c5ca551b77c4eb67?lnk=gst&q=facter+perl#c5ca551b77c4eb67 He writes:

When I try to connect to my new puppet master, I get an error because of a self-signed certificate: ---snip--- # puppet agent --test --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [self signed certificate in certificate chain for /CN=Puppet CA:

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

Hello, First of all I am new to the Puppet technology. I am trying to get my puppet agent (windows) to reach my puppet master (Linux) server. In this tutorial: http://docs.puppetlabs.com/learning/agent_master_basic.html It claims to test your puppet agent you need to use the ''puppet agent --test'' command. My result when I tried this is: C:\Program Files (x86)\Puppet