similar to: Storeconfigs

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

Hi What does this error-message mean, and how do I preceed? err: Could not store configs: You cannot call create unless the parent is saved Magnar _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Hi all, I currently am using puppet with storeconfigs and am quite happy with the results. I also see that there is now the option of having async_storeconfigs. What I''m wondering about is the following: 1. What benefit is there to running async_storeconfigs over storeconfigs? 2. In what scenario''s would async provide a benefit to standard storeconfigs? 3. What are the typical

Hi all, As I understand it, storeconfigs needs to be enabled on both the agent and the master to function ideally. I have a couple of questions: -> Can the various agents and the master safely share the same storeconfigs db (say, a postgresql server)? Is there any benefit to setting things up this way? -> Is there any benefit for an _agent_ to use an RDBMS vs sqlite for its

I''m doing some testing with the puppetlabs/haproxy module on a vagrant box with puppet 3 set up. The module we use requires exported resources to be enabled in order to specify haproxy backends, but I don''t have it configured in puppet. I have our puppet repo checked out to the VM and am using puppet apply, pointed at the specific module path we use for development, to

I have a working configuration using external nodes, but when I enable storeconfigs using either Sqlite or MySQL, nodes no longer get assigned their classes from the external nodes script. I''m currently using the 0.25.4-2ubuntu6 packages from Ubuntu 10.4. Disabling storeconfigs and restarting puppetmaster causes nodes to be assigned classes from the external nodes script. I''ve

# cat /etc/redhat-release CentOS release 6.4 (Final) # puppet --version 3.2.3 # rpm -q puppetdb puppetdb-1.3.2-1.el6.noarch I am now receiving "Not collecting exported resources without storeconfigs" for my opsview module. It was working fine on puppet 2.7 with Activerecord/MySQL. I am still new to puppetdb so maybe I am missing something. This is from puppet.conf: storeconfigs

Recently I started noticing that after running for a while puppetmaster would freeze after a client called `freshness` which would eventually result in the client getting a timeout and the client dyeing. I tracked the freeze down to the call to ActiveRecord::Base.verify_active_connections! in rails.rb on line 26. After scouring the nets I finally found:

I''m adding tables to the storeconfigs database, to support my storereports plugin, and would like some guidance on handling the schema version. First prize would see my database extensions applied as migrations. But then ActiveRecord would want to bump the schema version. Any ideas on how to handle this gracefully so that I don''t confuse the hell out of puppet itself, on

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

I''m re-posting this because I''m not sure that it got through the first time. If someone could at least echo back that this is reaching the list, I''d appreciate it. (I''m new to the list.) Sometimes (with variable frequency) storeconfigs stores the wrong data in the fact_values table. This has the end result that exported resources, when collected, have

I can''t seem to find a sane way of running storeconfigs on the new AWS server environment I''m working on. - SQLite is not an option. It becomes unusable far too quickly. - Using a mysql adapter doesn''t seem to work properly. - I quickly run into bug #9290<http://projects.puppetlabs.com/issues/9290>again and again. Which after 2 years STILL

Hello all, I have what is certainly a stupid problem on my part. I have setup puppet in a test environment and it''s been working wonderfully. I am now in the process of moving this to our production systems and I have rebuilt our puppetmaster completely from scratch using the same modules/manifests, etc. from my test system. Unfortunately I am running into an issue with what I

Hi Guys, Im trying to turn on storeconfigs with a mysql db backend. On my testing server in our lab, i configured this successfully and can see if keeping information on all test hosts. When trying to implent the same idea onto our production puppet server, I get the following errors: Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/

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

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

I''ve been pondering how to handle our file distribution issues - we''re starting to roll puppet out, and I''d like to get it somewhat right from the start. I''ve been watching the list for a while, and observed ''complaints'' about the speed of the fileserver method when dealing with recursive directories. If I can avoid this, I''d

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

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my