similar to: puppetd dies?

Anybody else experience the need to restart puppetmasterd before a node can register itself. I''ve been cleaning up my installation here on client nodes and every once and a while I find myself needing to restart the puppetmaster daemon. A client node attempts to connect and never does. A restart fixes things. There doesn''t seem to be anything useful in the error messages

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 see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

I think that I''m running into the warning on external node support here but after a recent upgrade for my puppetmaster I get: puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names aa0-006-4.foo.com, aa0-006-4 I''ve not changed puppetd.conf which contains: ldapnodes = true ldapserver = my.ldap.foo.com ldapbase = ou=hosts,dc=foo,dc=com I''ve not

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

hi,all I want set up a puppet HA structure. but if the puppetd can set more than one server address ,the work will be simple :D if one puppetmaster have error, the client can auto try the next. I think I can use the heartbeat or dns to do this same thing,but not so good. so I want know the puppetd can direct set in the configure file ? if not,will be add this option? -- Huang

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

With both puppet-0.23.0 and 0.23.1 if I setup just the configuration file puppet.conf, none of the puppetd options seem to get parsed. I first noticed this when monit failed to start/stop services due to the lack of a pid file being generated (and mine is not in one of the usual places). I''m sure that something like the patch attached but I bet it breaks other assumptions :-) Cheers,

I am attempting to move our test puppet installation from looking for node information in a manifest to LDAP. I followed the instructions at: https://reductivelabs.com/trac/puppet/wiki/LdapNodes and was able to get the puppet schema loaded into our LDAP. I can now query LDAP and modify/load data without any issues using the OpenLDAP tools. e.g. ldapsearch -h ldapdev1.domain.com -x

I''m having problems with a definition not being found. I get the following error when running puppetd -vt: err: Could not find type "manual_apt_get_update" in file /etc/puppet/manifests/definitions/apt_misc.pp at line 22 The definition is present for sure. Can anyone spot a problem with the code below? define manual_apt_get_update { exec { "/usr/bin/apt-get

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:

I have this configuration: class monit { # Installing packages. package { "monit": ensure => latest; } file { "/etc/default/monit": owner => "root", group => "root", mode => "0644", source => "puppet:///monit/etc/default/monit", } file { "/etc/monit/monitrc": owner => "root", group =>

I turned on reporting the other day and I''m seeing alot of these when puppet runs. Especially during times when nothing is going on (middle of the night etc) Tue Dec 11 12:34:48 -0500 2007 //base/puppet/puppet::client/Service[puppet]/ensure (notice): ensure changed ''stopped'' to ''running'' It''s also quite odd that puppet when it runs it thinks

Has anyone done rollbacks with puppet? The story goes that last night I pushed a change out, which intentionally changed the way certain services where managed. The change involved pushing out a few files, cronjobs, etc., which was okay until it was discovered there was a bug with the service. My configurations are kept in subversion and rolling back to a previous configuration would have

I made an attempt to switch to mongrel today and I''m running into a strange error message I can''t seem to track down: debug: puppetmaster: Setting servertype to ''mongrel'' Server is not a class Tracing through with the debugger shows: [snip] /foo/lib/gems/puppet-0.22.4/bin/puppetmasterd:248: case Puppet[:servertype] (rdb:1) n

All, Once the puppet clients are installed, is there a option to list the client in the server. mind you I never meant the cert - signing list.. which would be puppetca --list. Thanks for your help -Rajeshwaran -- He also serves Who only stands and waits.... _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

Hi all, I''ve got a new class in the current code, which I''ve been calling Configuration but Matt reasonably thinks is horrible. He is recommending the name Manifest, and I figured I''d see what others thought. The point of the class is to function as a resource container -- it keeps a reference to all of the resources we''re managing, and knows how to

Might there be anything CentOS related on why I cannot access the Monit GUI system on http://box-running-monit.com:2812 ? I am using a very basic /etc/monit.conf config, but I cannot get it serve the web page on my box The service start and stops fine (e.g. "/etc/init.d/monit start"), and I have it set to listen to port 2812 in the "/etc/monit.conf file" (so far, kept the

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

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel