similar to: Error 400 on SERVER - pe_mcollective - missing value of param 'undef'

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

Hi, I am able to install my RPM via this puppet code ... [root@agent1 ~]# puppet apply -v install_named_conf.pp info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb info: Loading

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?

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:

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

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:

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir

I am trying to setup a different CA_server and master server. I am following these links : http://bodepd.com/wordpress/?p=7 http://docs.puppetlabs.com/guides/scaling_multiple_masters.html Kindly help as am getting this error info: Retrieving plugin err: /File[/var/opt/lib/pe-puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1

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

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

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

Does anyone know why i would get a module error for my ''base'' module that I''m not even including for a node? I''m explicitly NOT include the ''base'', yet puppet-client-t2 still errors when i pull it in. Snips from both are below. Any ideas why this would happen? Thanks, JJ ==== site.pp file [root@puppet-master-t1 puppet]# cat

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

Hi, I wonder why the puppet agent on the server itself will not run: ---snip--- # puppet agent --test Error: Could not run Puppet configuration client: Puppet::Node does not respond to from_s; can not intern instances from text/plain Error: Could not run: can''t convert Puppet::Util::Log into Integer ---pins--- whereas the client on a test box tells me: ---snip--- # puppet agent --test

Hi, I am trying to use Hiera in puppet 3 and I have two nodes that both need the same configuration. In this case they are two web servers which have the same apache configuration. Rather than creating two seperate hiera files for node1.yaml and node2.yaml is there a way to group these by role (e.g. webserver.yaml)? I want to avoid duplicating the configuration if possible and keep the data

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

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

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]

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

Does anyone have any insight into this error message? err: Could not retrieve catalog from remote server: Error 400 on SERVER: The fact named fact_stomp_server does not appear to be a valid hostname. The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this problem is running puppet agent as a normal user instead of root, or the fact is