similar to: switching checksum: did not match checksum

Hello List, I´ve tried to switch from md5 checksum to md5lite within all my configuration to spare a few cpu cycles on my master, but it didn´t work at all :-( Then I´ve found out about bug #13199, but the bugs lists only 2.7x as affected. can anybody confirm this issue on 3.x? funny that the bug isn´t anywhere on the roadmap at all .... I´d suggest to remove mtime/md5lite from the

This happens to Puppet 2.7.1 (both master and client). I have a file resource that I set to ensure => absent, Puppet removed it correctly with info line that it has a duplicate entry in the filebucket. I then changed the ensure => present, the agent run gave me following error: /usr/bin/puppet:19 err: /Stage[main]/Emb/File[/opt/jetty-distribution-7.4.2.v20110526.tar.gz]/ensure: change from

Hello puppet users, I´de like to switch from md5 checksums to md5lite to save a few cpu cycles on my (overloaded) puppetmaster. so it is just replacing md5 to md5lite within my manifests and I´m done or do I have to keep things like the local clientbucket in mind? are there any procedures/recommondations regarding this? I´m running puppet >= 3.1.x on my puppet minions and master. bye ,

Hello, Anybody know how I can make checking file for verify for size/md5sum and if it not equal my value rewrite it from server. There may vriant than simple: file { /my/file: ensure => present, checksum => true,source => "puppet:///files/file"} ? Thanks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to

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

So I''m new to puppet and I''m having a bear of a time just getting a test server going. I installed puppet and the puppet client via yum on CentOS on AWS, so that saved me some time. I followed a few various blog posts about getting everything set up and applying a file, etc. Now I am trying to install a module (puppetlabs/apache) and it''s failing miserably for me. I

Hi all, class zabbix { file { "/etc/zabbix/": ensure => directory, recurse => true, purge => false, force => false, owner => "root", group => "root", mode => 0755, source => $operatingsystem ? { solaris => "puppet:///zabbix/solaris",

Hello, Does anybody know how to compare a filebucketed file easily with the current file based on these infos? info: /Stage[main]/Nginx/File[/etc/nginx/nginx.conf]: Filebucketed /etc/nginx/nginx.conf to puppet with sum 90dbcd7cf0accf5d372d077a6c90020c remote: notice: /Stage[main]/Nginx/File[/etc/nginx/nginx.conf]/content: content changed ''{md5}90dbcd7cf0accf5d372d077a6c90020c''

Hello, I''m running Puppet 2.7.6 and currently expanding the number of servers managed by Puppet. At around the 160-170 host mark (with a 5-minute run interval + splay), my puppetmaster server is starting to die. Is this normal? What I''m getting in the agent logs is the following: Wed Jun 20 12:15:08 +0200 2012 Puppet (debug): Failed to load library

What is puppet doing here? Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch Nov 17 00:02:01 gumby puppetd[720]: (//Node[gumby.fr.xxx.com]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure) created Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch Nov 17 00:02:07 gumby puppetd[720]:

I am having issues with filebucket. I have looked through the puppet users google groups with similar issues but have not found a solution that works. I am trying to setup a central filebucket on the puppetmaster server. I am replacing the client''s /etc/puppet/puppet.conf file with a preconfigured version. The server delivers a copy of the puppet.conf file to the client, but the backup

I configured my rsync daemon to be restarted when the rsyncd configuration file changes. When the rsync daemon gets restarted by puppet, it listens on the same port puppetd does, so running puppetd again results in an error. The init script for rsync is small and can not be changed from puppet (all variables are declared within the init script and it only searches for the path where the rsync

Hi All, I was surprised to notice that a call to noop from puppetrun did not work as expected. on the agent side (for this case the server side..), I ran: puppetd --verbose --no-daemonize (where listen is set in the puppet.conf) on the puppet server side(in this case the client side), I ran: puppetrun --noop --host SERVER notice: SERVER(IP) triggered run info: Caching catalog at

I''m running puppet from svn - build 2537. I''ve got a functional configuration and am testing it on a couple of development machines prior to moving it into production. I noticed today that the machines are taking ~300 seconds to process their configurations, so i watched a run and saw that it''s recompiling all of the Packages every single time. The only thing

Hello, I''ve created a little class which should unpack a 7z archive on Windows. The class has a parameter for passing in the archive version, so that I can trigger an update when a new version of the archive is available. A simplyfied version looks like this (requires 7z): class my_archive ($version = undef) { file { ''version'': path =>

Hello List, We are using puppet to manage a growing number of Debian Etch based servers (currently 70). Since upgrading to 0.22.4 we encountered a problem when services do not restarted on puppets request. For example the Nagios remote plugin executor daemon (nrpe). It''s running daemonized and its confiugration is located in /etc/nagios/nrpe.cfg. This file is managed through puppet

Hi all, I''m having a stupid moment getting a remote file bucket working. My client only file buckets locally, not remotely. I have this site.pp: ********* filebucket { "main": server => "puppet" } File { backup => "main" } node ''default'' { include test } ********* and this test module: ********* class test { file {