similar to: strange behavior from purge

So I have the following: define nagios::service ( $nagios_template = ''service-template'', $host_name = $fqdn, $service_groups = '''', $contact_groups = $default_contact_group, $max_check_attempts = 3, $dependency = false, $dependent_host = $fqdn, $dependent_service = '''', $check_command = '''' ) {

I''m not sure if this has been posted previously, but I couldn''t find any information on it. I added a cron job via the cron type and it installed properly. Next, I removed the cron type from the manifest. The result was that, while the entry was no longer in the yaml file, the cron entry was not removed! Is this a bug, or the way that it is supposed to function? Thank you,

I attempted the following: resources { service: purge => true, noop => true } service { sshd: ensure => running; iptables ensure => running; } And got the following message: notice: Starting configuration run err: Found a bug: uninitialized constant Parse notice: Finished configuration run in 0.47 seconds When I remove the ''resources'' line, everything works

I have a little issue with purging. I use: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rules'']: ensure => directory, mode => 0700, recurse => true, purge => true, } but purging does not work, i can do a touch

Is there a way to exec something on purge?

I have a situation where I''d like to perform some actions when a node is removed from a class. I have a few (homegrown) services that install ssh keys in authorized_keys and it''s possible that a node may have the service enabled and disabled during it''s lifetime. When disabled I''d like to clean up the ssh keys for security reasons. This brings up the broader

I use a simple yaml file and and an external nodes script to express each of my nodes. What I''m trying to do is make sure that all individual data is expressed at the node level and not have anything in classes or modules that isn''t generic and shared. the example below works really well but I can''t express it via my external nodes, I have to bury it in a class (or

Hi all, [Please CC me in replies, I am not subscribed to this list.] First of all, thanks for puppet! It is a very nice tool and I''m in the (slow) process of using it to manage my new Xen-based virtual server farm with it. Most of the "simple" tasks worked well so far, and I may be able to add a few recipies to the Wiki when I find time to do so. However, is there any way

Hi, We''re using thin stored configs heavily to manage things like Munin and Nagios and we''re currently wondering what to do when nodes go away, or change considerably. If we get rid of a server then all it''s stored config is still present in the database, as well as it''s nagios and munin configurations. We created a script that iterates through the database

I turned on reporting the other day and I''m seeing alot of these when puppet runs. Especially during times when nothing is going on (middle of the night etc) Tue Dec 11 12:34:48 -0500 2007 //base/puppet/puppet::client/Service[puppet]/ensure (notice): ensure changed ''stopped'' to ''running'' It''s also quite odd that puppet when it runs it thinks

I''m seeing these in my logs on my puppetmaster: puppetmasterd[4111]: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: DELETE FROM fact_values WHERE "id" = 8 currently this is 0.24.0 relect from some previously collected resource that wasn''t cleaned up? upgrade issue? nothing to worry about? that''s the only

Hi All, is it possible to delete cronjobs by patterns using ''cron'' resource? I.e. I want to make sure that there is no any cronjob that contains "/ path/to/some/unneeded_file" command in root crontab without knowing the command possible parameters and schedule. If no, any suggestions about how it can be performed are welcome. Thanks in advance

Hi, We are totally sold on Pupet (what a nice concept) and are trying to setup a proof-of-concept. We are trying to learn a bit from other people''s work by integrating external modules. One of the modules we wanted to start with was the ''ntp'' module from David Schmitt. It clearly uses some functionalities from the ''common'' module, which we also

I was playing around with the generate() function and was wondering if anyone was making us of it. The current way I''m attempting to use it is to determine what the homedir of a given user is. I have: --- $homedir = generate("/bin/sh", "-c", "grep ^${name} /etc/passwd | cut -d: -f6") --- which returns what I expect it to return except that it preserves the

Should this work? # --- remove any cronjobs that are not managed by puppet. resources { "cron": purge => true } I get the following error. Resources[cron]: Failed to generate additional resources: You must specify a title for objects of type Puppet::Type::Cron Ben

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

so I have this sudo module that I''ve been working on: class auth::sudo { package { sudo: ensure => installed } file { sudo_config: name => "/tmp/sudoers", owner => "root", group => "root", mode => 0440, notify => Exec["sudoers-syntax"], source => [

I''m almost afraid to ask because this probably sticks out like a sore thumb on the wiki somewhere, and I''m just not seeing it. But I have a bunch of files with the same owner/mode. Is there a way to somehow collapse these, so that all I repeat is the file name? Example: file { "/opt/test/1": owner => "jtan", group =>

Hi all, Today I came across something that I consider a bug. Would like to hear your opinions. Facts: - Using 0.22.1 from Debian Unstable on a Debian Testing machine - Recipes work on other machines The recipe in question is: # Keep home-dirs in sync file { "/home/tim": recurse => true, source =>

so here I am trying to track down why one of my execs isn''t working properly and I notice in the wiki[1]the option on_failure for logoutput. Turns out it does''t work (in 0.23.0) err: Parameter logoutput failed: Invalid ''logoutput'' value "on_failure". Valid values are true, false, debug, info, notice, warning, err, alert, emerg, crit. err: Could not