similar to: reports without puppetmaster/puppetd

I''m having a hard time shipping off complete puppet manifests/facts/files within a single versioned container to end nodes because of how strict puppet is about not allowing relative paths, even with runtime command line options. (I can not use the puppet/puppetmaster client/server model because of company policies, organization divisions and personnel issues.) When I export a complete

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You folks were so helpful with my last problem I thought I''d try again. I''m attempting to use the services filetype to ensure that ntpd is running on all my hosts. Unfortunately this does not seem to be working on my Gentoo test system. I get the following output on the client log: puppetd[3436]: Starting configuration run

Hi all, This has theoretically been a high priority for a long time, and I''m finally going to get it done, I think. Here''s my plan, and I''d appreciate any comments you might have on it. Currently, sections only have meaning internally, in that one can call ''config.use(section)'' to create any directories needed for that section. Additionally,

I have the following in my site.pp node "pclient.example.com" inherits default {} When I try to start puppetmaster it gives me the following error Starting puppetmaster: Syntax error at ''pclient.example.com'' at /etc/puppet/manifests/site.pp:24 When I change the node declaration to this node ''pclient.example.com'' inherits default {} puppetmaster

The original blastwave.rb would store "no pkg-get in /usr/sbin /usr/ bin" into @@pkgget if pkg-get is not found in the PATH. The patch below modifies blastwave.rb to store the first matching binary in the user''s PATH, or if not found, check the default location (puppetd''s PATH may not be sane) and if still not present and executable, correctly store as nil.

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

Hi guys, Unlike what it says in the documentation and the --help output, I can''t seem to get puppetd to use the --server setting. The only way I can get puppetd to work is to include a ''puppet'' alias to the ip of the machine I''m running puppetmasterd on in my hosts file. The strange thing though, is that the logs of my puppetmaster show that it *is* getting

Hi, I have a Gentoo server running puppetmasterd from Puppet 0.24.1 and a Ubuntu server running puppetd from Puppet 0.23.2. I have added listen=true to the [puppetd] section on the client and run puppetd --debug. I then run puppetrun --debug --host hostname on the puppetmaster server. This is the output I get: Puppetmaster: # puppetrun --debug --host hostname Failed to load ruby LDAP library.

I''m getting certificate errors when I attempt to run puppetd on the puppetmaster. As near as I can tell, this is because I''m using the same puppet.conf for both puppetd and puppetmasterd; but puppetmaster runs as user "puppet" and puppetd runs as user "root", yet both expect the certificates to be readable and chmod 600. I tried telling puppetd to use

I have a test area network that is not routed to the production network because of IP address space re-use between the two networks. I would like the puppetmaster to serve both the production and test area networks. The puppetmaster is on the production network. I understand the puppet to puppetmaster connect to be HTTP using SSL. Can I somehow setup the puppet clients to use an HTTP

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

I''ve just put it out; hopefully the packagers will get it in place soon. Here''s the changelog: Execs now autorequire the user they run as, as long as the user is specified by name. (#430) Files on the local machine but not on the remote server during a source copy are now purged if purge => true. (#594) Providers can now specify that some

Hello I am thinking that it is better to do a cvs export of a project once, on the puppetmaster box, rather than do the same cvs export on all puppet clients, yes? If so, how does one do this? Do you run puppetd on the same box as puppetmasterd and set up the cvs export as an exec for only the node with the same hostname as the puppetmaster? Thanks Jesse Jesse Reynolds Virtual

Anyone using the rrdgraph report on the puppetmaster on Debian stable? I''m trying to get this working and not getting far. I even took rrdtool and librrd0-dev from backports and I still get the same problem. It seems that the rrdfiles are being somewhat created, but nevertheless, the puppetmaster isn''t happy and keeps spewing: err: Report rrdgraph failed: Could not create

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

Hi, https://reductivelabs.com/trac/puppet/wiki/DocumentationStart https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction https://reductivelabs.com/trac/puppet/wiki/PuppetMasters https://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice - Max

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

Anybody else experience the need to restart puppetmasterd before a node can register itself. I''ve been cleaning up my installation here on client nodes and every once and a while I find myself needing to restart the puppetmaster daemon. A client node attempts to connect and never does. A restart fixes things. There doesn''t seem to be anything useful in the error messages

Hi, I''m running Puppet 0.23.0 on my servers, and i got something like this: In a classa.pp file (included in site.pp): class A { file { "test1": ... } } In a classb.pp file (included in site.pp): class B { file { "test2": ... } if defined(File["test1"]) { ... do things ... } if

hi,all I want set up a puppet HA structure. but if the puppetd can set more than one server address ,the work will be simple :D if one puppetmaster have error, the client can auto try the next. I think I can use the heartbeat or dns to do this same thing,but not so good. so I want know the puppetd can direct set in the configure file ? if not,will be add this option? -- Huang