search for: pluginsource

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 = puppet://puppet/plugins [plugins] path /etc/puppet/plugins allow domain.com err: /File[/var/lib/puppet/lib]: Failed...

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 facter 1.5RC1, but no difference there as well. Am I missing something? Thanks, Ohad --~--~---------~--~----~------------~-------~--~----~ You received thi...

...ts log the following error: "Could not evaluate: Could not retrieve information from source(s) puppet://my-dns-name/plugins" which I think means they no longer seem to be able to find the Facter facts I have installed in $modulepath/<module>/lib/facter ? Do I also need to set the pluginsource setting and if so, where to? Any pointers gratefully appreciated! Cheers, Drew -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send ema...

So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync''d to the host it seems when puppetd wakes up and starts its catalog run it doesn''t re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron?

...#39;ntp''], # source => "puppet:///modules/ntp/files/${conf_file}", source => "/etc/puppet/modules/ntp/files/${conf_file}", } } Furhter info from puppet server: puppet apply --configprint: /etc/puppet/modules:/usr/share/puppet/modules pluginsource = puppet://puppet/plugins pluginsync = false Can someone please help me please, as I''m lost with this error? Thanks in advance Dan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit htt...

...elp would be much appreciated. Specially if what I am trying to do with 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 ldapba...

...atically. # The default value is ''$confdir/localconfig''. localconfig = $vardir/localconfig runinterval = 120 #factsync = true # These settings are necessary to enable plugin support via modules # Our custom facter facts rely on this pluginsync=true pluginsource = puppet://$server/plugins plugindest = $vardir/lib factpath = $vardir/lib/facter factdest = $vardir/lib/facter [puppetmasterd] modulepath = /var/lib/puppet/modules certname = puppet --~--~---------~--~----~------------~-------~--~----~ You received this message because you ar...

...ns: wrong header line format this seems to be related to bug #4830. there was a ''workaround'' to add some lib directories to my modules. I did that and it didn''t work. There was another workaround that involves creating a bogus plugins mount in fileserver.conf and setting pluginsource to that mount. While that does eliminate the error, it also breaks pluginsync (not cool). my fileserver.conf looks like this: [plugins] # path /var/lib/puppet/plugins allow * my puppet.conf looks like this: [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssld...

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 not find file_content plugins/puppet/parser/functions/xxxx". This occurs both over passenger and over the over the...

...ns 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 dblocation = /var//opt/csw/puppet/state/clientconfigs.sqlite3 runinterval = 60 localconfig = /var//opt/...

...apply node_name = cert node_name_fact = "" node_name_value = vusion-production node_terminus = plain noop = false onetime = false passfile = /var/lib/puppet/ssl/private/password path = none pidfile = /var/run/puppet/apply.pid plugindest = /var/lib/puppet/lib pluginsignore = .svn CVS .git pluginsource = puppet://puppet/plugins pluginsync = true postrun_command = /etc/puppet/etckeeper-commit-post preferred_serialization_format = pson prerun_command = /etc/puppet/etckeeper-commit-pre privatedir = /var/lib/puppet/ssl/private privatekeydir = /var/lib/puppet/ssl/private_keys publickeydir = /var/lib/p...

puppet schrieb: > #779: access to inherited variables from within a template > -----------------------------------------+---------------------------------- > Reporter: simu | Owner: luke > Type: enhancement | Status: new > Priority: normal | Milestone: >

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

...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 = /etc/puppet/ssl/private factpath = /var/puppet/facts/ hostcert = /etc/puppet/ssl/certs/ puppetmaster25.balkon.statystyka.net.pem localcacert = /etc/puppet/ssl/certs/ca.pem logdir = /var/puppet/log certdir = /etc/puppet/ssl/certs req...

I tried to install the ''mongrel'' gem tonight via puppet in an attempt to migrate from webrick to mongrel as described on the puppet site[1]. I added the following to my manifest: package { "rubygems": ensure => installed; "mongrel": ensure => installed, provider => gem, require => Package["rubygems"]; }

...9;'. privatekeydir = /etc/puppet/ssl/private_keys # From where to retrieve plugins. 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/plugins''. pluginsource = puppet://puppet/plugins # Which type of queue to use for asynchronous processing. If your stomp server requires # authentication, you can include it in the URI as long as your stomp client library is at least 1.1.1 # The default value is ''stomp://localhost:61613/''....

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction