The use case i try to illustrate is when to declare some item (eq
mysqld service) with a default configuration that could be included on
every node (class stripdown in the example, for basenode), and still
be able to override this same item in some specific class (eg
mysql::server), to be included
We are using the puppet built in mechanisms with Nagios and that
concatenated_file.pp for Munin, that puppetstoredconfigclean.rb script
works like a charm, but I'm still having difficulty purging the now
unmanaged elements. Puppet isn't removing any of the unmanaged files
from the filesystem so con
Hello,
I am facing a little problem(?) with foreman. I have enabled
"reports=foreman,rrdgraph,store" on the puppetmaster. And, I can see the
reports in foreman as well, except for the RRD Graphs.
However, I can see "/var/puppet/rrd" being populated every time any client
runs the configuration, I
Andrew Schulman wrote:
> To me it seems like more specialized material that should go in the reference
> rather than the tutorial. But wherever it goes best is fine with me.
Well, the Language Tutorial *is* the reference manual for the language.
There's no other document giving a more in-depth
Ok, I've managed to 'fix' this issue by, on each puppet run, forcing
/etc/munin/puppet to purge and empty itself before collecting
file { "/etc/munin/puppet":
ensure => directory,
owner => munin,
group => munin,
mode=> 755,
requi
Hi,
I'm guessing that you went through
http://theforeman.org/wiki/foreman/Puppet_RRD_Graphs.
how do you access your rrd graphs directly? did you notice the apache alias
statement?
the rrd_report_url: settings (in config/settings.yaml) should point to the
relative url from your puppetmaster.
ch
On 09.12.2009 12:35, LOhit wrote:
> Hello,
>
> I am facing a little problem(?) with foreman. I have enabled
> "reports=foreman,rrdgraph,store" on the puppetmaster. And, I can see
> the reports in foreman as well, except for the RRD Graphs.
>
> However, I can see "/var/puppet/rrd" being populated
On 09.12.2009 11:44, Alexandre wrote:
> The use case i try to illustrate is when to declare some item (eq
> mysqld service) with a default configuration that could be included on
> every node (class stripdown in the example, for basenode), and still
> be able to override this same item in some spec
http://groups.google.com/group/puppet-users/browse_thread/thread/b6378c7df1e9356f/3d224f60ff762ec8?#3d224f60ff762ec8
cheers,
Ohad
On Wed, Dec 9, 2009 at 7:46 PM, Rus Hughes wrote:
> Ok, I've managed to 'fix' this issue by, on each puppet run, forcing
> /etc/munin/puppet to purge and empty itse
> Ok, I've managed to 'fix' this issue by, on each puppet run, forcing
> /etc/munin/puppet to purge and empty itself before collecting
>
> file { "/etc/munin/puppet":
> ensure => directory,
> owner => munin,
> group => munin,
> mode=> 755
On Dec 9, 1:25 am, David Schmitt wrote:
> If you can detect from the facts that an erreneous situation is
> ocurring, you could change the environment at the node level or in an
> external node script.
Or, if you can know from the facts presented (or otherwise) what the
correct provider is, but
On Dec 9, 6:27 am, Silviu Paragina wrote:
> Not tested but it should be like
>
> class stripdown {
> include mysql::server
> *S*ervice {"mysql": enable => "false", ensure => "stopped" }
>
> }
>
> Check the language tutorial for overriding. Note that is a big "S" not a
> small "s".
As
I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any
ideas?
Sanitized facter output:
architecture => i386
domain => missyou.edu
facterversion => 1.5.7
fqdn => broken.missyou.edu
hardwareisa => i686
hardwaremodel => i686
hostname => broken
id => root
interfaces => eth0,sit0
ipad
do you have the lsb packages installed? :) (e.g. redhat-lsb)
Ohad
On Wed, Dec 9, 2009 at 10:51 PM, Len Rugen wrote:
> I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any
> ideas?
>
> Sanitized facter output:
>
> architecture => i386
> domain => missyou.edu
> facterversion =>
On 09.12.2009 09:25, David Schmitt wrote:
>
> If you can detect from the facts that an erreneous situation is
> ocurring, you could change the environment at the node level or in an
> external node script.
>
>
> Regards, DavidS
>
You mean something like
node problem
{
if (condition)
{
> I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any
> ideas?
do you have redhat-lsb installed?
cheers pete.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.co
On 09.12.2009 16:28, jcbollinger wrote:
> As far as I know, overriding only works in a subclass, so it would
> need to be:
>
> class stripdown inherits mysql::server {
> Service { "mysqld": enable => "false", ensure => "stopped" }
> }
>
>
> Obviously, that's messy and it doesn't scale for mu
On Mon, 07 Dec 2009 17:09:41 -0500 Joe McDonagh
wrote:
> It would be nice if we could preseed the puppet installation package
> with some values. This way during boot up, preseeding
> debian-installer, I could also preseed the puppet package to start in
> a certain environment. Beyond that you
Hi All,
I'm looking to clean up the way I deploy packages to OS X clients. I
have a puppetmaster and a webserver that hosts installation .pkg files
at every site in our district. I've been using variations of the
pkg_deploy.pp file that utilizes the pkgdmg provider: Here's the
file:
define pkg
resource defaults for OS X clients
Package { ensure => installed, provider => pkgdmg }
Then we have a fact called "pkgbase" that sets the http server the
packages are delivered from for various locations with a fallback to
the default location. We also make use of variables so
that was it... thanks.
On Wed, Dec 9, 2009 at 9:04 AM, Ohad Levy wrote:
> do you have the lsb packages installed? :) (e.g. redhat-lsb)
>
> Ohad
>
> On Wed, Dec 9, 2009 at 10:51 PM, Len Rugen wrote:
>
>> I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any
>> ideas?
>>
>>
During puppet catalog runs, I sometimes (~ 10%) get the following
message:
Failed to retrieve current state of resource: SSL_connect SYSCALL
returned=5 errno=0 state=SSLv2/v3 read server hello A
Has anyone else ran into this? I am running puppet 0.25.1 on Solaris
9 and 10. Let me know what othe
I've uploaded version 0.2 of ssh::auth to
http://reductivelabs.com/trac/puppet/wiki/Recipes/ModuleSSHAuth .
Version 0.2 is a bug fix release. It fixes a variable inheritance problem that
caused clients and servers to not be able to install keys.
ssh::auth is a Puppet module that provides centr
http://projects.reductivelabs.com/issues/2909
I am getting in console
r...@tbagchi-desktop:/home/tbagchi# puppetmasterd --debug --no-
daemonize --logdest console
/usr/local/lib/site_ruby/1.8/facter/util/resolution.rb:46: warning:
Insecure world writable dir /usr/bin in PATH, mode 040777
/usr/loca
24 matches
Mail list logo
