similar to: Puppet Setup - Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Connection refused - connect(2)

My install was working for a couple of months until I rebooted my puppet server. The clients do not report an error when I run puppet agent -t. I''ve attempted to remove certificates and renew. The clients get new certificates, but the console still does not update. Even the puppet server itself is not updating as a client. After reboot the only thing I have noticed that changed

Dear All, I''m very new to Puppet Enterprise.... I have the following setup so far: 1. Puppet Master (Puppet Ent) on Ubuntu with its own Agent 2. Puppet Agent on MAC Mountain Lion Everything looked ok but then I noticed this on the MAC (below), which suggested to me I had the wrong Agent? I''m a little confused on how to get the Puppet Ent Agent for MAC? Info: Retrieving

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hello All, I wanted to create two two MySQL database with same user credential using Puppet-MySQL. How can I achieve this? Please find my script below. class mysql::vsdatabase { include mysql mysql::db { ''vidispine'': user => ''user'', password => ''user123'', host => ''db.<hostname>.com'', } } How can I add

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

Hello all, I''m running puppet for the first ime. I''ve finished the install but I''m stuck at the certificate part. The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet client (0.24.8-4.el5) is running on CentOS 5.3. After the install, from the client side, I''ve run: puppetd --server puppetmaster.domain.com --waitforcert 60 --test On the

Hi, I have a puppetmaster - agent architecture. I have a module for the vsftpd configuracion in the agents. The configuration of the value ''max_per_ip'' in the agents may vary. This is a line of the manifest: $max_per_ip = hiera(''max_per_ip'',10) I want to specify different values for each agent using hiera. The problem is I am only able to specify the

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

I have a small environment with a single puppetmaster and puppetdb on the same node that I get sporadic "Failed to submit ''replace facts'' command" errors from nodes. It isn''t consistent about which nodes are causing the error and I can''t find anything else going on at the same time on either the master or the agent that these errors happen. Here

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

I made two decisions this afternoon that are now related to each other. 1. Use more of the modules that exist in the Forge 2. Rebuild my monitoring server As I perused the various modules that help with managing monitoring packages my eyes fell upon a module that reported to be able to manage nagiosql, a setup that I had been planning on migrating my nagios monitoring to. So I installed

Greetings, ruby 1.8.7, facter 1.5.7, puppet 0.25.2, and Solaris 10 on sun4u. From /etc/puppet/fileserver.conf, [solaris] path /etc/puppet/manifests/solaris allow * From /etc/puppet/manifests/site.pp, file { "/etc/shadow": source => "puppet:///solaris//etc/shadow", } And, ls -l /etc/puppet/manifests/solaris/etc/shadow -r-------- 1 root sys 536

Hi everyone, Here are the manifest I am using: In file ''*modules/test/manifest/init.pp*'': class test ( $test = undef, ) { notice("Here is the message: ${test}") } Now in ''*modules/saas/manifests/client/sudo.pp*'': class saas::client::sudo { class { ''test'': } } Now in ''*manifests/sites.pp*'': import

Hello After add some packagelist to puppet class. I get lots of warning message "appears to have a negative number of dependencies". My puppet master and agent version are 3.3.1. Here is the log out: [root@gpu022 ~]# puppet agent --test Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in

Morning All I''m trying to use Hiera with Puppet 3.0 to streamline some of my module configuration... However I''m having issues using the ''*%{::clientcert}*'' variable as part of the hierarchy... Currently, my *hiera.yaml* file looks like: --- :backends: - yaml - json :yaml: :datadir: /etc/puppet/hieradata :json: :datadir: /etc/puppet/hieradata

When I try to connect to my new puppet master, I get an error because of a self-signed certificate: ---snip--- # puppet agent --test --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [self signed certificate in certificate chain for /CN=Puppet CA:

I auto-upgraded puppet (as usual) using "yum upgrade -y", and now all agents are getting error 400. # puppet --version 3.0.0 On agent (any!) # puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for build6.[censored]: Failed to find facts from PuppetDB at abyss.[censored]:8081:

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path

Hi there, I''m running into an problem which I can resolve. It is bugging me for couple of days now. Goal: CentOS 6.4 freshly installed incl puppet 3.2.3 and I want to install puppet master, puppetdb, mod_passenger & apache with "puppet apply". So when this is complete, I should have an puppet master server running so I can create new hosts etc. So this is the command