similar to: update from 0.22.4 to 0.23.x, not migrating database schema

Just wondering if anyone is using a backend database other than sqlite, and if so, how easy/hard it was to configure. I''m constantly receiving "SQLite3::BusyException: database is locked..." which I presume is due to sqlite''s relatively coarse locking method. Cheers, James -- Senior Linux Platform Engineer Midrange Services AXA Technology Services - Asia Pacific

I had a host that was exporting a resource to another host to trigger backups. The first host has now gone away, but the second host is still seeing the exported resource (because it still exists in the puppetmaster''s database). I fixed the problem by going in to the database and deleting all the rows I could find that related to the absent host, but I''m wondering if

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

Hi, I currently have a MySQL database containing all Puppet storeconfigs. My intention is to migrate to PuppetDB on a PostgreSQL server, so the first step is to use the ''storeconfigs'' face to export all the DB to a file PuppetDB can later consume. But the ''puppet storeconfigs export'' command always ends up being killed, I suspect due to some sort of OOM

Hello everybody. I have a question about removing exported resources. How is this done? Does it happen automagically? If I do: @@file{"/tmp/bla": content => "blahs content", ensure => present, } and thus export "/tmp/bla" to another host does it vanish by itself as soon as I remove the definition, or would I need to state something like:

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

hi,guys I''m test the resources export and collect , OS is Debian etch and sarge, puppet server and client version all of the 0.23.2 ; the db is MySQL-4.1 My test code is like this. node ''b'' { @@file {"/tmp/a": ensure => present ,content => "test"; } } node ''a'' { File <<||>> } I run puppetd on

Hello all. Probably this question has already been posed in the context of another software, but I am unable to find it. I would like to implement a module which should manage munin-clients as well as the munin-server. Here is what I am thinking about implementing: - There are two classes: munin::client and munin::server - munin::clients'' configuration will be managed automatically.

Hello all. I am using the munin module for a while now, I think that after the upgrade to puppet and puppetmaster 0.23.2 (or 0.23.1) it simply stopped working. Were there any changes to the realizing and exporting of resources? What could prevent this module from stopping to work. What happenes is that new hosts (munin::client nodes) do get stored in the database, but the munin::host does not

Hello all. There is some strange thing going on with our OS X clients. We have created a package which is run via SystemStarter. What it does? It parses /etc/fstab and mounts the NFS directories mentioned there. This is needed since we want to have static mounts and the NetInfo-automounter combination does not do static mounts (even with ttl=0 set for the mount, which is supposed to do a

Hi all, i'' m trying to configure puppet to use rails with postgresql. I'' m having troubles to make it work. Got no error when running puppetmasterd but nothing is being populated in the DB. Is anybody using puppet with postgres ? my config (in puppet.conf) [rails] dbadapter = postgresql dbname = mydb dbserver = localhost dbuser = user dbpassword = password

Hi there, I have a strange problem with the exported ressources in the munin module I wrote. See: http://mail.madstop.com/pipermail/puppet-users/2007-June/003179.html For some reason it stopped working. On the munin::host I get the error that: err: Could not retrieve configuration: Exported resource File[munin_def_XY_4949] cannot override local resource The munin::host is also a

Hello all, what exactly is the "design decision" that is needed here? We currently have the problem that 0.23.2-3 (debian package) does not work when it comes to collecting exported resources. The resources are saved in the database, so picking them up is the problem (db is Mysql5.x). This is a major problem for us, since we are using this a lot for our monitoring services. I

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

FYI: We have a custom `checkout'' type which stopped working when migrating from 0.22.4 to 0.23.2-ish. This turned out to have been caused by the location of property.rb changing between 0.22.4 (puppet/type/property.rb) and 0.23.2-ish (puppet/property.rb). (I say 0.23.2-is because I''m using 40491ebe7ca9692b57fb533412ece8fb694b7d4c since it only has a few extra bugfixes over

hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

I thought I''d put this out there for anyone to save anyone who''s running 0.22.4 on AMD64 hosts a whole world of hurt. Basically, the libshadow-ruby1.8 package that Puppet (as of 0.22.4) relies on is broken for AMD64 in both Debian (Sarge+) and Ubuntu (all releases). The problem is basically just some non-portable code. I''ve reported the bug into Debian with a patch, so

Hello dear list. First of all thanks to all the developers for the great work on puppet. After using it for a while, there is not better tool to manage a network! I have a problem with the $processor fact, which seems to be either not there or ignored at all. I try to implement package deployment for the Macs (Intel vs. PowerPC) as described here:

Hey all, I want to write a NFS module. Before I start, I thought I''d ask: Does someone already have such a module? May that person share it? What I want to do (have) is: - configure (different) exports on many NFS-Servers - configure NFS-Clients to mount some or all of those. Thanks, udo.

Hey all, i have attached a module which installs SSL-Root-certificates in Debian and Darwin. One thing is left to do for darwin: check whether the certificate is installed already. Until I have figured out how to do this, The test is rather simple. There is a class called dfncertificates defined in this module which gives you a hint how the module is used. Have fun, comments are welcome. udo.