similar to: Differences between puppet and puppetd

I''m using puppet 0.25.1. I''ve got a simple resource: exec { "/bin/ls $oracle_base/dba/bin/database_backup.ksh": logoutput => on_failure, } and I don''t want it to log every time it''s successfully run: $ sudo tail -F /var/log/messages | grep puppetd Feb 17 16:36:11 test puppetd[26614]: (//my_module/Exec[/bin/ls /u01/

Hello a newbie here. The situation is that: 2 machine one master one client Puppet 0.24.5 This my configuration: Client: /etc/puppet/puppetd.conf [puppetd] server = Asus-Vista-Box logdir = /var/log/puppet vardir = /var/lib/puppet rundir = /var/run master /etc/puppet/manifests/classes/sudo.pp class sudo { file { "/etc/sudoers": owner => "root",

Hi, I''m in the process of evaluating puppet and cfengine for a rollout on a mix of in-house servers and managed customer servers. I''ve always been a pro-cfengine man, and it''s already running on a small setup of 5 machines. But even though I have pretty clear idea of how I should proceed building the system, I''m intimidated by the vast amount of

Hi, As someone new to puppet I''m trying to work out the best way to manage different filesystems and logical volumes on different servers. Specifically I would like to be able to define on a series of nodes different LVM logical volumes to create and mount. I''m trying to do this at the moment with a define of the following type: # Manage a partition and create if needed.

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

I''m having this issue where "puppetd -v -o" hangs (won''t return my prompt) when starting a daemon I wrote. If puppetd is running as a daemon a zombie process is created each time puppetd tries to start my daemon. Puppet detects when the daemon is down and starts it just fine. I''m using version 0.22.3 on RHEL 5. Here''s the class. I''ve

I''ve got the following class that runs if I activate the repo in /etc/yum.conf. If I run "puppetd -t" from the command line it will restart puppetd fine. If I let the class run on it''s own as a deamon puppetd does not restart. The puppetmaster on the other hand does restart using either method. I ran the client in "--debug" but that doesn''t seem to

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

Hey All, Id like to submit two init scripts for debian for puppetd and puppetmasterd, Which is the best to do this? Cheers B _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

On the Configuration refrence page the listen setting is descriped thusly: listen Whether puppetd should listen for connections. If this is true, then by default only the runner server is started, which allows remote authorized and authenticated nodes to connect and trigger puppetd runs. The question is when listen is set to true, does puppetd only listen for remote calls or will it listen for

Hi, From looking at the puppetd --help, there is not currently (at 0.22.4) a method of specifying tags in the puppetd.conf. I was hoping to use this for the following reason: Currently, I use ''noop = true'' in my puppetd.conf, and run ''puppetd --no-noop {tags}'' to install the configurations that I am happy with. This is because I''m currently

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

This feels like a FAQ and sorry if it is, I failed to find an answer. I''d like some advice on handling backward compatibility between puppetd and puppetmaster. My puppetmaster is at v0.24.5 using Debian Lenny packages. I tried to bring up a puppetd client v0.25.4 (Ubuntu 10.04 packages) but failed to have it download the puppetmaster''s certificate. The puppetd client seemed

Hello All I gather that the number of times the daemon checks in is controlled via runinterval (default 1800 seconds) Further, splay (and splaylimit) sets if a pseudo random time is used before checking in. BUT does splay have any meaning if i can not set when the daemon should attempt to check in? Or can i set the check-in time (i may have just missed the option)? cheers chakkerz

Guys, I seriously could not find this topic in the documentation. What do you do when you need to force puppetd hosts get the new settings from puppetmasterd? What I found was only sending USR1 signal to the client process in order to make it refresh its configuration from the master. But I find it a bit inconvenient for a large amount of hosts. There is also puppetrun which, if I understand

Hello... What is the last version of puppet that will work with ruby version 1.6.8? I have a few RHEL 3 machines I would like to run puppetd (only the client, not puppetmaster). They will be updated to RHEL 5 fairly soon, so I don''t want to spend a lot of time trying to get a more recent version of ruby on them. thanks /me buys Luke a beer for all his help :) I now have

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

If you install 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]

Heya, I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a problem with the default setup of Ubuntu. Ubuntu uses network-manager to start the network in the background, which in turn causes puppet to start before the network is up. Puppet will then exit because it can''t resolve the server name. Currently I "solve" this problem by uninstalling

Subject basically says it all. Anyone have a good idea of how to get puppetd restarted after installing a updated puppet.conf? Using the Service types obviously doesn''t work since puppet is already running. Is there no, please reload your config on the next run option? I mean there is always some screwing with a cronjob to just restart puppet once and awhile but I dunno I was