search for: factsourc

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

...1.ssl = true +plugin.activemq.pool.1.ssl.ca = /etc/puppetlabs/mcollective/ssl/mcollective-cacert.pem +plugin.activemq.pool.1.ssl.key = /etc/puppetlabs/mcollective/ssl/mcollective-private.pem +plugin.activemq.pool.1.ssl.cert = /etc/puppetlabs/mcollective/ssl/mcollective-cert.pem # Facts factsource = yaml plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml +# Puppet Classes +classesfile = /var/opt/lib/pe-puppet/classes.txt + +# Puppet Agent plugin configuration +plugin.puppet.command = /opt/puppet/bin/puppet agent +plugin.puppet.config = /etc/puppetlabs/puppet/puppet.conf + +p...

...39;'. factpath = $vardir/lib/facter:$vardir/facts # From where to retrieve facts. The standard Puppet `file` type # is used for retrieval, so anything that is a valid file source can # be used here. # The default value is ''puppet://$server/facts/''. factsource = puppet://<puppetmaster>/facts/ # The pid file # The default value is ''$rundir/$name.pid''. pidfile = <vardir>/agent.pid # The user puppet master should run as. # The default value is ''puppet''. user = apache # The group...

I''m working with a pretty simple config at the moment to track down some issues I''m seeing with custom facts and plugins. I have factsync = true (default locations) and I have a simple fact in /var/lib/puppet/facts/ (actually it''s David''s netmask plugin) my pp file I''m testing with contains only: notice "netmask: ${netmask}" puppet -v

Hello, I''m a little confused how to configure the puppermaster and puppetd to add a new fact. I''ve followed this tutorial http://reductivelabs.com/trac/puppet/wiki/AddingFacts but I''m with doubts about the factsource. In my puppetmaster I have the new fact in /etc/puppet/facts directory. fileserver.conf (on puppetmaster server): [files] path /etc/puppet/files [facts] path /etc/puppet/facts puppet.conf (on client): [puppetd] logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run server=my_server fa...

.../masterhttp.log manifestdir = /etc//opt/csw/puppet/manifests pluginpath = /var//opt/csw/puppet/plugins factdest = /var//opt/csw/puppet/facts authconfig = /etc//opt/csw/puppet/namespaceauth.conf logdir = /var//opt/csw/puppet/log ssldir = /etc//opt/csw/puppet/ssl plugindest = /var//opt/csw/puppet/lib factsource = puppet://mypuppet.example.net/facts rundir = /var//opt/csw/puppet/run genconfig = true pluginsource = puppet://mypuppet.example.net/plugins factpath = /var//opt/csw/puppet/facts libdir = /var//opt/csw/puppet/lib statedir = /var//opt/csw/puppet/state railslog = /var//opt/csw/puppet/log/rails.log...

...vider = psk plugin.psk = mcopwd connector = activemq direct_addressing = 1 plugin.activemq.pool.size = 1 plugin.activemq.pool.1.host = puppet.test.italy.cloudlabcsi.local plugin.activemq.pool.1.port = 61613 plugin.activemq.pool.1.user = mcollective plugin.activemq.pool.1.password = mcopwd # Facts factsource = yaml plugin.yaml = /etc/mcollective/facts.yaml and the result of mco ping debug 2013/11/25 13:02:31: pluginmanager.rb:167:in `loadclass'' Loading Mcollective::Facts::Yaml_facts from mcollective/facts/yaml_facts.rb debug 2013/11/25 13:02:31: pluginmanager.rb:44:in `<<'' R...

...es = "" document_all = false downcasefacts = false dynamicfacts = memorysize,memoryfree,swapsize,swapfree environment = production evaltrace = false external_nodes = none factdest = /var/lib/puppet/facts/ factpath = /var/lib/puppet/lib/facter facts_terminus = facter factsignore = .svn CVS factsource = puppet://puppet/facts/ factsync = false fileserverconfig = /etc/puppet/fileserver.conf filetimeout = 15 freeze_main = false genconfig = false genmanifest = false graph = false graphdir = /var/lib/puppet/state/graphs group = puppet hostcert = /var/lib/puppet/ssl/certs/vusion-production.pem hostcr...

...> ls -ld /var/puppet/ /var/puppet/facts/ drwxr-xr-x 12 puppet puppet 512 Jan 25 18:00 /var/puppet/ drwxr-xr-x 2 puppet puppet 512 Jan 25 18:00 /var/puppet/facts/ facts-related config entries in the dist puppet.conf are: > grep fact puppet.conf | grep -v ''^ *#'' factsource = puppet://puppet/facts/ factpath = /var/puppet/lib/facter:/var/puppet/facts factdest = /var/puppet/facts/ Does anyone know what''s causing this, or how to correct it? Google is showing me a couple other occurrences of this with older versions, but no solutions. -- You recei...

...g: puppet: Setting templatedir to ''$vardir/templates'' debug: puppet: Setting factsignore to ''.svn CVS'' debug: puppet: Setting factpath to ''$vardir/facts'' debug: puppet: Setting factdest to ''$vardir/facts'' debug: puppet: Setting factsource to ''puppet://$server/facts'' debug: puppetmasterd: Setting config to ''$confdir/puppetmasterd.conf'' debug: puppetmasterd: Setting node_name to ''cert'' debug: puppetmasterd: Setting user to ''puppet'' debug: puppetmasterd: Setting m...

Hi, I have looked all over the place and can''t seem to find a complete answer to my query I am setting up MCollective to run alongside my puppet deployment and am having some problems getting it to play as I want it to Basically, I need to make sure that puppet NEVER makes any changes without them being triggered by someone (I honestly can''t see how anyone would ever want

I am currently trying to get mcollective 2.2.4 up and running on RHEL 6 activeqm appears to be running and bound to the correct port, I see the server and client connections to the activemq box. However when I run mco ping all "seems to go well" except I get "No responses recieved" and above that I get the following log messages, debug 2013/05/29 17:02:12: activemq.rb:233:in

...puppetmaster25.balkon.statystyka.net.pem hostcrl = /etc/puppet/ssl/crl.pem rundir = /var/puppet/run ssldir = /etc/puppet/ssl plugindest = /var/puppet/lib privatekeydir = /etc/puppet/ssl/private_keys hostcsr = /etc/puppet/ssl/ csr_puppetmaster25.balkon.statystyka.net.pem factsource = puppet://puppet/facts/ hostpubkey = /etc/puppet/ssl/public_keys/ puppetmaster25.balkon.statystyka.net.pem statedir = /var/puppet/state authconfig = /etc/puppet/namespaceauth.conf publickeydir = /etc/puppet/ssl/public_keys pluginsource = puppet://puppet/plugins privatedir...

...c/puppet/ssl/private_keys/ ip-10-36-11-244.ec2.internal.pem # From where to retrieve facts. The standard Puppet `file` type # is used for retrieval, so anything that is a valid file source can # be used here. # The default value is ''puppet://$server/facts/''. #factsource = puppet://puppet/facts/ # The YAML file containing indirector route configuration. # The default value is ''$confdir/routes.yaml''. route_file = /etc/puppet/routes.yaml # Boolean; whether to use the zlib library # The default value is ''true''...