similar to: Puppet agent on Solaris no logging

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

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

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

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

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

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

when a node tries to send a report it drops the following error: err: Reporting failed: undefined method `graph'' for #<Puppet::Transaction::Report:0xb7060948> on the server i have: reports = rrdgraph,store reportdir = /var/www/puppetreports rrddir = /var/www/html/rrd rrdinterval = $runinterval rrdgraph =

Hi all, I''m doing a new install of my puppet server and I''m doing it like: 1.-) adding epel repo: http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 2.-) yum -y install puppet-server 3.-) rm -rf /etc/puppet 4.-) copy my old puppet conf (from puppet-0.24.5 to 0.24.6) mv /etc/puppet.old /etc/puppet 5.-) start puppetmaster: [gridinstall etc]# /etc/init.d/puppetmaster start

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 all, I am trying to setup puppet master and puppetdb on same node using puppetdb module. When I try to run puppet agent -t, I see following erorr notice: Unable to connect to puppetdb server (ip-10-172-161-25.us-west-1.compute.internal:8081): SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed notice: Failed to connect to puppetdb; sleeping 2

In a recent post Nikola Petrov summerized methods for managing config files such as puppet.conf: * use augeas with virtual resources * use the concat module * use the standard template function with multiple arguments; look at http://docs.puppetlabs.com/guides/templating.html and scroll down to "Combining templates" I can add a few others: * use the ini_setting type

Hello Folks! I am trying to learn puppet. Installed the puppet 3.0.2 and configured one node as the master and the other as the client. Generated the certs and all that. But, I seem to be doing something wrong wrt to the init.pp file. Attached is exact error and my current server configuration. Any help in helping me fix this issue is appreciated: *[root@pupclient ~]# puppet agent --test*

the puppetmaster conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl reports = store, http, foreman reporturl = http://localhost:3000/reports/upload [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig the puppet client conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet

Hi everyone, Please help, I have built a new server and installed puppet (2.6.17) running on RHEL 6.3. It seems that it is not listening on port 8139. iptables -L: Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt

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

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

possibly related to (or the same as) issues 4830 and 2244, i''m getting errors when adding a custom fact and provider to a module to propagate to clients. am i missing something here? i tried the workaround of adding a fileserver.conf to the master (referenced below and in the tickets) with no change. thanks for any help. here''s a pile of details: puppetmaster 2.6.9 is running

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 =

Hi, I''m following http://reductivelabs.com/trac/puppet/wiki/PluginsInModules in order to use a custom fact. My modules looks like: # ls manifests/modules/network/ manifests plugins # ls manifests/modules/network/plugins/facter/primaryint.rb manifests/modules/network/plugins/facter/primaryint.rb as is said in doc. Then: Turn on pluginsync and specify factpath, so that the facts