similar to: resource collection error

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

Here''s some happy-fun Perl to make your storeconfig/virtual resources day better. I probably should have written this in Ruby, but perl comes naturally :) #!/usr/bin/perl # # Perl DBI to remove all related entries from Puppet''s storeconfigs database. # Use when a host is removed from the Puppet network forcibly # Alternatives: run puppet on host to be removed with a blank

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

Hello, I just installed the latest version of puppet and puppetmaster on an up to date RHEL4 system. If I turn on ''storeconfigs'' on the puppetmaster server I get the following error: debug: Calling puppetmaster.getconfigerr: Could not retrieve configuration: Uncaught exception No such file to load -- sqlite3 in method puppetmaster.getconfig I have gems and rails installed

Hello, When I kick off SVN1992 with storeconfigs=yes, I get the following error: err: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: INSERT INTO resources ("exported", "line", "title", "host_id", "restype", "source_file_id") VALUES(NULL, 23, ''svnpkgadd-emacs-nox-etc'', NULL, NULL,

Hi all, we had notified that table ''fact_values'' of puppetmaster database is not updating when a fact value changes (for example we have updated some puppet clients version to 0.23 and fact_value of database is still the old version 0.22.4) it is a bug? misconfiguration? we are using ''storeconfigs = true'' with MySQL backend we''ve tried to restart

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

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 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''ve been thinking about how to make Puppet a killer app, and I think there is one specific thing that could be done to help make that happen: People using Puppet now to consistently state what they *really* wish Puppet could do for them -- the recent thread around Puppet on Windows is in that vein, but it''s not specific enough. For example, I''d like to know what

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

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

Hello, I''m having some trouble getting stored configs to work properly with SQLite. During each run, the puppet master is reporting the following error: err: Could not store configs: SQLite3::SQLException: fact_values.value may not be NULL: INSERT INTO fact_values ("updated_at",3 18:41:56'', NULL, 3, 18) I''m using Puppet 0.24.4 with Rails 1.2.6 and SQLite

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, I think I''m having a similar problem to the user who raised this bug: http://reductivelabs.com/trac/puppet/ticket/733 I''m running 0.23.2 with storeconfigs. I''ve got it working to the point where my clients'' facts are being populated in the database[*] but updates don''t seem to happen unless I restart puppetmasterd. For example: 1) I run my test

Hi, I''m upgrading from 23.2 to the latest and have "dbmigrate = true" in my config. When I try to run puppetd, I''m getting: Could not migrate database: SQLite3::SQLException: no such table: schema_info: SELECT version FROM schema_info I''m perfectly blowing away my old db (by deleting /var/lib/puppet/ state/clientconfigs.sqlite3 ?), but I haven''t