similar to: New error in Centos 5.1

This is particularly nasty, since it''s on the puppetmaster itself: [root@puppet tmp]# rpm -q yum puppet puppet-server yum-3.0.5-1.el5.centos.5 puppet-0.24.0-2.el5 puppet-server-0.24.0-2.el5 [root@puppet tmp]# cat /etc/issue CentOS release 5 (Final) Here''s the output of puppetd --debug: notice: Starting catalog run debug: Loaded state in 0.01 seconds debug: Prefetching rpm

Hi Luke and other people working on 0.24. I hope this is constructive. So, I have our configuration working against a checkout from git as of last night. Subject to (sorry, here''s the big but :) * external_nodes script is not being called (#951) * Custom types aren''t working unless I drop them into $rubysitedir/puppet/{type,provider}. Previously they worked in

this time when I try to connect the first node: [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from

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

Sorry if this is obvious, but how can I have reports emailed to me- I want to know what each puppetd update is changing Thanks --e Eugene Ventimiglia Director of Systems GridApp Systems e: eventi@gridapp.com o: 646 452 4081 _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Hi working with the following puppet-0.24.1-1 puppet-server-0.24.1-1 ruby-1.8.1-7.EL3.8 rhel3 u8 The puppetmaster is running on rhel4 u5 I am working with puppet and rhel3 u8 and I have any an issue anytime I ask puppet to interact with yum for the record - yum from the cli works perfectly I setup a class to manage ntpd and in the class I have the following function # make sure ntpd is

I restarted puppetmasterd and it announced that the Cert does not match existing key ! [root@puppet ~]# puppetmasterd --verbose --no-daemonize info: Starting server for Puppet version 0.24.1 info: mount[files]: allowing 10.100.0.0/16 access info: mount[files]: allowing *.gridapp.com access info: mount[files]: allowing *.dev.gridapp.com access info: Retrieving existing certificate for

Hi, I have a number of puppets talking to 1 puppetmaster. Everything was working fine until suddenly this week the puppets are revolting. Whenever I try to run ''puppetd -v'' I see a lot of messages like: Certificates were not trusted: hostname was not match I''m sure I did not make any changes to DNS lately and I didn''t upgrade puppet on any of the machines

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

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

Hello all, I''m thinking about a configuration class that, amongst other things execs out to a ''dangerous'' configuration script. I''d like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: class blah { exec { danger: noop => true, tag => hitme, command

I''m thinking about how to set up the processes for Production puppet runs now. Being ultra-conservative here, we''d like to see what would happen before pressing the red button. I can run in noop mode, and everything is evaluated but nothing is done. A YAML report magically appears on the Puppetmaster which my script parses and spits out something the management can read

Hi. I''d like to use exception handling in my custom facts. For example, in plain Ruby: begin buildno = '''' bcrelease = open("/etc/BCrelease") while (line = bcrelease.gets) line = line.chomp buildno = $1 if line =~ /^Build:\s+(\d+)/ end bcrelease.close print "#{buildno}\n" rescue print "No

Hi, I was managing a bunch of Centos 4.5 with Puppet until the ruby security patch bit me creating ssl problems. As I''m not able/willing to patch the installed version I tried upgrading to dlutter''s 0.24.0-2.el5 version. Unfortunately this didn''t help much. So I removed the server and client installation completely (making sure to manually remove the config, ssl, ...

Hi all, i'' m trying to configure puppet to use rails with postgresql. I'' m having troubles to make it work. Got no error when running puppetmasterd but nothing is being populated in the DB. Is anybody using puppet with postgres ? my config (in puppet.conf) [rails] dbadapter = postgresql dbname = mydb dbserver = localhost dbuser = user dbpassword = password

Dear all I''ve gotten into the habit of including SVN headers in my templates, etc so it is easy to see where the file installed into /etc/puppet/ came from. Furthermore, we use svn cp to create release branches. Therefore, you''ll see something like this: # $Id: dumpadm.conf 1239 2007-10-23 16:04:06Z sa_dewha $ # $URL:

I just built new puppet rpm''s for Fedora (puppet-0.22.1-2) that fix the lockdir problem that many of you have encountered. The packages should show up on a mirror near you very soon. Unfortunately, I am having trouble getting to my buildsystem that I use for the RHEL versions of the RPM; I made the source rpm available on my people page[1] If you need the RPM for RHEL, you need to

Hi all, As promised, 0.24.1 is out. Here''s the changelog: Updated vim filetype detection. (#900 and #963) Default resources like schedules no longer conflict with managed resources. (#965) Removing the ability to disable http keep-alive, since it didn''t really work anyway and it should no longer be necessary. Refactored http keep-alive so

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

Fedora Core 7 has just updated their Ruby package (was 1.8.6.36-3.fc7, is now 1.8.6.110-3.fc7), and the upgrade broke my Puppet installation, and there was a similar report from someone else. Communications between the puppetmasterd and the puppetd running on the same host broke down with the message: Could not retrieve configuration: Certificates were not trusted: hostname not match with