search for: lutterkort

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

...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 from David Lutterkort''s yum repository. My sqlite rpms where build from source using the source RPMs from Fedora Core (sqlite-3.3.3-1.2). Is this problem with my sqlite or can someone reproduce this elsewhere? I tested it with a virtually blank site.pp and just storeconfigs turned on in my puppetd.conf file....

I just realized that if you don''t have redhat-lsb on your (Fedora 7) box, all those lsb* facts don''t show up. Should I make redhat-lsb a requirement for the facter rpm to guard against that ? David

Hey gang, I seem to be having a brain disconnect on how to get the Augeas type to manage things that have multiple values (i.e. an Augeas tree) via Puppet. If I run this in augtool: augtool> set /files/etc/ssh/sshd_config/AllowGroups/1000 sshuser augtool> save I see this in /etc/ssh/sshd_config: AllowGroups sshuser However, if I try this in an Augeas type: augeas {

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

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

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 ssh/ssh_config.erb: | Could not find value for ''initr_ports'' at /var...

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, I''ve just built rpm''s for puppet-0.23.1 - since there were a few people who had trouble with the update for 0.23.0 (the change in config files requires a bit of rpm trickery), I decided to be a little more cautious in how I push the new packages. So far, new packages are (or, will be shortly) available in rawhide, Fedora 7 updates-testing, and in my yum repos for

I am just starting with puppet to replace a ''homegrown'' config distribution system and it is looking very promising, i will be playing with the templating next. I have run into an error when attempting to disable the shipped repo''s with CentOS 4.4. See the relevant info below. This is obviously a problem when repo definitions include multi-line baseurl''s.

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

On the module organization wiki, we''re got the following statement: To control access to the files in modules, the fileserver configuration can contain an explicit declaration of a ``modules`` module:: ... however, I thought the fileserver couldn''t define module or any section that is in the module paths. Has anyone tried this? And if it doesn''t work, is there

Out of curiosity, is anybody using puppet on RHEL3 (or Centos 3) ? If so, how did you get it to work ? Did you build a ruby-1.8.x or does puppet work on the 1.6.x ruby that ships with RHEL3 ? thanks for any pointers, David

Puppet has been in Fedora Extras for the last couple of weeks or so; I just forgot to post about that. With that, there is no need to use my personal repo at people.redhat.com anymore; your standard yum configuration should find it. The current version is 0.18.3; I just built 0.18.4 for Extras, but it will be a day or two before it shows up on a mirror near you. David

This is in reference to David Schmitt''s writeup [1] I like that writeup a lot; I just had a few comments/clarifications: * Namespaces: For now, we just use a flat namespace for modules, i.e. you can''t have modules within modules, and you always know that in a fully qualified name ''foo::bar::baz'' that ''foo'' is the module name and

...I even tried making one of the puppets go to ''bink'' in stead of ''puppet'' but that doesn''t help. I also tried installing a new client but it doesn''t want to talk to the server either. Any ideas what might be wrong? I''m using the latest Lutterkort rpm''s on CentOS 4.5 and 5. Thanks in advance, Nico

Hello, I use puppet with RHEL and there are some packages that aren''t in up2date/yum repositories. I need a way to get these specific RPMs installed. There''s a blog posting that describes an almost-perfect way to do it: http://www.raskas.be/blog/2007/09/10/managing-user-passwords-with-puppet-on-centos/ The only problem with his example is that the RPM will always in the /tmp

Hi, I''m just getting started with puppet, and using the RPMS provided (on CentOS 4.3), and RedHat''s killproc is annoying me again. The process is called ''ruby'' instead of ''puppetmasterd''. $ ps 7869 PID TTY STAT TIME COMMAND 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] So, service puppetmaster

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

I am working on some initial testing of puppet and noticed that when using the package type, I see this in my client logs (from different runs): warning: Found multiple default providers for package: up2date, yum; using up2date warning: Found multiple default providers for package: yum, up2date; using yum This is on a CentOS 4.4 client with puppet-0.22.0-1.el4 (from dlutter repo). After