similar to: Extending puppet catalog face

I''ve been looking into using puppet-rundeck and run into a bit of an issue that I''ve traced back to puppet. I have a feeling this is going to be my lack of understanding of something or a misconfiguration. Here''s a snippet of code that demonstrates my plight: https://gist.github.com/9667ad19762bf20bd947 The above works for only 1 of the 4 nodes, specifically the one

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, I''ve got a problem where clients apparently randomly lose the ability to retrieve catalogs. This is what I end up seeing in the log: puppet-agent[26510]: Starting Puppet client version 2.6.6 puppet-agent[26510]: Could not retrieve catalog from remote server: puppet-agent[26510]: Using cached catalog puppet-agent[26510]: Could not retrieve catalog; skipping run Notice that no

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,

I have followed many tutorials including the ones provided by puppetlabs and I keep seeing the same issues. I began by installing puppet on machine: puppet001, and puppet master on machine: puppetMaster. The hosts files were then configured so that both machines were reachable by the machine name. The puppet.conf files were then updated, and a cert was generated and sent from puppet001 to

Hi, I just installed & configured puppet-dashboard as per the official documentation <http://docs.puppetlabs.com/dashboard/manual/1.2/>, but now my nodes cannot retrieve their catalog: [root@puppetnode-01 ~]# puppetd --debug --verbose --no-daemonize ... err: Could not retrieve catalog from remote server: Server hostname > ''puppetmaster-01.mydomain.com''

Hi, I have noticed that when a typo is introduced or a module is plain broken, puppet will run using a cached catalog. This is logged as an error on the local client, however, it is not logged as an error on Puppet Dashboard. How can I change this behavior, so that using the cached catalog will result in a warning/error being displayed on Puppet Dashboard? Foreman does this. I''ve

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

If puppet fails half way into processing a catalog the system might be in an unusable state right? For example if it installs a package but not the one that follows it or can''t set up the config file for whatever reason it doesn''t know how to "undo " the catalog does it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

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, We''re trying to come up with a nice way to indicate when a Puppet module like cloud provisioner breaks a Puppet subcommand because of missing dependencies. When this happens in the current 3.0rc branch, all help for all subcommands is unavailable. This isn''t very helpful. We''re planning to simply mark the subcommands that have incomplete actions as

After upgrading my puppet master to 2.6.8 from 2.6.2, I intermittently get things like: puppet-master[29789]: (Scope(Class[Auth::Kerberos_ldap])) Could not look up qualified variable ''common::datacenter::ldap::ldapservers''; class common::datacenter::ldap has not been evaluated puppet-master[29789]: Failed to parse template auth/rhel5/ ldap.conf.erb: undefined method

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

How do I expose a Custom Puppet Face via REST API. Same as catalog or facts or node REST API Couldn''t find any resources on this. Any links to examples or write up''s on this? Thank You. Regards Sai. EMC Corporation -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving

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",

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*

I''ve tested this functionality in both 2.6.8 and the latest 2.7.0 RC. As far as I can tell, the TransBucket looks good but fails on #to_catalog due to an alias. https://gist.github.com/1028013 Any help or thoughts would be appreciated! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

>Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find terminus puppetsvr for indirection catalog I had a working puppet install (new) with 2 agents working well. I added puppet dashboard and the inventory part which is also working well. However, clients are talking to the server (putting info into dashboard inventory), but not pulling down the

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

We are getting this frustrating error on all of our servers after restarting the puppet server. Can''t seem to get rid of it no matter what. The following pops up in /var/log/messages after trying to start puppetd: Jun 8 10:59:04 svn001 puppetd[92558]: Could not retrieve catalog; skipping run Jun 8 10:59:18 svn001 puppetd[92597]: Could not retrieve catalog from remote server: undefined