similar to:

Hi all, I''ve followed http://reductivelabs.com/trac/puppet/wiki/UsingMongrel for configuring my puppet with mongrel. Al seems to work fine, except that, after a reinstall of 40 nodes atone time, I got many kind of errors like: ------------------------------------------------------------------------- err: Could not request certificate: Certificate retrieval failed: .tmp file already

I am trying to setup Puppet + Mongrel on RHEL5. So far I have followed this document: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel_On_Enterprise_Linux The puppetmasters all start up and Apache starts up on 8140. However, when my client connects I get the following errors: [root@lv1764p puppet]# puppetd --server puppetdev.encana.com --no- daemonize -o -v info: Retrieving

Hi all, My current conf splits 188 clients execution in one hour, and puppet runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is

Hello list. I''ve (hopefully) gotten nginx and mongrel up and running, and copied the startup script found on http://reductivelabs.com/trac/puppet/wiki/UsingMongrelPound to enable starting puppetmaster by issuing "mongrel_puppetmaster 18140". This makes sure that mongrel i started. But how do I make sure nginx is automatically started? As of now I manually issue the

Hi, We''re trying to follow the instructions at http://reductivelabs.com/trac/puppet/wiki/UsingMongrel (Just using a single puppetmaster/mongrel instance and plain mod_proxy for now, instead of balancer one) We got past the "Server is not a class" error by modifying mongrel.rb We also kind-of got past the: /opt/bin/puppetmasterd:293: undefined method `daemonize'' for

Hi I am reading and configuring puppet in relation to http://reductivelabs.com/trac/puppet/wiki/UsingMongrelOnEnterpriseLinux The question I have is in relation to the ssl certificates generated the first time the puppetmaster service is run and the ability to use a CNAME. If the host that i am running the puppetmaster on is server.example.com and i want to use puppet.example.com as a CNAME that

I tried to install the ''mongrel'' gem tonight via puppet in an attempt to migrate from webrick to mongrel as described on the puppet site[1]. I added the following to my manifest: package { "rubygems": ensure => installed; "mongrel": ensure => installed, provider => gem, require => Package["rubygems"]; }

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

The problem was solved when we moved to an Apache+mongrel setup from the initial webrick setup. Seems that webrick doens''t handle the SSL certs correctly enough to get this type of setup working. .r'' 2008/6/3 RijilV <rijilv@gmail.com>: > hey all, trying to get SSL cert deligation working based on > http://reductivelabs.com/trac/puppet/wiki/PuppetScalability.

So I''m still working on a ''perfect'' setup so I can document it on the wiki, and will submit some puppet patches against 0.23.2 next week, but here''s what I''ve done that has made a big difference to stability here. in puppetmasterd at line 261, I''ve modified the Mongrel instantiation from: server = Mongrel::HttpServer.new(addr,

Hi, I have just successfully configured Puppet to run with Mongrel, and would like to update the documentation with what I''ve learned. However, since I''m not an expert with these things, I thought I''d share with the list before updating the wiki. So here''s what I''d change: + Remove this picture:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

I have a test area network that is not routed to the production network because of IP address space re-use between the two networks. I would like the puppetmaster to serve both the production and test area networks. The puppetmaster is on the production network. I understand the puppet to puppetmaster connect to be HTTP using SSL. Can I somehow setup the puppet clients to use an HTTP

Hello... I am trying to switch to mongrel from webrick to get rid of the . puppetmaster is FreeBSD 6.2 with ruby, puppet, and mongrel all from ports (latest as of this morning). I get "Server is not a class". --verbose, --debug do not spit out any useful info. puppet-0.22.4 ruby-1.8.6.111_1,1 ruby18-bdb46-0.6.2 ruby18-gems-0.9.4 rubygem-daemons-1.0.8 rubygem-fastthread-1.0

Hi I have created a module for djbdns [1], which will generate the data file (dns entries) from defines in puppet classes. This is all fine and working. :) However I autogenerated after a few tests the classes for the domains from the current source of our domains. Which are about 50 classes each calling around 3 defines, which will be concatenated_file calls (from davids common module), which

Hello, In the wiki "Using_Mongrel" http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel it proposes a configuration with the option: SSLVerifyClient require But with this option set I am not able to register new clients. When I run a new puppet client, I get the error: warning: peer certificate won''t be verified in this SSL session err: Could not request

Hi folks, When running puppetd --environment whatever, the environment is not taken into account on the puppetmaster. This bug appeared after ticket #1130 got resolved and is certainly due to caching of the node terminus. Looking through the code didn''t help me understand how this yaml cache should get refreshed. On the puppetmaster, the cache files located in

Hey All, This is probably a gotcha of some kind. That is to say I''ve missed a configuration somewhere. I''ve recently moved over to using mongrel as the puppet server type and having nginx proxy to one of four mongrel instances. What I''m seeing though is that when I try to run a new node (one that has been created post moving to mongrel/nginx) is that it returns with the

I went through all the ''getting started'' stuff, and have a puppetmaster and several test clients configured. I''m not clear as to how the puppetmaster manages the puppet configurations on the clients ... while it would obviously be possible to add puppet.conf as a distributed file, I''m guessing there''s probably a better way to manage this sort

Hey Guys, So i have puppetmaster running and well. I have a few questions 1) Even though i followed instructions on http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel on using Mongrel, puppetmaster is probably still using webrick since the client connection timeout still occurs. How do i make it use mongrel? 2) Now after messing a little with /etc/sysconfig/puppetmaster i increased