search for: factpath

I have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded

...t;. ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and puppetmaster node puppet.conf on the agent node : *[main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates pluginsync = true [agent] server = puppet report = true* ----------------------------------------------------------- puppet.conf on the puppetmaster node : *[main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/...

.../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 dropped by pluginsync are loaded by Puppet: [main] pluginsync = true factpath = $vardir/lib/facter as it does not say if it''s talking about master/client, I''ve set vars in both hosts: Master/client: # grep . /etc/puppet/puppet.conf|grep -v "#" [main]...

I have a single LB running Apache with mod_proxy in front of a Puppet master. These are the LB and Puppet master configs: <Proxy balancer://puppetmaster> BalancerMember http://192.168.1.10:8140 </Proxy> Listen 8140 <VirtualHost *:8140> SSLEngine on SSLCipherSuite SSLv2:-LOW:-EXPORT:RC4+RSA SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite

...: undefined method `+'' for nil:NilClass It''s still working (custom fact roothome is /root). On the client, debug lines let me see that the type is retrieving the custom fact correctly. After all, the type runs on the client. The custom fact roothome.rb lives in $libdir/facts ($factpath) as before. Regards, Derek ------------------------------------------------------------------------ For important statutory and regulatory disclosures and more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and there...

...arting 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 facter 1.5RC1, but no difference there as well. Am I missing something? Thanks, Ohad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Pupp...

...ing configuration version ''1367916628'' Notice: Finished catalog run in 0.02 seconds It is in the same host. pwd /etc/puppet/environment/production cat /etc/puppet/puppet.conf [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates server=Debianita.user.arinso modulepath = $confdir/environment/$environment/modules manifest = $confdir/environments/$environment/manifests/site.pp cat /etc/hosts xx.xx.xx.xx Debianita.user.arinso Debianita localhost -- You received this messa...

...t 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 to /var/lib/puppet/facts with no problems. Any suggestions as to how I should start trying to debug this? It looks like a path problem to me, but I''m not sure where this is set or how to check it. James ****************************************************...

.../settings.rb:291:in `parse'' from /usr/lib/ruby/1.8/puppet.rb:220:in `parse_config'' from /usr/sbin/puppetd:269 Here is the /etc/puppet/puppet.conf for the client [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=false server=puppet-master.local;loc environment=test report = true [puppetmasterd] templatedir=/var/lib/puppet/templates **Here is the /etc/puppet/puppet.conf for the master [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var...

...svn export its specific base role path to a test server instance, and then apply that exact revision of manifests, facts and files. Like this -- svn export -r X https://subversion/puppet/trunk/role/qmailcluster//tmp/qmailcluster-puppet-revisionX cd /tmp/qmailcluster-puppet-revisionX puppet -v -d --factpath ./common/facts/ --factpath ./facts/ main.pp I could live with each source file URL having to be absolute (source => file://), but only if I have some way of calling a facter that stores the current working directory in a variable ($base_path) that can be used to adjust file URLs. (source =>...

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.

...ll 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] templatedir=/var/lib/puppet/templates When I run the command puppetd --server my.server.com --waitforcert 60 --test I get the following error err: Could not request certificate: Certificate retrieval failed: Permission denied - /etc/puppet/...

...rns what I''m looking for. I want to put this on the server and distribute it. My puppet clients and puppetmaster server are 0.25.4. On the puppetmaster I edited /etc/puppet/puppet.conf: [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginpath=$vardir/lib/facter pluginsync=true [puppetmasterd] #templatedir=/var/lib/puppet/templates factsync=true factpath=$vardir/facts and also fileserver.conf: # cat /etc/puppet/fileserver.conf [files] path /var/lib/puppet/files allow * [plugins] path /var/lib/puppet/facts...

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

...o these parameters and values come from? I''ve taken a look at my puppet.conf file (which I believe is located in the proper place of: /etc/puppet/puppet.conf) and it 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 templatedir=$confdir/templates [master] # These are needed when the puppetmaster is run by passenger # and can safely be removed if webrick is used. ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY Clearly these values of the ''''...

...ensure => present, } service { ''ntp'': ensure => running, } } the File: / etc / puppet / puppet.conf the client is well [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates prerun_command=/etc/puppet/etckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-commit-post server=puppetmaster [master] # These are needed when the puppetmaster is run by passenger # and can safely be removed if webrick is used. ssl_client...

Hey guys, Does anyone know how to change the location of puppet.conf? In my situation, I don''t want to store it under /etc/puppet/puppet.conf or ~/.puppet/puppet.conf -- I''d like to store it under /opt/puppet/puppet.conf in this example. Is there a method without having to symlink, perhaps with an environment variable like PUPPET_CONF=.... ? Thanks for your time, Jason --

...environments is plain stupid. I am using 0.24.4 My puppet master looks like [main] logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run ssldir=/var/lib/puppet/ssl templatedir=/etc/puppet/templates pluginsync = true pluginsource = puppet://$server/plugins plugindest = $vardir/lib/puppet factpath = $vardir/lib/facter environment = production [puppetmasterd] environments = production,testing storeconfigs=true smtpserver = smarthost dbadapter = mysql dbserver = lhr1-ahbat-01 ldapnodes = true ldapserver = lhr1-ahaaa-02 ldapbase = ou=Hosts,dc=active,dc=com dbname = puppet dbuser = puppetuser d...

...er report = true pluginsync = true certname = doforte.geofusion* *### Server config* *-host* ... *192.168.0.107 gfn-puppetmaster 192.168.0.112 doforte.geofusion doforte* ... *-puppet.config* *[main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter templatedir=$confdir/templates prerun_command=/etc/puppet/etckeeper-commit-pre postrun_command=/etc/puppet/etckeeper-commit-post [master] # These are needed when the puppetmaster is run by passenger # and can safely be removed if webrick is used. ssl_client_header = SSL_CLIENT_S...

...pet/run; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/state; \ puppetd --confdir=/usr/local/.aqadmin/puppet/conf \ --logdir=/usr/local/.aqadmin/puppet/log \ --rundir=/usr/local/.aqadmin/puppet/run \ --statedir=/usr/local/.aqadmin/puppet/state \ --vardir=/usr/local/.aqadmin/puppet/var --factsync \ --factpath=/usr/local/.aqadmin/puppet/var/facts \ --factdest=/usr/local/.aqadmin/puppet/var/facts \ --server=xxxxxxxxxxx --waitforcert 30 --test --debug it has worked from <0.24.1 but now i cannot launch the utils. I tried to use root (--user=root) but guess what, on freeBSD there is no root group so th...