similar to: What I''m doing with Puppet

Hello all, puppet hangs while trying to restart a daemon when the associated config file changes, here the log: Mar 19 11:30:04 ingentTest puppetd[27390]: Starting Puppet client version 0.22.0 puppetd[27390]: Starting configuration run puppetd[27390]: (/ingenttest/qualsevolnode/guaita[guaita]/File[/etc/guaita.conf]/content) synced puppetd[27390]:

Hi, I was at the Puppet talk at Oscon and I would like to try using Puppet for PXE on RHEL machines and I was wondering if there are standard minimal Kickstart recipes from which Puppet can then take over. Thanks, Jason van Zyl jason at maven.org

I''m very interested in the way that puppet appears to be able to generate nagios configurations though I can''t seem to find any documenation on how it works: http://reductivelabs.com/trac/naginator is clearly a placeholder page... Meanwhile the various pieces of info at links such as: http://reductivelabs.com/trac/puppet/wiki/TypeReference#nagios-host are just teasing me.

Why doesn''t the yum provider support version, I tried added ensure -> ''ver'' and it barfs up (on clients) with: <snip> err: //stan.gbuild.org/any-host/java/Package[j2sdk]/ensure: change from 1.4.2_12-fcs to 1.4.2_13-fcs failed: Package provider yum does not support specifying versions at /etc/puppet/manifests/classes/ java.pp:13 </snip>

Hello. Hope you can help me further. I can vaguely remember that once I saw a reference how to preconfigure debconf in puppet manifests. So you can define answers in debconf inside of manifests. No idea where anymore. Anybody knows? greetinx Christo

Greetings, I''m trying to set up a minimal CentOS 4 kickstart that installs puppet during the %post and then use puppet to build up the rest of the configuration. I''ve gotten things so that puppet 0.20.1-2 will install using yum during the %post in the kickstart, but now I''m seeing this error when it tries to run during %post and after I reboot the newly installed

Hi, I am new with Puppet and I am very glad using it, but I have a basic doubt, when I use puppet to install packages to a debian machine with: debian:/etc/puppet# cat manifests/packages/lm-sensors package { lm-sensors: ensure => installed } Does it run apt-get update before installing the package? If not how is the best way to do it? How Puppet deals with packages installations that

Hey Folks, I''m looking at doing automated provisioning of new servers and am trying to integrate puppet into this process. What I''m wondering though is what the best process for securely registering a new node is. At the moment the first time puppet is run I have to then accept the certificate on the puppetmaster and then run puppet again. What I would like to do is accept the

notice: /subject.sol1.net/virtual_mail_server/File[/etc/postfix]/checksum: checksum changed ''{time}Thu Jan 25 16:31:08 EST 2007'' to ''{time}Thu Jan 25 16:36:39 EST 2007'' I know there''s something weird in the directory modification detection that causes the next run after things actually change to suffer from this problem, but I''m getting it

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

How are people upgrading puppet itself on their hosts that run puppetd? Can puppet be used to upgrade to a new puppet package via gem, rpm or some other package provider? How do you handle restarting? Just hoping theres a better way than "ssh and a for loop" or having to have another configuration management system installed.

We were using Naginator resources like nagios_host, etc. along with stored configurations and exported resources. Worked pretty well. However we have to separate the Puppet master and the Icinga (Nagios) server. They will be on different machines from now on. Are there any best practices for such a scenario? I already thought about some kind of ''rsync'' of the configuration from

Can you wildcard a domain for a node name like the following? node ''*.sub.example.com'' { .... } Thanks, Kent

Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It

On Aug 27, 2006, at 9:55 AM, Thorsten Sandfuchs wrote: > hio, > me again :) > > In Debian, there is a mechanism to preseed debconf (configuration- > database for > the system) with decisions, before installing a package. Debconf > mussn''t ask > the user then. I wrote this pp for preseeding-support: [snip] Very cool. Seems like that''s something that

Hi, I have this small problem with my servers managed by Puppet (i have a workaround so the problem is not so important): 1) These servers are installed with Red Hat Linux Enterprise and i use Puppet in client-server mode. 2) I''ve made a Puppet class called "yum" to install (by the RPM package provider) and configure YUM on my servers. I don''t use the YUM package

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, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

I just talked to Mike McGrath from Fedora Infrastructure, and he told me that they are seeing load spikes (not quite performance problems yet, but definitely a concern) in their setup. As an example, the graph [1] shows a typical client - the spikes from 16:00 to 8:00 are almost exclusively puppetd doing its thing. It seems that the most likely culprit is the fileserver - they serve 500-1500

Hi all, Today I came across something that I consider a bug. Would like to hear your opinions. Facts: - Using 0.22.1 from Debian Unstable on a Debian Testing machine - Recipes work on other machines The recipe in question is: # Keep home-dirs in sync file { "/home/tim": recurse => true, source =>