similar to: Puppetting the puppetmaster problems

Hi, I am using a template to create an /etc/exports file. I have a template that looks like this (but results in the puppetmasterd dying on the server when the client updates): <% nfsHomeClients.split.each do |host| -%> /nfs <%= host %>(<%= mainshareoptions %>) <% nfspaths.each do |path| -%> <%= path %> <%= host %>(<%= nfsoptions %>) <% end

Hello, all. I am getting the following error on a couple of my puppet nodes when I run puppetd -v -o --no-daemonize --no-splay: err: Could not retrieve catalog: undefined method `-'' for #<XMLRPC::DateTime:0xb7c729e8> The error goes away if I add --ignorecache, but I''m not sure that''s quite the fix I''m hoping for. It will also go away if i remove my

Hi, I am getting the following error on my CentOS clients; err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/nodes.pp:32 The server is CentOS 5.4 with packages from the epel-puppet repos; # rpm -qa | grep puppet puppet-dashboard-1.0.3-3 puppet-2.6.1-0.3.rc3.el5 puppet-server-2.6.1-0.3.rc3.el5 The clients are; # rpm -qa | grep puppet

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

Hi guys, I''m trying to setup my first puppet installation and I''m running into problems. I''ve got the puppetmaster running on a fresh install of Centos 5.4. The puppet client is also on another Centos 5.4 server. Once I''ve signed the client certificate on the puppetmaster, the client seems to break. See below for the debug output from the client. Any clue as

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

Hi Experts, I''m trying to generate my own certificates (all of them, including certs for CA, server and client) for puppet to use. and I''m getting "Could not run: Could not retrieve certificate for puppetsrv and not running on a valid certificate authority" Just wondering what the problem could be? What I did is: 1. generate a self signed CA cert, and save the

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

whenever i run a test from client it finishes sucessfully but client is not getting any configuration changes from server [root@PROXY-02 tmp]# puppetd --noop --test notice: Ignoring --listen on onetime run info: Caching catalog for proxy-02.carnation.in info: Applying configuration version ''1327091881'' notice: Finished catalog run in 0.02 seconds [root@PROXY-03 modules]# puppet

Hello I have a puppetmasterd installation running on a Mac OS X 10.6.3 Server with puppet installed via macports. Earlier today it was happily signing requests, before I upgraded puppet from 0.24.8 to 0.25.4. Now I get "Invalid argument": bash-3.2# puppetca --sign bouti.carbonplanet.com bouti.carbonplanet.com err: Could not call sign: Invalid argument The only mention I can find on

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, As someone new to puppet I''m trying to work out the best way to manage different filesystems and logical volumes on different servers. Specifically I would like to be able to define on a series of nodes different LVM logical volumes to create and mount. I''m trying to do this at the moment with a define of the following type: # Manage a partition and create if needed.

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

Hello folks, I am getting this error on one of the clients, here''s all of the output. It was working on this client and today it stopped working. I cleaned the cert for this client puppetmaster by "puppetca --clean host.domain.com" and I removed the "/var/lib/puppet/ssl" directory so it would get new certs. But I still keep getting the same error as below. I have other

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 rather new to puppet and I''ve been trying to get a module to work on the client servers. Right now I''m trying to get http://forge.puppetlabs.com/ghoneycutt/pam to run. When I try to run it I get these two errors: err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of resource: Could not retrieve information from source(s)

We haven''t been able to use mongrel for testing yet, but in order not to waste time, we did some performance testing with 1, 2 and 4 puppetmasterd/webrick processes. Attached is an HTML page (ripped from our wiki - not pretty, but reasonably readable) which describes the method and results. If someone feels like making some nice graphs, that would be great. If not, I''ll try to

Hi guys, I am fairly new to puppet and I am having a problem with one of the clients. I recently installed a new server that should get config from puppet master. All similar servers I recently installed didn''t have any problem. I installed puppet agent on the server and sent a sign request. SSL cert is signed but when I run puppetd manually I get the following: info: Retrieving

So I have been trying to run puppet once in my kickstart %post scripts but every time it detaches and daemonizes even though I have explicitly stated otherwise. Am I missing something? # rpm -q puppet puppet-0.24.8-1 # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature

I restarted puppetmasterd and it announced that the Cert does not match existing key ! [root@puppet ~]# puppetmasterd --verbose --no-daemonize info: Starting server for Puppet version 0.24.1 info: mount[files]: allowing 10.100.0.0/16 access info: mount[files]: allowing *.gridapp.com access info: mount[files]: allowing *.dev.gridapp.com access info: Retrieving existing certificate for