similar to: puppet enterprise

Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

My class reads like: class name1::name2 ($gidvariable) { file { "somepath-to-file": ensure => file, mode => ''0640'', gid => $gidvariable, } } The problem is that the file isn''t getting set to the $gidvariable''s value which is a string "abc". The other things work (presence as file, mode). Stuart -- You

Hi, When I put noop = true in /etc/puppet/puppet.conf on the node in question, I observe no changes. Great. Good But also, I see because of report = true absolutely zero information in the yaml regarding what would have been changed. Is there an equivalent to the above for "test = true" or must I alter the rc file to include --test ? Thanks ahead Puppet wizards!!! -- You

somefile.pp class mumble { } class mumble::testcontents inherits mumble { file { "/tmp/testfile": path => "/tmp/testfile, ensure => present, mode => 0640, content => "I am a test file.", puppet parser validate passed it. puppet apply says it is run yet no /tmp/testfile appears the puppet master is running and this is being

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

Hi, I put a --noop into the rc file for puppet client and restarted it and watched it log the above message. My problem with the above message is it doesn''t give enough detail as to what was discovered and what the 2 events were (mode difference, file existence, etc.) Is there a way to up the logging level for a puppet agent --noop observation run? I tried adding --verbose in the rc

Hi all, Using Puppet 2.5, I have a class which creates users: # cat modules/users/manifests/init.pp class users { user { ''ringo'': ensure => present, uid => ''1506'', groups => [''admin''], shell => ''/bin/bash'', home => ''/home/ringo'', managehome

Hi everybody! So for non-automated physical/manual application of single specific patterns or sets of puppet patterns on an entirely manual basis, what is best practice and/or where is it described? Meaning what is the way to stop the puppet agent from running automatically and instead require a manual command for puppet to exercise on that node. If it is as simple as puppet apply

Dear readers, I was shocked to see that "puppet kick" will be deprecated in 3.0.0 https://projects.puppetlabs.com/issues/15735 How can MCollective replace "puppet kick"? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit

I''ve installed the puppet labs lvm module. After fixing the missing "}" at line 20 in init.pp (really?!?!), I''m getting this:'' err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type physical_volume at /truth/sauce/env/prod/modules/role/manifests/common.pp:43

Puppet 3.0.0-rc5 is a feature release candidate for the 3.x series of Puppet. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc5.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available at http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.0.rc5.gem or by using `gem install --pre

Seems like nodes are matching the default node before they are matching the more specific nodes. My site.pp has: include "nodes/*.pp" In the nodes directory are two files, default.pp and nagios_server.pp. default.pp: node default { include role::common } nagios_server.pp: node ''mon01.us1.xxx.com'' { $node_env = "production" include

So I was looking at the type reference, and noticed that for a lot of the types, no namevar was listed. When I checked the types in the code, for each of those omissions, the namevar was simply "name". Now, it might be self evident that this is the case, but a little documentation couldn''t hurt, If not in each type, at least in the section where it describes what namevars

Hi, I needed a function to check if a file is existing on the Debian box I am configuring. So I used this one module Puppet::Parser::Functions newfunction(:file_exists, :type => :rvalue) do |args| if File.exists?(args[0]) return 1 else return 0 end end end It work greats for some service where apache2 doesn''t work for me. I am using it this way

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet and it''s caused the odd issue we have to fix in the Mac pkg preflights. After re-reading ''man hier'' I''m tempted to change the default on OS X to: /var/db/puppet instead. /var/ multi-purpose log, temporary, transient, and spool files ...

Dear community, I use puppet to deploy iptables on every server. This is working fine. In the manifest I defined an iptables service which leads to my init script. The thing is each time I run puppet I got : notice: /Stage[main]/Iptables/Service[netfilter]/ensure: ensure changed ''stopped'' to ''running'' I would like to add a status command to my startup script

I have a freshly installed and updated CentOS 5.4 system running puppet 0.25.5. I followed the passenger docs here: http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger Upon starting the client, the following appears in the apache error log. [Thu Jun 24 10:48:40 2010] [error] [client 10.10.4.45] Premature end of script headers: production [ pid=6785 file=ext/apache2/Hooks.cpp:706

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package

I''m trying to find email addresses of some of the speakers from Puppet Conf last week. They aren''t on the web site... maybe due to spamming concerns. Short of Googling, how can I get these? Also... are there slides available yet? What about video? Doug -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this