similar to: Catalog changes not picked up immediately

Hi again, I''m trying to manage mount options in /etc/fstab with Augeas but can''t figure out how to add more than one option. augeas { "/etc/fstab": context => "/files/etc/fstab", changes => [ ''set *[file = "/tmp"]/opt nosuid'',

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 {

I''m looking for a way to run more than one puppetmaster on the same server under passenger. Most of the puppet CPU load is waiting for the catalogs to compile. This also seems to be mostly what takes large amounts of RAM. I have storedconfigs on. I want to be able to move the fileserver to a different pool of puppetmaster processes. Is there an easy way to tell the client, either in

Hello, I randomly errors like this: Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog from remote server: end of file reached Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (notice): Using cached catalog Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog; skipping run Here are the versions: puppetmaster

Greetings, I have a tested, working setup of Puppet and Webrick. I can add nodes, classes, etc. Then I switched to Puppet/Passenger and get the error below. Puppet, Apache and Passenger are all up. I have installed using *YUM *repos and *GEMs*. So, I have the most updated packages they have. Puppet version: 2.7.19 Ruby version: 1.8.7 (2011-06-30 patchlevel 352 i386) Apache: 2.2.15 The error

So set up new node, ran on the client puppetd --server puppetmaster --waitforcert 60 --test on the puppetmaster itself I ran puppetca --list saw the hostname and then ran: puppetca --sign hostname.domain.com and on the puppet node itself I went back and ran puppetd -tv and get the following error: err: Could not retrieve catalog from remote server: certificate verify failed warning: Not

Hello, Seems that file ressource gets a new idea of what to be given. I have the following recipe : class resolvconf { file { "/etc/resolv.conf": owner => root, group => wheel, mode => 644, source => "puppet:///puppet/dist/resolv.conf",

Hi All, We are observing frequently issue that Puppet agent intermittently stops without doing any thing when lot of puppet agent hitting puppet master . In our environment , we have configured puppet master over Apache-passenger and we have used LDAP as node classifier. - puppet 5.5 - Apache-passenger 3.0.17 - CentOS 6.3 / 5.5 - OpenLDAP 2.4 Sometimes restarting Apache solves

Hello, I''m new to puppet and am getting a puppet server setup with puppet dashboard. I have the puppet server and puppet dashboard (Apache/Passenger) setup and working well with 60+ test nodes working as expected. Only problem is that I have this one error in the logs which I can''t figure out. Jan 26 17:09:41 ppt01 puppet-agent[27357]: Could not retrieve catalog from remote

Just installed the puppet master server in and the client just installed the puppet I managed to sign the certificates root@Puppetmaster:/etc/puppet# puppet cert --list --all + "puppetclient" (96:9A:C3:8D:B6:72:A4:5F:01:AA:40:A9:95:3E:FB:D2) + "puppetmaster" (12:92:DF:EB:72:E5:DF:99:D8:22:CA:5F:22:3A:1D:61) at the time I create the file site.pp in / etc / puppet / manifests

I''ve been hitting this issue for a long time. well over a year and I guess it''s time to start pushing it to try to find the root cause. I''ve seen this reported several times in the past but I''ve never seen a resolution found for this exact problems. There are other root causes for pson errors that have been resolved, but not for the ones describing my

Hello, I really didn''t expect this to be difficult, but I''ve been struggling with this all day :( I''m running CentOS 5.3, with rubygems, rack and fastthread, from EPEL. I''m running puppet-0.25.0-1 built from the spec file in the latest stable tarball. I''m using mod_passenger-2.2.5-2.el5 from Jeroen van Meeuwen (kanarip), which is effectively EPEL

Hi, I am running dashboard 1.1.0rc1 under passenger 3.0.5 and apache 2.2.3 with puppet 2.6.6. Im trying to get urls like this http://user:password@host working as suggested in the docs for reporting but atm i did not get it (401 auth requided). Maybe I am forgetting something? I use a common .htpasswd file. Auth type Basic, etc. Sorry if this has been seen in this mailing-list. I searched for

Hi, I have a puppet infrastructure running 2.6.14 under Passenger with about 30 nodes. I''m just spinning up a new Cent 6.3, puppet 2.7.19 master. Right now I have the master built and configured using the same configuration as my 2.6.14 setup, with a few tweaks for the new version. Puppet on the master built itself fine. I have puppetd stopped on the master. I tried pointing one

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

I updated some of my gems, and I think it may be the reason I am getting the following error when the agents try to retrieve a catalog. err: Could not retrieve catalog from remote server: Error 400 on SERVER: The single-table inheritance mechanism failed to locate the subclass: ''Host::Managed''. This error is raised because the column ''type'' is reserved for

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

Hi all, I''m in the procedure of migrating my old puppet server (puppet-2.6.14-1.el5) with mongrel to a new one (puppet-2.7.14-1.el6.noarch) with passenger. I''m facing a really strange behaviour with the catalog compilation time. I''ve 3 servers: 1.-) Centos 5.8 puppet-2.6.14-1.el5 + rubygem-mongrel-1.0.1-6.el5 Client: Compiled catalog for td055.pic.es in environment

Anyone know what this is? It doesn''t seem related to puppet but I''m stumped. info: Loading facts in dmidecode info: Loading facts in cpuinfo debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in

Hi, I install puppet 2.6.18, test it and it was working okay. Then I install Apache and Passenger on the Puppet server. I run on a puppet agent: puppet agent —test And I got the error: "warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run" In the puppet server access_log I have: "GET