search for: puppetbucket

...a problem with one of my puppets. When I run puppetd and a file needs to be updated I get the following error message: debug: //jupiter/freebsd_base/File[/etc/rc.conf]: Changing source debug: //jupiter/freebsd_base/File[/etc/rc.conf]: 1 change(s) debug: Calling fileserver.retrieve debug: Calling puppetbucket.addfile err: Could not call puppetbucket.addfile: #<Errno::EINVAL: Invalid argument - connect(2)> err: //jupiter/freebsd_base/File[/etc/rc.conf]/source: change from {md5}7a0407239c13f0355c0ece466ec613cd to puppet://puppet.domain.net/files/sys/jupiter/rc.conf failed: Invalid argument - con...

I''m trying to wrap my head around these files... do both of them need to reside on the client and master? are there any docs that describe these files and what all the option/ sections are and what they do? Thanks all.... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

What''s this mean? root@gravity:/etc/puppet/manifests# puppetd -v --listen info: Starting handler for Runner info: Starting server for Puppet version 0.22.1 info: Listening on port 8139 notice: Starting Puppet client version 0.22.1 err: Could not run Puppet::Client::MasterClient: Host gravity.example.org not authorized to call puppetmaster.freshness Thanks, Kent -- "It may be true

...-post listen = true runinterval=1800 splay=true summarize = true auth.conf: path / method find, search, save auth yes allow puppetmaster.domain.ltd namespaceauth.conf [fileserver] allow * [puppetmaster] allow * [puppetrunner] allow * [puppetbucket] allow * [puppetreports] allow * [resource] allow * Puppet master version 2.7.9 Puppet client version 2.7.6 -- 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@googleg...

Hi, We''re trying to follow the instructions at http://reductivelabs.com/trac/puppet/wiki/UsingMongrel (Just using a single puppetmaster/mongrel instance and plain mod_proxy for now, instead of balancer one) We got past the "Server is not a class" error by modifying mongrel.rb We also kind-of got past the: /opt/bin/puppetmasterd:293: undefined method `daemonize'' for