similar to: Undefined method 'closed?' for nil:NilClass

Hi list, I am trying to get a puppet certificate on a new client but I get error: err: Could not request certificate: undefined method `closed?'' for nil:NilClass I googled and found that it had something to do with reverse DNS lookup, the client is behind a NAT firewall so I assume a reverse lookup will fail. Can I bypass this somehow? Puppet version on master and client is 0.25.4

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

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:

Hi. Is there any way to make puppet run a particular module first before another module is run. For example, I''m using the augeas resource type in one of the modules. But libaugeas-ruby1.8 is not installed in the client machine. So when the catalog is run, I get the following error: Could not find a default provider for augeas. So I built another module that will install the

I am banging my head against the wall for recently built hosts that are unable to verify the server''s certs. The usual is not working. on the puppet agent machine: find /var/lib/puppet/ssl -type f -delete on puppet master: puppetca --clean <new_host_cert> on agent: puppetd --server puppet --waitforcert 2 --no-daemonize -d -o on puppet master: puppetca --sign

I upgrade our infrastructure (mostly RHEL5, some RHEL6) from 3.1 to puppet-3.2.1-1.el5. Ruby sits at ruby-1.8.7.370-1.el5. I ran some tests and everything seemed good so I pushed it out. Since then, all my puppet clients are failing with this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `[]'' for nil:NilClass at

Hi, I had a working puppet setup using version 0.22 until the ruby security patch bit me. I tried upgrading server and clients to 0.24.1 however my old manifests don''t seem to work anymore. When I run puppetd on the client I see lots of messages like: err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent

Hi, I''ve been experimenting with Puppet for a few days now, and I really like it. But! I''m having real CPU usage problems. Puppet is still happily eating away 100% CPU for almost an hour at a time, with no apparent things happening. (puppetd -tv --trace --debug, but nothing appearing in the console during this.) I believe the following resource is to blame: file {

Our puppetmaster runs 0.24.8 on Ubuntu 9.10. Our clients are either Ubuntu 9.10 or Ubuntu 8.04. We''ve just brought up our first Ubuntu 10.04 machine. This machine installs puppetd 0.25.4. The Ubuntu 10.04 machine can''t seem to present it''s certificate request properly. In my masterhttp.log, I see [2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

Guys, I seriously could not find this topic in the documentation. What do you do when you need to force puppetd hosts get the new settings from puppetmasterd? What I found was only sending USR1 signal to the client process in order to make it refresh its configuration from the master. But I find it a bit inconvenient for a large amount of hosts. There is also puppetrun which, if I understand

Dear all, I have this line: <% $c_repo.split('','').each_with_index do |repo, i| %> in one of my template files and on the target node I''m getting this error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template zmfs/zmfs_prob.erb: private method `split'' called for nil:NilClass Any idea what am I missing?

Hi all. I am testing 0.25.4 to upgrade from 0.23.2. In testing, I found two strange messages on 0.25.4 which I have never found on 0.24.3. So could you tell me what these messages mean and how to fix them. [Environment] Puppetmasterd -version : 0.25.4 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [Strange messages] 1.When Puppetd

Hi I''m trying puppet for the first time and attempting to get it working in Amazon EC2 with Ubuntu 10.04 using the default puppet 0.25.4-2ubuntu4, I''ve read the ''Pulling Strings'' book and tried following various tutorials found on the net to set up it but each time I get as far as signing the certificate before getting this error.... info: Caching certificate

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

Hi all, I''m new to puppet and I can''t seem to figure out how to get rid of this error on the client or to get the recursive copy of files to the client: err: //dev_oracle_dev_tools::install/File[/tmp/oracle_dev_tools]: Failed to generate additional resources using ''eval_generate'': Error 400 on SERVER: private method `gsub'' called for nil:NilClass My

I''m getting this error message quite often on the puppet clients. I don''t know what it means. Restarting puppet often helps and the messages will go away, but suddenly it will come back again. Any thoughts? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

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

Hi, I am using puppet (version 0.25.5-1.e15 for redhat) for password management for non-system users. This morning, users on some of my puppet clients had their encrypted password strings in /etc/shadow replaced with the following string: YAML::syck::BadAlias That has effectively broken the users'' ability to login to those servers. Puppet will not overwrite that string with the

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]