similar to: pluginsync fails to load custom facts or providers

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

Hi, I''m following http://reductivelabs.com/trac/puppet/wiki/PluginsInModules in order to use a custom fact. My modules looks like: # ls manifests/modules/network/ manifests plugins # ls manifests/modules/network/plugins/facter/primaryint.rb manifests/modules/network/plugins/facter/primaryint.rb as is said in doc. Then: Turn on pluginsync and specify factpath, so that the facts

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

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

So, I''m reading that this works, but I''m obviously missing something somewhere, cause its not... I''m testing a masterless setup, and thus far, pluginsync isn''t doing anything. my puppet.conf looks like [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl classfile = $vardir/classes.txt

With custom type ''vcsrepo'', I''ve been getting this error ever since I restarted my master box: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at /etc/puppet/environments/local/modules/user_mpeebles/manifests/init.pp:56 on node 1001.milespeebles.org Warning: Not using cache on failed catalog Error: Could not

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

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

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

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, 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

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

Seeing an error that I didn''t get in .24 since my recent upgrade today. I have pluginsync set to true, my fileserver conf is pointing to /etc/puppet/plugins and my config file is using the default pluginsource of puppet://puppet/plugins yet the client fails saying it can''t find it. Did the behaviour change in .25 from .24? [puppetd] pluginsync = true pluginsource =

Hi folks, When using SRV lookups (over 2 puppetv3.1.1/RHEL6 masters), does anyone know why the "pluginsync" fails to sync at irregular intervals ? I am using "pluginsync = true" and "pluginsource=puppet:///plugins" on my puppet-clients(3.1.1/RHEL6). Yet I get failures such as "Error: Could not set ''file'' on ensure: Error 404 on SERVER: Could

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

Hi! I''ve installed puppetmaster 2.7.13 on a server with CentOS 6.2 with a rpm supplied by yum.puppetlabs.com. I''ve setup a apache2 vhost with mod_ssl and passenger. The server is configured to autosign the cert requests. The agent installed on the puppetmaster''s server works fine. I''ve a second agent on a server which can sync with the server too. This

Dear all, I have RedHat Server with Puppet and logging in /var/log/puppet But on Solaris it does not work. I am using the CSWpuppet3 3.3.1 Do you have an idea? cat /etc/puppet/puppet.conf # puppet.conf [main] logdir = /var/log/puppet confdir = /etc/opt/csw/puppet config = $confdir/puppet.conf vardir = /var/opt/csw/puppet ssldir = $vardir/ssl server =

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 got 3 custom facts configured within a couple of modules and am using pluginsync to sync them to the clients. My clients are CentOS 5.7. If I run "puppet agent --test -v", I get the following output and the custom facts get loaded and I can use those facts in my module classes: info: Loading downloaded plugin /var/lib/puppet/lib/facter/oraclehome.rb info: Loading

I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with "--pluginsync" but not otherwise. I have "pluginsync=true" in my puppet.conf. Shouldn''t the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.