similar to: storeconfigs seems to disable external nodes

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

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

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 all, hoping someone may have encountered a problem similar to this before: On my customer''s EC2 based infrastructure, we have implemented the nodeless, truth driven module outlined by Jordan Sissel here http://www.semicomplete.com/blog/geekery/puppet-nodeless-configuration. It''s quite an effective model, especially in the realm of EC2... we still have a puppetmaster

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/

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

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:

Hi all, I''m using the version 0.24.1 with strange problem: When I enable storeconfigs in puppetmaster (puppet.conf) I have the following error on clients debug: Finishing transaction -604715208 with 0 changes info: Loading fact hardware_platform info: Loading fact dmi debug: Retrieved facts in 2.12 seconds debug: Calling puppetmaster.freshness *err: Could not retrieve configuration:

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

Dear All, I know puppetDB its more faster than storeconfigs, but to replace storeconfigs with puppetDB into production server Its need more explanation than some link from puppetlabs, need prove to my bos and team. For testing i just have 1 puppetmaster and 1 and 2 puppet agent, how i can look different performance? Its that any idea / or complex puppet stanza to benchmark / compare this with

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

Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually

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

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

Hello, Anyone have any luck getting storeconfigs + MySQL working? I was getting some freaky uninformative errors: err: Could not call: wrong number of arguments (1 for 0) It''d be great if we could get a wiki page up, there appears to be a pretty large consensus of people who are unable to get it running. Regards, AJ

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, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

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 have updated the 1100 clients that prior to the update used to connect to the master just fine. Now after about 30 minutes of running, puppetmasterd starts to complain "puppetmasterd[6875]: Too many connections", and from that point forward will stop compiling catalogs. Puppetmaster is configured using the Mongrel Apache configuration as described here: