similar to: Monitoring the puppetmaster

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

Hi, I''m currently trying to debug a performance issue I''m having. Therefore I would need "DEBUG" output. When using one puppetmaster process, this is fairly easy by starting it like this: > puppet master --no-daemonize --debug Now I need to see this debug output when running puppetmaster the way I ususally do - using Apache/Rack/Passenger. After looking

Dear experts, Since I''ve moved my *puppetmaster* form SL5 (Scientific Linux) to SL6 with SELinux on, I''m facing loads of trouble. I also move away from WEBrick to apache/passenger, following the instruction here: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > and I can''t start httpd any more. It fails with this: Starting httpd: (98)Address

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Hi, I have been getting the below error for sometime now. Both master and client are using version 0.24.8. Output from /var/log/messages err: Could not call puppetmaster.getconfig: #<#<Class:0xb7b50a9c>: execution expired> err: Could not retrieve catalog: execution expired P.S- all of this was working absolutely fine and suddenly has started to misbehave. Regards, -- You

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

Hi! I''m testing Puppet 2.6 and got all the basic stuff working with the default webricks. I read that it doesn''t scale very well and is not suited for production environments and the recommended setup is Apache/ Passenger. Is there a step-by-step-guide on how to set it up? Any help is very appreciated. Regards, Freddie -- You received this message because you are subscribed

I''m unable to get a response from the puppetmaster I''m testing with. `netstat -apn` shows puppetmaster/ruby listening on port 8140, but telnet connections are refused both from a different location and from the commandline on the master server. I''ve restarted a number of times but I''m still getting nothing, and AFAICT there aren''t any conflicting

Hi all, I''m currently getting a lot of update failures showing up with no logs in the dashboard. This happens for about half of our 28 nodes, about once an hour. When re-run half an hour later, everything seems fine. Through a combination of server restarts and our Puppet master locking up entirely yesterday, almost all of our nodes are now trying to do their half hourly update at

Hello, I really didn''t expect this to be difficult, but I''ve been struggling with this all day :( I''m running CentOS 5.3, with rubygems, rack and fastthread, from EPEL. I''m running puppet-0.25.0-1 built from the spec file in the latest stable tarball. I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen (kanarip), which is effectively EPEL

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

Hi, I''m currently trying to get my puppetmaster work in passenger, but have not succeeded so far. Passenger itself seems to work (a small "hello world" app runs fine), but when I point a puppet client (0.24.8) to it, I get: info: Retrieving plugins err: Could not call fileserver.list: #<RuntimeError: HTTP-Error: 500 Internal Server Error> err:

After an unexpected and unreasonably long hiatus, I''ve finally returned to implementing Puppet in my environment. My puppetmaster: Puppet 0.25.4, Facter 1.5.7, Ruby 1.8.7, and FreeBSD 8.0. I''ve got five clients using the puppetmaster so far. After about 24 hours, I''ve got three puppetmaster processes running. This number continues to grow over time. If stored configs

I am working on setting up a Puppet configuration where some of the data is stored on a DRBD volume. The modules and vardir are stored on the drbd volume. The puppet.conf files point to the drbd volume for vardir. I created a cert for a VIP puppet-master using the puppetca -- create command I had everything working on the primary drbd node, but when I fail over, everything starts up fine, but I

I noticed a behaviour which is kind of confusing. I have the puppetmasterd running. Now I want a new client to connect. I edit the site.pp and add the client. When the client is started I can see it with puppetca --list. So I sign the client. When it next tries to connect it shows: notice: Allowing ::ffff:192.168.x.y(::ffff:192.168.x.y) untrusted access to CA methods notice: Host

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

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

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

hi, i''m trying to set up my puppetmaster infrastructure with multiple puppetservers behind load balancers in each of our datacenters. i''m using 0.24.6. i''ve read the howto on puppet scalability, and i think i''ve got the ssl config working correct, but i''m noticing that when puppetd is used to build a puppetmaster, some of the files in $vardir/ ssl

Can anyone who''s having this problem please send details? I''m trying to reproduce it -- I''ve got 5 clients concurrently retrieving 200 10k files made of random binary, and I can''t get any corruption or memory growth at all. Is everyone experiencing the problem using Mongrel? Webrick? What versions of ruby? Are only big files affected? Small files?