similar to: Certificate nightmares

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status

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 {

Hello everyone, Just getting my first puppet master set up and I am having a problem that I just do not know how to get past. For some reason, my certificate store keeps getting corrupted. Basically what happens is that the server will issue itself a valid certificate (after removing the ''bad'' cert) and will run just fine. When I start puppetDB (I am pretty sure it happens

Hi, I currently have a MySQL database containing all Puppet storeconfigs. My intention is to migrate to PuppetDB on a PostgreSQL server, so the first step is to use the ''storeconfigs'' face to export all the DB to a file PuppetDB can later consume. But the ''puppet storeconfigs export'' command always ends up being killed, I suspect due to some sort of OOM

Is there an easy way to convert a puppet client into being a puppet master? Here''s the scenario. I''m using puppet to configure all my systems, and would like it to be able to deploy a new puppet master as well. We have systems worldwide so having local puppet masters is very desirable for fault tolerance. So Kickstart (via cobbler) installs a puppet client during the initial

I''m having a strange issue: A new machine created this morning showed thi error: ON PUPPET AGENT [root@wso2greg ~]# puppet agent --environment=production --verbose --no-daemonize --debug Debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Failed to load library ''ldap'' for

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 all, I have experience using puppet, however I am new to setting puppet up as it was already done for me in past environments. I am running into an issue while trying to set puppet up for the first time on RHEL 6.4. I was hoping y''all might be able to help me! I get the following error from the puppet client''s /var/log/messages log: May 30 07:06:30 pclient

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

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

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

Hi all, Could anyone help me at least start debugging this issue? All agents have the same error, but i can''t find anything on the master-side logs. And the agent-side logs are non-existent (/var/log/puppet is empty). Thanks. Versions: Master: Red Hat Enterprise Linux Server release 6.3 puppet-server-3.1.0-1.el6.noarch puppetdb-1.1.1-1.el6.noarch puppetdb-terminus-1.1.1-1.el6.noarch

I need to programmatically remove cert from Puppet master and remove all information in Puppet DB for a node from another machine which is neither Puppet Master or PuppetDB. It does have a Puppet signed cert since it is also provisioned using Puppet. I can''t find any decent documentation on this. I am using the Community Edition. Any pointers / help is appreciated. Rajul -- You

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

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

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Ok, I''m new to puppet, but I''ve got everything working for my setup. Almost. I''m trying to set up a new server, using cobbler, and then puppet. CentOS 6.2 Puppet 2.7.11 Cobbler 2.0.11 I have things set up so I can use kickstart to install the server on boot. It installs puppet and facter from the puppetlabs repos and the snippet

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is