similar to: Certificate Issues.... again

- ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] - puppet-2.7.19-1.el5 I''m facing with the following error when starting puppet agent: **`puppet agent --server=puppetmaster.domain.com --no-daemonize --verbose --debug`** debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Puppet::Type::User::ProviderDirectoryservice:

How do I debug errors with external nodes? When my client connects, the following appears on the puppetmaster when running in debug mode. It''s not feasible to always be running the pupeptmaster in debug mode. debug: importing ''/etc/puppet/modules/yum/manifests/client.pp'' in environment production info: Automatically imported yum::client from yum/client into production

I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in

Hello Everybody, I am trying to install the puppetdb on the same machine as am running my puppetmaster. I am getting the following error when am trying to connect the agent: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for ftldwshost180.wsdev.citrix.com to PuppetDB at

Hi, My puppet master don''t want to start anymore. Any idea ? [root@puppetmaster requests]# puppet master --no-daemonize --debug debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug:

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 everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

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

Anybody knows what this error, bellow, means, the target file, C:/Splunk/etc/system/local/inputs.conf, does exist. sometimes, if I delete the file, it does actually create it, but never update it if it exists and changed... The resource is defined as:     file { "splunk_inputs":        owner   => SYSTEM,        group => SYSTEM,        mode    => 664,        require =>

Hi, whenever i am starting puppet master after new installation it gives below messages .. /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `initialize'': Permission denied - /var/lib/puppet/run/master.pid (Errno::EACCES) from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `open'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in

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

Oh my god.... what is this? Getting this on first boot of new client. Aug 24 01:11:09 app03 puppet-agent[5392]: Reopening log files Aug 24 01:11:09 app03 puppet-agent[5392]: Could not request certificate: Neither PUB key nor PRIV key:: header too long I stop the client, and remove the ssl directory on the client: [root@app03 puppet]# service puppet stop Stopping puppet:

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

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

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

All, I''m having an interesting certificate problem with a host I provisioned today. The host was provisioned and puppet was installed as part of the post-os provisioning process. After I signed the certificate I see the following on the client side: [root@client ~]# puppetd --verbose --no-daemonize notice: Starting Puppet client version 0.25.4 err: Could not retrieve catalog from

We are seeing this error in our log files on some clients: puppetd[15068]: Could not run Puppet configuration client: undefined method `initvars'' for #<Puppet::Type::Package:0x2aaaabbb4858> Where do I begin troubleshooting this? The client software versions are: ruby-1.8.5-5.el5_4.8.x86_64 ruby-libs-1.8.5-5.el5_4.8.x86_64 ruby-shadow-1.4.1-7.el5.x86_64 facter-1.5.8-1.el5.noarch

I am getting this error after installing puppet with gem $ gem install puppet Fetching: facter-1.6.14.gem (100%) Fetching: puppet-3.0.1.gem (100%) Successfully installed facter-1.6.14 Successfully installed puppet-3.0.1 2 gems installed Installing ri documentation for facter-1.6.14... Installing ri documentation for puppet-3.0.1... Installing RDoc documentation for facter-1.6.14... Installing

Hi, I have a couple of FreeBSD-servers that I try to manage using puppet. I''m just trying it out at the moment and have just deployed 5 new boxes (from PXE and scripted installation so supposedly they are all identical except for the name and ip-addresses). On two of the servers I get the error-messages at the bottom of the post. The first error- message I get every time I run puppet on

I have been through all of the instructions for setting up a PuppetMaster using Passenger. At the present time, when I access Passenger I receive the Passenger Error page with the message "The application has exited during startup (i.e. during the evaluation of config/environment.rb)". I''ve looked at the log files and there is nothing obvious. When I run puppetmaster