similar to: Switching from webrick to mongrel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''m running the latest version of puppet (debian 0.22.4-2), and I''ve gotten to a point with my configuration where puppetmasterd needs to be restarted every few days due to what seem like file handles not getting closed. I either see this set of errors: May 22 08:08:34 localhost puppetd[2810]: Could not get config; using

Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It

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"]; }

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''ve been trying out some configurations and been frustrated because they weren''t working how I would expect. After trying practically everything I could think of, I tried removing everything except the most basic elements to see what was going on. It turns out that my client is thinking that there is no configuration change, when

Can anyone help me with this error I am having. I am using puppet on Debian Etch, version 0.20.1-1 from apt works OK, but due to one or two problems we want to use the version from testing, 0.23.2-10, but the puppetd just fails upon startup spitting this out: Starting puppet configuration management tool/usr/lib/ruby/1.8/timeout.rb:54:in `open'': execution expired (Timeout::Error)

Hello, I have 680 hosts reporting into a central puppet server. Yesterday I made a change to site.pp and the nodes/foo.pp and nodes/ bar.pp files to push out some new files (a script to enable LDAP) and it seems that only a handful of stores have downloaded the file and run the script. (I don''t have reporting setup yet other than on a few clients which I did manually) If I ssh into a

Hello... What is the last version of puppet that will work with ruby version 1.6.8? I have a few RHEL 3 machines I would like to run puppetd (only the client, not puppetmaster). They will be updated to RHEL 5 fairly soon, so I don''t want to spend a lot of time trying to get a more recent version of ruby on them. thanks /me buys Luke a beer for all his help :) I now have

We haven''t been able to use mongrel for testing yet, but in order not to waste time, we did some performance testing with 1, 2 and 4 puppetmasterd/webrick processes. Attached is an HTML page (ripped from our wiki - not pretty, but reasonably readable) which describes the method and results. If someone feels like making some nice graphs, that would be great. If not, I''ll try to

I am having a difficult time understanding and determining which module method is best for the env I help to support. Overview of systems supported: -There are 17+ clients. -4+ envs (dev, stage, beta, prod ..) per client -Several flavors and versions of OS ( Mostly fedora and centos ) -All are apache, some mongrel and most passenger -code deployments are capistrano -configurations are done with

Hi, suppose puppet-old.domain is a CNAME pointing to puppet-new.domain, and puppet-new.domain is running Apache (for SSL) with mod_proxy_balancer to balance over some 10 puppetmaster processes. The configured SSLCertificateFile in Apache is that of puppet-new.domain How do I get a node to stop complaining when connecting to puppet-old.domain (ending up at puppet-new.domain through the CNAME)?

Hi all, I''m trying to set up puppet 0.24.5 using the packages provided for Mandriva 2009.0. After installing the packages and starting the puppetmaster service for the first time, the relevant CA certificates and keys are generated automatically and placed in subdirectories of $ssldir. However, when I then run puppetd on the same machine thus: $ puppetd --server myhost.mydomain

Hello, I randomly errors like this: Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog from remote server: end of file reached Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (notice): Using cached catalog Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog; skipping run Here are the versions: puppetmaster

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

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

Hi, On my puppet node, there are many facter variables that are empty in my manifests. But, there are not empty when I start "facter" on the node. why ? ex in a module: class resolver { if $::ipaddress6 { ... } $domainename = "$domain" } In this manifest, $domain and $ipaddress6 are empty In the facter command line, there not empty. -- You received this

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:

Hi, I''m starting to move over to Modules, which looks pretty clean and solid. Reading http://reductivelabs.com/trac/puppet/wiki/ModuleOrganisation, one thing that confuses me is how the client resolves the implicit file server resources. I''ve got a few different puppet master servers running on different ports, and my configuration re-defines $puppet_master_host and

Hi, https://reductivelabs.com/trac/puppet/wiki/DocumentationStart https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction https://reductivelabs.com/trac/puppet/wiki/PuppetMasters https://reductivelabs.com/trac/puppet/wiki/PuppetBestPractice - Max

Hello all, I am running puppet 2.7.1 with mongrel and an apache proxy. I have been seeing an issue where it appears that the puppetmaster is completely ignoring any facts that are sent to it. When a client connects, any configuration that relies on facts shows those variables as being empty strings. (I have been testing this with a simple notify resource that prints out the IP address and the

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,