similar to: logoutput attribute on exec type

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''m working on a definition for activating/deactivating Apache modules on an Ubuntu system. Inside my Apache class I have this definition: define module($ensure) { case $ensure { enabled: { exec { "a2enmod": command => "/usr/sbin/a2enmod $name", logoutput => on_failure,

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/

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

I''m working on a module to handle creating and populating Python virtualenvs. Without going into too much detail, basically these are nicely-encapsulated environments into which python packages can be installed and run. It''s not uncommon to have several virtualenvs on a system, potentially with the same packages installed (maybe different versions). Puppet''s defines

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 have the following exec in my manifest : exec { some_exec: path => [ "/bin","/usr/bin","/usr/local/bin" ], command => "EXECUTE COMMAND 1", onlyif => "EXECUTE COMMAND 2", logoutput => "on_failure" } I want that the "COMMAND 1" should be executed by "USER 1" and "COMMAND 2"

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

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

Not sure if this is another issue cropping up with 0.24.1 but I''m getting the following: info: Loading fact raid /etc/puppet/facts/location.rb:5: private method `split'' called for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call'' from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value'' from

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 (

Here''s the problem I''m trying to solve. I use apache, for lots of things, some of those things are configured from a performance standpoint differently. In less vague terms I need to be able to change the MaxClients setting to different things based on the different purposes apache serves. (say proxy vs. app) Under previous CMS/templating engines I would have a httpd.conf that

Hi, I want to audit some files on content and planned to do this with puppet filebucket. Lets say for example that I have a list of audit_files as a parameter from puppet dashboard with a list of files to audit. Output from ENC for this particular parameter: audit_files: "[\"/etc/passwd\",\"/etc/resolv.conf\", \"/tmp/mawi\",

I don''t manage any macosx machines but I do run puppet standalone to check syntax etc. I''ve been getting the following error: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb": superclass mismatch for class ResourceOverride specifically small test pp files still work, though I''ve found when I use parseonly it

Hi All, I was wondering if it is possible to NOT show an event in puppet dashboard. I have an exec resource that fires of a ruby script. This is triggering a changed event on every run, but actually I want to exclude this from showing up as "CHANGED" Is this possible, if so how can I achieve this? --- myscript: --- exec { "run_myscript" : #

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

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 =