similar to: Can I run puppetmasterd behind NAT (or Reverse Proxy)

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

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:

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

I apologized ahead of time if this post shouldn''t go here but I having been knocking my heading for the last two days trying to get over the following error while trying to "clone" my primary puppetmasterd because we have outgrown one puppetmasterd setup. I have basically set up a 2nd instance of our primary puppetmasterd and rsync''ed over /var/lib/puppet/ssl/ from the

Hello, puppetmasterd is running as shown here: puppet 10209 1.1 1.5 138124 62532 ? Ssl 13:37 0:06 /usr/bin/ruby /usr/sbin/puppetmasterd --manifest=/etc/puppet.production/manifests/site.pp --logdest=/var/log/puppet.production/puppetmasterd.log however, the log file is not being updated with information when a client runs puppetd --test Am I missing something obvious? Best,

Hi, We have dedicated puppet master boxes, which basically only run a mongrel/puppetmasterd (6 instances), an apache proxy for mongrel and puppetd. Recently puppetmasterds seemed to have leaked almost all of the RAM, and the thrashing made the box painfully slow. We restarted the puppetmasterd processes, and started collecting some statistics. Attached is a graph of memory usage on one of the

Hey All, Id like to submit two init scripts for debian for puppetd and puppetmasterd, Which is the best to do this? Cheers B _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Hi everyone, I am in the process of evaluating Puppet (version 0.23.0 - Solaris 10 sparc), so I am still a newbie. First tests with Puppet were fine since it was running with the default configuration. Now, I have created a "puppet.conf" file ( puppetmasterd --genconfig > puppet.conf ) to customize some of the configuration parameters. When "puppet.conf" is present,

I am confused about all the database talk on the list lately. I''ve been playing with Puppet for the last 6 months and have never set up a DB for it to use. What are you guys using the DB for? My first though (really the only thing I could find) was for storing node configurations. But I''m storing them in the file system and it seem to work just fine. What are the advantages

So, I have a server at home that has four VMs running inside it. All are managed via puppet. The physical host runs puppetmasterd. I don''t recall noticing this before, but puppetmasterd has decided to be kind of crazy. Here''s the physical host with no puppetmasterd running: top - 11:36:15 up 271 days, 15:16, 1 user, load average: 5.68, 5.50, 6.45 Tasks: 129 total, 1

Hello All, Ticket #30 (http://mongrel.rubyforge.org/ticket/30) has a set of changes to mongrel that I''ve written on behalf of my employer, Raritan Computer, Inc. Also, these changes are released under the existing Ruby license used for Mongrel. Raritan is using mongrel internally for product development and was not able to get the level of scalability desired due to limitations

I posted this earlier on IRC, but it didn''t seem anyone was active: <mozillaman>Hey all! <mozillaman>Quick question for you :) <mozillaman>I installed puppet according to the directions on the site and got this: sudo /usr/bin/puppetmasterd --nonodes undefined method `retrieve'' for nil:NilClass <mozillaman>Anyone have any ideas? Any help would be

Hi, Is there a way to have puppetmaster sign new clients'' certificates when using apache+mongrel for serving, without having a separate puppetmaster instance running webrick on a different port/IP? I guess this does not work out of the box because apache is told to do the verification very early in the connection process, at which point it does not yet know that the client is going to

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

Is there a way of specifying the server on a different port? I want to be able to change between two different puppetmasterd''s on the same box, and I want to pick between them by using selecting the port. There seems to be lots of :port* symbols floating around, and a --port in puppetd, but it''s not looking consistent. Is this something on the TODO path, or is there a

Moving to mongrel as our footprint has grown considerably. Configs worked fine before but for some reason we are unable to start puppet on the new host. Any help would be greatly appreciated. -jeff Centos 5 # ruby -v ruby 1.8.5 (2006-08-25) [i386-linux] # gem list mongrel *** LOCAL GEMS *** mongrel (1.0.1) A small fast HTTP library and server that runs Rails, Camping, Nitro and

I''m trying to run puppetmasterd the first time with --mkusers. It fails with the following error message: 001 # /usr/bin/puppetmasterd --mkusers Could not configure for running; got 1 failure(s) Adding --verbose and --debug does nothing to improve the output. How do I begin to debug this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

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:

Anyone ever migrated the puppetca to a different host? What are the steps that are involved?