similar to: monitoring puppet

Hi, I am running puppet version 0.25.1 on both the server and client and am getting the following error on a puppet run: err: Could not apply complete catalog: Could not retrieve dependency ''Class[http]'' of Class[puppet::http] Class http is defined in the "http" module like so: class http { package { httpd: ensure => installed } file {

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

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

Hello, I try config puppet with foreman frontend. Into puppetmasterd I create modules "test" and create init.pp: # Create "/tmp/testfile" if it doesn''t exist. class test_class { file { "/tmp/testfile": ensure => present, mode => 644, owner => root, group => root } } Configure nodes in site.pp and import

I am experiencing a curious event, and wondering if others have seen this... As well, I have a question related to it. Today, I noticed my puppet summary report from Foreman this morning, that 60 of my 160 hosts all stopped reporting at nearly the exact same time, and have not since restarted. Investigating, it appears that my puppetmaster temporarily ran out of disk space on the /var

I''m playing around with foreman for the moment. I can''t seem to figure out how to make the dashboard look like in this screenshot http://theforeman.org/wiki/foreman/Screenshots#Dashboard In order for those statistics to work what should be done? I have activated the rrdgraph reports in puppetd, uncommented the line ":rrd_report_url: report/" in config/settings.yaml

Hi, I created a centOS6 EC2 instance last night and ran the foreman puppet module but it came back with a few years. Was hoping somebody could help me understand these errors. [root@ip-10-170-77-129 config]# echo include foreman | puppet --modulepath /root/puppet-foreman/ err: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml/foreman]/ensure: change from absent to directory failed:

I just started digging into puppet and it looks like puppet is using a pull model. You have a master server and clients talk to it to get config info. Is anyone out there using a push model? If not, why not? Are there security reasons you would use one over the other? It seems that cfengine also uses a push model, so I wondered if this is a "standard" or if there are specific

Hi, I have a Puppet Enterprise (2.0) puppetmaster running with Foreman, and having trouble getting it working as an External Node Classifier. In short, if I manually add a test client into site.pp, it will retrieve the proper catalog / classes, but I would like to avoid having to do that. I''m also using environments (production/testing/ development) as well, but think I have most of

I have a 3 different puppetmasters running different groups of machines (dev, testing, and production). I''d like to very simply say "Give me a brief summary of the status of the nodes you manage." I''ve been having nightmare dependency problems trying to get things like Dashboard running that seem to be able to do this (Ruby, which may be an elegant language, is very

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

Greetings: Sorry for cross-posting this question, but I haven''t gotten any love over on the Google Forum for Foreman users<https://groups.google.com/forum/#!forum/foreman-users> (their forum isn''t as active as this one). I only recently learned about The Foreman and I''d like to deploy it on a 64-bit Ubuntu 12.04 LTS workstation to provision/manage a bunch of

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

Hi guys, Unlike what it says in the documentation and the --help output, I can''t seem to get puppetd to use the --server setting. The only way I can get puppetd to work is to include a ''puppet'' alias to the ip of the machine I''m running puppetmasterd on in my hosts file. The strange thing though, is that the logs of my puppetmaster show that it *is* getting

After an unexpected and unreasonably long hiatus, I''ve finally returned to implementing Puppet in my environment. My puppetmaster: Puppet 0.25.4, Facter 1.5.7, Ruby 1.8.7, and FreeBSD 8.0. I''ve got five clients using the puppetmaster so far. After about 24 hours, I''ve got three puppetmaster processes running. This number continues to grow over time. If stored configs

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

Hi I''m in the process of looking for a way to have developers deploying on their test systems without intervention of sysadmins, to solve this i''d like to use Puppet (either the OSS version or Enterprise, whichever solves the problem). I can manage to only grant access to certain systems and limit the ability to execute puppetd --test, however, the developers would like to

Hi, installing puppet at my first site was quite easy (not w/o problems, but still). At the second site, I''ve run into something more serious. First things first - I install puppetmaster on existing server, used to keep LDAP db (my puppetmaster DOES NOT use LDAP, it just tries to coexist on the same machine). The thing is, I need to puppet this baby, so I''m running into a

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

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911