similar to: Obtaining puppet and facter for RHEL5/Centos5

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.24.8 is now available! This is a maintenance release for the 0.24.x branch but contains a small number of new features including some significant performance enhancements for large installations and stored configurations. The tarball is available at: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz MD5 hash:

Having just spent about 2 hours trying to work out how to add a password --md5 $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1 line to my grub.conf I thought it would be worth sharing how I finally got it to work. augeas {"/boot/grub/grub.conf": context => "/files/boot/grub/grub.conf", changes => [ "set timeout 15",

For 40 days and 40 nights Facter wandered in the wilderness sustained only by the occasional patch and bottle of Kool-Aid. Slightly less tanned and equally happy Facter 1.5.8 has arrived! 1.5.8 is a feature and maintenance release containing a number of fixes, updates and additional tests. You can get the release at: http://reductivelabs.com/downloads/facter/facter-1.5.8.tar.gz Please log any

I''ve tried this over and over, and I just cannot get it to work. I''m trying to do a proof of concept on puppet, so I''m using two CentOS 5.3 systems running in VMs on separate hardware (i.e. the two VMs are not on the same physical box). I''ve built the systems from scratch numerous times, and then pulled down puppet from the rpmforge repo. In the course of

I am trying to get puppet to manage my LDAP users but I don''t appear to be having much success. What I have in puppet.conf is this [puppetmasterd] ldapserver=ldap.myorg.company.com ldapbase=dc=myorg,dc=org ldapuser=cn=admin,dc=myorg,dc=org ldappassword=mysecret ldapparentattr=dc=myorg,dc=org I added the ldapparentattr in desperation and doubt if

Hi, When you set managehome to false on a User ressource, homedir will still be created on a CentOS box as the -M flag is not passed to useradd. $ diff -u /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ useradd.rb.bak \ /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/useradd.rb --- /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ useradd.rb.bak 2008-10-23 01:19:07.000000000 +0200

Hello, Since i use facter 1.5.5 i got error running it by hand. It still work in puppet but i loosed the hability to run it from the command line: (aqadmin)> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50:in `require'': no such file to load -- facter (LoadError) from /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50

Hi all, I''m using the pear/pecl package providers from http://www.mit.edu/~marthag/puppet/ and I''ve run into a memory limit problem. I''ve tried hacking the script so that it passes additional options to pecl/pear, however these just error out about not being valid options (even though they are!). I''m now at a point where the following stanza gives the

I''m using puppet to manage configs on machines where I don''t have root access. Whenever I use a File resource where the source is a puppet:// resource, I get tons of warnings when I run puppet that look like: Cannot manage ownership unless running as root True enough, I''m not running as root, but I also didn''t specifically mention a "owner"

We have successfully installed puppet on a CentOS Server, but I am battling with a deployment. It has to do with grid software. The repository gets created, then begins installation. The problem is that it just hangs - no errors, no network activity. I can see puppet is running, but nothing it being updated. Any pointers ? -- You received this message because you are subscribed to the Google

So I have been trying to run puppet once in my kickstart %post scripts but every time it detaches and daemonizes even though I have explicitly stated otherwise. Am I missing something? # rpm -q puppet puppet-0.24.8-1 # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature

Hi, I have a lot of systems where the puppetd doesn''t do anything .. When I test with puppetd -tv, it s running well, but when it is started as deamon th process do nothing :( How can I debug this ? Vincent May 29 10:07:56 puppetd[6160]: Reopening log files May 29 10:07:56 puppetd[6160]: Starting Puppet client version 0.24.8 May 29 10:07:56 puppet: puppetd startup succeeded May 29

Hi guys, Apologies if this is covered elsewhere. I''ve had a hunt through Google, Redline, and the FAQs but dont see it. Puppet 0.24.8 (and 24.7 on teh same box) starts up fine, but then just sits there, regardless of what I set runinterval to be. Puppet Server debug output stops at: debug: Creating default schedules debug:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

Hello there I''m having this error: Could not call fileserver.describe: #<Errno:: ECONNRESET: Connection reset by peer> From what i can tell, eventually the master decides it has had enough and freezes. I''ve got about 25 hosts checking in to it, but restarting the master daemon appears to be only a partial solution with the clients occasionally not being able to then

I just started getting this error on some machines after a yum update from centos 5.2 to centos 5.3. Does anyone know what it means? Since I''m not a ruby person, I''m not sure how to debug this, but it looks to me like facter is having trouble parsing information about my interfaces. # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:19: uninitialized constant

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

Currently, facter returns the kernel version as both the kernel and operatingsystemrelease facts. I would like to change that so that on Fedora, operatingsystemrelease is the release number (5,6,7 etc.) or ''Rawhide'' ... are there any objections to making that change ? David

Hi. I''m a beginner, but I have a basic puppet setup working. I am doing a manual tarball installation and it seems to be hanging then eventually timing out on just downloading the file: file { "/opt/hadoop-0.20.0.tar.gz": source => "puppet:///hadoop020/hadoop-0.20.0.tar.gz" } I have another module that does the same things and works, my only guess

Hello, I have run into problems in the past where a package has been added to our yum repository, and a (new) class has been pushed to install that package, but puppet fails because the yum db on the target machine is too stale, and thus isn''t aware of the existence of the new package. My question is this : what have other Puppet admins done in order to ensure that a target machine