similar to: configured puppet server as client now no updates are working

I''m running into a very odd occurrence. I started with a new puppet server and was able to add a few classes, however as I try and add new ones I get odd parsing error messages, the most common being Could not match ''}'' at whatever file. Here is the exact error I get err: Could not retrieve catalog: Could not parse for environment production: Could not match

Hi, I''m trying to use standard hiera on puppet (gentoo). I simply did # gem install hiera Then setup /etc/hiera.yaml When i call the hiera() function in puppet i get "Error 400 on SERVER: Unknown function hiera at /data/puppet/manifests/ site.pp:27" Is there a step that I''m missing? BTW. standalone hiera works fine. -- You received this message because you

When an error occurs in prerun_command, puppet continues execution instead of stopping. We can see the error at the log file, but puppet cotinues doing changes: puppetd[18430]: Failed to prepare catalog: Could not run command from prerun_command: Execution of ''/path/to/command'' returned 1: We want to prevent changes when an error occurs in prerun_command. Our puppet.conf:

I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9

Hello, I was trying to change two modules on my puppet. And I was block on one error, until I figured that the error which show up was not related to a specific module. This error is causing issue to all my puppet clients : #puppetd -vt info: Retrieving plugin err: Could not retrieve catalog from remote server: Error 400 on SERVER: compile error (erb):416: syntax error, unexpected kEND,

For some reason I am unable to run "dry runs" of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not

Hello, I am trying to configure a new puppet server on Debian Squeeze, so the server version will be 2.6.2-4. I am trying to configure a client running Lenny, the puppet version is 0.25.4-2 I declare the new client with the command : #puppetd --server puppet.domain.tld --waitforcert 60 --test on the server : #puppetca --sign client.domain.tld When the client finish to execute the first

Hi Guys, I am new to the world of puppet. I have successfully configured puppet on centos 6 and am now trying to install puppetb on the same host. After the configuration when I try to run puppetd --test command on the client I get : [root@puppettest ~]# puppetd --test notice: Ignoring --listen on onetime run err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to

I change my ubuntu to mac os, and rsync my puppet file to the puppet server. I run puppetd -tv in the client, and then this error happens puppetd -tv err: Could not retrieve catalog: Could not parse for environment production: Could not find file /etc/puppet/manifests/site.pp warning: Not using cache on failed catalog -- You received this message because you are subscribed to the Google Groups

Hi working with the following puppet-0.24.1-1 puppet-server-0.24.1-1 ruby-1.8.1-7.EL3.8 rhel3 u8 The puppetmaster is running on rhel4 u5 I am working with puppet and rhel3 u8 and I have any an issue anytime I ask puppet to interact with yum for the record - yum from the cli works perfectly I setup a class to manage ntpd and in the class I have the following function # make sure ntpd is

Hi, I exposed few days ago this situation on the IRC, but unfortunately I haven''t found a way to solve it yet. I run the Puppet Master with multiple environments, and everything is working good but a couple of nodes that are causing me some troubles. These nodes are pointing to my production environment and I need to point them back to development to grab some changes I made. I

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

Hello all, After banging my head against my desk for a few hours, I''m posting here (after being told this isn''t a bug). I''m trying to use puppet to install some packages on my fedora clients, som on my puppet master i created a class with the following contents: class fedora-ws { include atrpms-repo $packages = ["subversion"] package

Hello Folks! I am trying to learn puppet. Installed the puppet 3.0.2 and configured one node as the master and the other as the client. Generated the certs and all that. But, I seem to be doing something wrong wrt to the init.pp file. Attached is exact error and my current server configuration. Any help in helping me fix this issue is appreciated: *[root@pupclient ~]# puppet agent --test*

Hello a newbie here. The situation is that: 2 machine one master one client Puppet 0.24.5 This my configuration: Client: /etc/puppet/puppetd.conf [puppetd] server = Asus-Vista-Box logdir = /var/log/puppet vardir = /var/lib/puppet rundir = /var/run master /etc/puppet/manifests/classes/sudo.pp class sudo { file { "/etc/sudoers": owner => "root",

Today I was testing Puppet''s fileserver feature and and error came up: client> /usr/sbin/puppetd --test --verbose --server puppet info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: //Node[default]/sudo/Package[sudo]/ensure: created err: //Node[default]/sudo/File[/etc/sudoers]: Failed to retrieve current state of resource: No specified source

This is particularly nasty, since it''s on the puppetmaster itself: [root@puppet tmp]# rpm -q yum puppet puppet-server yum-3.0.5-1.el5.centos.5 puppet-0.24.0-2.el5 puppet-server-0.24.0-2.el5 [root@puppet tmp]# cat /etc/issue CentOS release 5 (Final) Here''s the output of puppetd --debug: notice: Starting catalog run debug: Loaded state in 0.01 seconds debug: Prefetching rpm

I am trying to setup Puppet + Mongrel on RHEL5. So far I have followed this document: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel_On_Enterprise_Linux The puppetmasters all start up and Apache starts up on 8140. However, when my client connects I get the following errors: [root@lv1764p puppet]# puppetd --server puppetdev.encana.com --no- daemonize -o -v info: Retrieving

I have set up puppet on Ubuntu/Debian servers with no problem. I am trying to get puppet working in a RHEL environment. I have the client installed and the certificate is signed so I know the two are talking but for some reason I can not get puppet to push the file on to the client. What am I missing? OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd

I am experiencing a curious event, and wondering if others have seen this... As well, I have a question related to it. Today, I noticed my puppet summary report from Foreman this morning, that 60 of my 160 hosts all stopped reporting at nearly the exact same time, and have not since restarted. Investigating, it appears that my puppetmaster temporarily ran out of disk space on the /var