similar to: configuring puppet to run custom facts

I''ve added some custom facts to my Puppet setup but they aren''t being displayed by facter. I''ve tested them and they work correctly when run manually (and I''ve also tried a number of those listed on the wiki) but they aren''t included in facter''s output. I am using the default settings for factdest and factpath and the facts are being copied

May I please ask again for some assistance with the question below? I hope somebody can help me. Thanks, Ed Greenberg -------- Original Message -------- Subject: Re: [Puppet Users] Using custom facts in Puppet Date: Tue, 16 Nov 2010 13:14:06 -0600 From: Ed Greenberg <edg@greenberg.org> Reply-To: puppet-users@googlegroups.com To: puppet-users@googlegroups.com On 11/16/2010 09:33

possibly related to (or the same as) issues 4830 and 2244, i''m getting errors when adding a custom fact and provider to a module to propagate to clients. am i missing something here? i tried the workaround of adding a fileserver.conf to the master (referenced below and in the tickets) with no change. thanks for any help. here''s a pile of details: puppetmaster 2.6.9 is running

Is there a recommended way to set $FACTERLIB so that Puppet will be able to access custom facts when running as a Red Hat service? If I export $FACTERLIB=/var/puppet/facts and then run Puppet manually I have no problems, but I''m not sure how I should be setting $FACTERLIB when Puppet is running automatically. Cheers, James

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:

Hi all, I have installed and configure puppet client in new virtual machine, but I have this error when running *puppetd --test (even if I run /etc/init.d/puppet restart) /usr/lib/ruby/1.8/puppet/defaults.rb:136:in `handle'': Invalid environment test (ArgumentError) from /usr/lib/ruby/1.8/puppet/util/settings.rb:299:in `parse'' from

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 am trying out having multiple environments so that I can push a test config to a single server in production. The idea being that I could push out a config change to one server and see if the change works in production. If it does then I can merge the change into the production environment and push the change out to all the clients. So to test this I made a change to a config file in testing

I''m a newbie attempting to get a custom fact distributed to clients. I''ve followed the instructions at http://reductivelabs.com/trac/puppet/wiki/AddingFacts and based my first fact on a simple recipe. I''m having at least one problem and possibly more. 1) Puppet/facter fails to load the custom fact, complaining that "non- sh interpreters are not currently

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hi I''m trying to add extra facts to facter. The puppetd is running on Debian Etch Amd64 as Xen 3.1 guest. I''ve follow the Wiki on adding the facts. First I used relative path in the manifest and added "factsync=true" in client''s puppetd.conf. And then tested it with "puppetd -vt". But no matter what i tried, this error came: File paths must be fully

2009/1/6 Robin Lee Powell <rlpowell@digitalkingdom.org> > > On Tue, Jan 06, 2009 at 11:23:56AM +0100, Olivier wrote: > > Hi, > > > > I''m new to Puppet. > > I installed Puppet on Debian Lenny (version is 0.24.5). > > > > When I''m trying to use puppet locally (on the machine I installed > > puppetmaster on), I keep getting

Hi, When starting puppet on a new machine, (or when the $vardir/lib is empty) puppet will not run the facts, it will only copy them. on the second time puppet runs, it works quiet well: on the client its defined: [main] pluginsync = true pluginsource = puppet://$server/plugins plugindest = $vardir/lib/puppet factpath = $vardir/lib/puppet/facter [puppetd] factsync = true I also tried with

Hello all, I''m running puppet for the first ime. I''ve finished the install but I''m stuck at the certificate part. The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet client (0.24.8-4.el5) is running on CentOS 5.3. After the install, from the client side, I''ve run: puppetd --server puppetmaster.domain.com --waitforcert 60 --test On the

Hello, I''m trying to add an environment variable as fact like this : #export $FACTER_test="infof" #facter | grep test test => infof But my fact don''t synchronize with puppet master. I don''t see it in / var/puppet/yaml/clientfile.yaml If I want this works, I''ve need to start puppet like this : #puppetd -vt --factsync but factsync''s

Hi, ppl I dont know what to do. I configure a new client do sync with my server. the server accept de client_cert without errors and then when i run the "puppet agent -t" agaion i got this error output info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server

Hello, I have been following through some of the documentation trying to make use of puppet in a test environment. I went ahead and tried to install puppet-passenger and puppet dashboard. I think i have succesfully done this, because at mymaster.local:3000/ I get the dashboard webpage (albeit with no nodes or anything reporting) and at https://mymaster.local:8140 I get a cert trying to be

If you install puppet from the ubuntu 9.04 repositories (apt-get install puppet) it sets up puppet differently than the gem. The differences are obvious from the /etc/puppet/puppet.conf which looks like this [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true [puppetmasterd]

I''ve upgraded to puppet v2.6.2 on ubuntu (clients and server) and now I get this error messages related to pluginsync: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate'': wrong header line format err: /File[/var/lib/puppet/lib]: Could not evaluate: wrong header line format Could not retrieve file

I am having issues with filebucket. I have looked through the puppet users google groups with similar issues but have not found a solution that works. I am trying to setup a central filebucket on the puppetmaster server. I am replacing the client''s /etc/puppet/puppet.conf file with a preconfigured version. The server delivers a copy of the puppet.conf file to the client, but the backup