similar to: Modules doesn't work from puppet agent.

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

I have a single LB running Apache with mod_proxy in front of a Puppet master. These are the LB and Puppet master configs: <Proxy balancer://puppetmaster> BalancerMember http://192.168.1.10:8140 </Proxy> Listen 8140 <VirtualHost *:8140> SSLEngine on SSLCipherSuite SSLv2:-LOW:-EXPORT:RC4+RSA SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite

Hey guys, Does anyone know how to change the location of puppet.conf? In my situation, I don''t want to store it under /etc/puppet/puppet.conf or ~/.puppet/puppet.conf -- I''d like to store it under /opt/puppet/puppet.conf in this example. Is there a method without having to symlink, perhaps with an environment variable like PUPPET_CONF=.... ? Thanks for your time, Jason --

Hello all, I fairly new to puppet and google groups so I''ll apologize in advance for not conforming to "normal" posting methods. I''ve recently installed puppetmaster on a fresh copy of Ubuntu 10.04LTS and after running: sudo puppet --configprint all, I get a long list of parameters and values echoed back to my shell. My question is where do these parameters and

Hi, ppl I dont know what to do. I configure a new client do sync with my server. the server accept de client_cert without errors and then when i run the "puppet agent -t" agaion i got this error output info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server

hi, i''m trying to set up my puppetmaster infrastructure with multiple puppetservers behind load balancers in each of our datacenters. i''m using 0.24.6. i''ve read the howto on puppet scalability, and i think i''ve got the ssl config working correct, but i''m noticing that when puppetd is used to build a puppetmaster, some of the files in $vardir/ ssl

Hi guys, I have a box that needs to identify itself to the puppetmaster as something different from the FQDN. I added certname to the agent configuration before the first run, but it doesn''t seem to be sufficient. The certificate was generated for the FQDN, and the host appears in the dashboard as the FQDN, and the node name used to evaluate the manifest is also the FQDN. I would

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

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 using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

Hi all, I have installed and configure puppet client in new virtual machine, but I have this error when running *puppetd --test (even if I run /etc/init.d/puppet restart) /usr/lib/ruby/1.8/puppet/defaults.rb:136:in `handle'': Invalid environment test (ArgumentError) from /usr/lib/ruby/1.8/puppet/util/settings.rb:299:in `parse'' from

Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch 2.7.19-1.el6 SERVER: -bash-4.1$ cat

I''m not sure at all what''s going on here, but I''ve spent a lot of time reading over the puppet hiera docs and setting everything up, but when I run puppet agent it just seems to ignore the hiera setup completely. Both the puppet master and agent nodes have exactly the same versions of puppet and hiera (installed via the official puppet APT repository). I''ve

Hey guys, Relatively new to Puppet and I''m trying to setup tagmail to send all emails to me: at one point I''ll filter that down to errors and whatnot (based on tags) but for now I just want to get it working. Master Puppet server is setup with Passengers, all works well: /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is

Hi It seems like classes.txt file is not being created when I run puppet on my servers. I am running puppet without a puppet master. I use subversion to pull the manifests on each of the boxes and run this command to run puppet. puppet apply --verbose /path/to/manifest My puppet version is puppet 2.6.4. My puppet.conf file looks like this: [main] # The Puppet log directory. # The

Hello all, I''ve tried to run ''puppetrun'', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

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

I have very strange problem. I set up puppet client on serveral servers but have problem with one of them. When I invoke: root@www ~ # puppet agent --server puppetmaster.domain.ltd --test notice: Ignoring --listen on onetime run info: Caching catalog for puppetclient.domain.ltd info: Applying configuration version ''1326444431'' notice: Finished catalog run in