similar to: Force puppet client reload?

I have some systems running Fedora Core 7. The latest yum break puppet with "Error: No matching Packages to list". I can make all the FC7 system not to update Yum. However, when I start installing Fedora Core 8, the default yum also break puppet. (err): Failed to retrieve current state of resource: Could not get latest version: Execution of ''/usr/bin/yum -d 0 -e 0

Hello, Why the following lines doesn''t work? cron { "app" : command => ""nice -n -10 /usr/bin/php /var/www/public_html/rotinas/rotinas.php 2>&1>> /var/log/app.log", environment => "PATH=$PATH", user => root, hour => ''*'', minute =>

Hello I have been using puppet for a while now, more or less successfully on SLES 11 and CentOS 5.5 currently I am using puppet 2.6.6 I now am trying it out on redhat 6, and now i run into an problem with even the simplest of modules/classes The error I get is : debug: /Stage[main]/Motd/File[/etc/motd]/content: Executing ''diff -u / etc/motd

Hi I''m trying to ensure ypbind and yp-tools are not installed BUT they one of the rare group of rpms that require each other. I have package { "yp-tools": ensure => absent, require => Package["ypbind"], } package { "ypbind": ensure => absent, require =>

I recently got a scary-looking circular dependency as a puppet error, and it took some thought to decipher it. Long story short, I fed it to graphviz, and the graph made it obvious where the problem was. Thought I''d share, in case others are having the same trouble. Code''s at http://gist.github.com/74566, and also pasted below for convenience. -- Philip # Make sense of

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

Hey gang, During the build of our Linux (EL4 and EL5) images, the kickstart process writes out a file (/etc/sysconfig/soe) that contains: SOE_VERSION="Version string" SOE_BUILD_DATE="2009-03-06" I then have /etc/profile.d/facter.sh scripts that has this: . /etc/sysconfig/puppet . /etc/sysconfig/soe FACTER_PUPPETMASTER=$PUPPET_SERVER FACTER_SOE_VERSION=$SOE_VERSION

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 am fairly new to using puppet, but have it setup on 25 machines. Just doing some basic configuration management. Recently I decided to try working with updating some services config files and used the ensure => running tags. My question is simple - if the source file does NOT change and I use a subscribe, why does the system keep restarting the daemon every time puppet runs? A simple

Hi i''m trying to describe some class with a package to install, which should work on different linux-distro''s as well on linux and openbsd: class vim { package { ''vim'': name => $operatingsystem ? { centos => vim-enhanced, default => vim, }, alias

Greetings! As you undoubtedly know, the fixes for CVE 2007-5162 in ruby break installations where puppetca has created certificates with a CommonName different from the server's real hostname. The Puppet clients quite correctly complains about hostname mismatch. A number of better and worse solutions have been suggested for this problem, especially in ticket #896. IMHO, there are two good

Hello there, Since the update with ruby all my puppet function is dead (well known issue with the cert) . There has been some discutions on the dev list on how to patch this for future versions. I have read the list and wondered how we can solve the issue while waiting for the .24. I am in beta test of the .23.x version but on my production system i wanted to find a way to solve this now

Hi All, In my companies environment, we have multiple sites in multiple geographic locations, sometimes with high latency between the sites. I''m trying to come up with a solution that could provide puppet infrastructure to all sites nodes. ----a few assumptions--- - puppet manifest / configuration is fetched from a centralized version control system. - store db is needed (ssh keys,

Hey All, This is probably a gotcha of some kind. That is to say I''ve missed a configuration somewhere. I''ve recently moved over to using mongrel as the puppet server type and having nginx proxy to one of four mongrel instances. What I''m seeing though is that when I try to run a new node (one that has been created post moving to mongrel/nginx) is that it returns with 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

Hi all, The underlying assumption of membership in any community is that your participation is at worst neutral, and if possible positive. Communities, online or off, generally do what they can to protect themselves from detrimental influences, which is where policies, politeness, moderators, and all that come into play. Puppet''s community has been both fortunate and awesome,

I''ve been doing some work lately to create new native types that allow Puppet to manage SELinux features natively. So far, I have: - Policy module loading, unloading, and upgrading - File context - SEL Booleans There''s plenty more work that could be done, but with these three working it should be at a point where it''s useful to start getting real work done.

Puppet version: 0.22.4 facterversion => 1.3.7 rubyversion => 1.8.5 Given the following: file { yum_repo_d: path => "/etc/yum.repos.d", ensure => directory, recurse => true, purge => true } yumrepo { pkg_repo: descr => "Packages Repository", enabled => 1, baseurl => "http://Some/path/", gpgcheck => 0,

hello list!! I have developed a custom apache module for my company that setups up our own particular config of httpd and php in order to run our sites.. However, there is one wrinkle. It take two puppet runs to start the httpd service with this module and we''d like to get that down to one run! The reason seems to be that we have our own custom ssl vhost conf that we use called

I have : raw <- read.table("monthly.text", skip=3, sep="|", col.names=c("junk", "junk2", "wpi", "g.wpi", "wpi.primary", "g.wpi.primary", "wpi.fuel", "g.wpi.fuel", "wpi.manuf", "g.wpi.manuf",