similar to: Issues with environments not being respected

Hi, I''m trying to use Puppet ability to export and collect resources using PuppetDB. My PuppetDB and Puppet Master are running on the same host and I used the PuppetDB puppet module to install PuppetDB and configure the Puppet master. Each time the puppet agent runs on a client, the facts and the catalog are being pushed in PuppetDB and I can query the PuppetDB server to get

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

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

So, I''m reading that this works, but I''m obviously missing something somewhere, cause its not... I''m testing a masterless setup, and thus far, pluginsync isn''t doing anything. my puppet.conf looks like [main] vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl classfile = $vardir/classes.txt

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

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

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

puppet maser conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [master] classfile = $vardir/classes.txt localconfig = $vardir/localconfig user = root group = root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog =

I did a fresh install on Ubuntu 12.04 with apt packages from puppet labs. I have agents talking to my puppetmaster. Puppetmaster is running apache/passenger connected to puppetdb and puppet-dashboard is setup to use puppetdb but it is not able to see any reports submitted to puppetdb. When an agent connects to master I see : Info: ''replace facts'' command for hostname

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 a little confused by the configuration reference. Is the following configuration supposed to work in 0.23.2? # $Id$ 2 3 [main] 4 confdir = <%= confdir %> 5 vardir = <%= vardir %> 6 7 rundir = /var/run 8 logdir = /var/log 9 10 ssldir = $vardir/ssl 11 12 [puppetmasterd] 13 manifestdir = $vardir/manifests 14

I am trying out having multiple environments so that I can push a test config to a single server in production. The idea being that I could push out a config change to one server and see if the change works in production. If it does then I can merge the change into the production environment and push the change out to all the clients. So to test this I made a change to a config file in testing

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

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''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

I am working on setting up a Puppet configuration where some of the data is stored on a DRBD volume. The modules and vardir are stored on the drbd volume. The puppet.conf files point to the drbd volume for vardir. I created a cert for a VIP puppet-master using the puppetca -- create command I had everything working on the primary drbd node, but when I fail over, everything starts up fine, but I

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 all, I think i''m forgetting something. If i do: "puppet apply manifiests/site.pp" it works perfectly, loading modules i have include in site.pp file. site.pp: cat manifiests/site.pp node default { include ntp, motd } But it does not work if i run puppet agent. puppet agent --test --server=debianita.user.arinso --environment production Info: Retrieving plugin Info:

Hello All, I''m trying to start using external nodes under foreman, and I''m running into some issues. I have the entries in puppet.conf: [main] external_nodes = /etc/puppet/external_node.rb node_terminus = exec The enternal_node.rb script is the one that came with foreman: #!/usr/bin/ruby # a simple script which fetches external nodes from Foreman # you

Dear all, I have RedHat Server with Puppet and logging in /var/log/puppet But on Solaris it does not work. I am using the CSWpuppet3 3.3.1 Do you have an idea? cat /etc/puppet/puppet.conf # puppet.conf [main] logdir = /var/log/puppet confdir = /etc/opt/csw/puppet config = $confdir/puppet.conf vardir = /var/opt/csw/puppet ssldir = $vardir/ssl server =