similar to: external nodes

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 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

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 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

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 =>

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

So before I start I should be upfront and disclose that I''m using external_nodes, so in keeping with that I''m trying as hard as possible to keep all the actually ''specific'' data in the node config files (currently just yaml)and have nothing specific in modules especially. So I have this definition: (credit goes to DavidS for the inspiration) define git::repo (

Hi all, I''m struggling with the following: I have a defined type wrapped in a class: class myclass { define mytype(bla) { file { "blabla": .... } exec { "blablabla": ... } } } And I access the defined type in my other class by doing this: class otherclass { include myclass myclass::mytype { "alb": ... } # and here I want to

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir

Hi all, I''ve noticed, that once using storeconfig, if the db (in my case mysql) is down than puppet wont start... is there a real reason for making puppet depend on the db? Thanks, Ohad _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

I have a cluster of 20 or so machines. On many of the nodes, the puppetd process take up a ton of resident memory (> 400MB RES in top, > 500GB VIRT in top) after running for a while (> 1 week). The only thread I found on this was titled "memory leak?" and last updated on 06-Dec-2007. The question on that tread was whether or not the memory was buffered memory. I

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

Hi, I''ve been using puppet for about a week and a half now, and it''s definitely making my life a lot easier. I''m using 0.24.1 and I''ve run into a small snag. I''m trying to write some code to make sure user home directories exist for users in LDAP. I''m trying to get their uid, gid and home directory from getent with something like: $uid =

Hi all, I attempted to add an EL5.1 client to our puppet server (EL5), and after signing the client cert, got the error "Certificates were not trusted: hostname not match with the server certificate" I found the mailing list discussion and the relevant page: http://www.reductivelabs.com/trac/puppet/wiki/RubySSL-2007-006 As far as I can tell, my puppermaster''s cert CN matches

Would it be possible to... ( I suppose that this is an enhancement request )... automatically do the following on a client-side manifest failure: 1. Wipe localconfig.yaml and state.yaml and try again (seems to fix most things for me) 2. Revert to a last known good configuration if all else fails. Thanks, Trevor _______________________________________________ Puppet-users mailing list

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 => [

Hello, I was wondering if there is a way to parse individual manifest files as part of a pre-commit hook in subversion. I am looking for something like puppetmasterd --parseonly, but that will work on individual files. This way I can reject a commit if it does not pass. Any ideas? TIA

Hello folks, Im trying to migrate from static nodes-definition to external nodes definition. My script looks like this stolen from http://reductivelabs.com/trac/puppet/wiki/ExternalNodes: {{{ #!/usr/bin/perl -w use warnings; use YAML qw( Dump ); use Switch; #initialize vars our @classes; our %parameters; Function to fill @classes and %parameters with correct values .... print Dump( {

I''m using the external_nodes functionality to read in a flat file of a node''s configuration. Currently said file is a straight yaml file (just to keep things simple). The place I''m currently stuck is in doing some more advance node configurations and placing that data in the yaml file. For example: node ''foo'' { $var1 =

Hi, I wanted to configure reporting in puppet. I came across the below links which says what needs to be added in config file to enable reports. But I was wondering how I view the visual report/graphs do I need to create my own script. http://reductivelabs.com/trac/puppet/wiki/ReportReference#rrdgraph http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting -- Deepak