Hello puppet gurus, maybe one of you can help with this. We have a
bunch of servers that are managed by puppet, but would like to make a
single, small change to a text file only on newly built machines.
This text file is controlled by a module that is referenced in several
places in our current co
> You can just create a new class that inherits your previous class
> and then overwrites the File[] you declared before and use that
> only on the new machines.
Will this also work with an augeas entry with a changes [] section?
--
You received this message because you are subscribed to the Goo
We are seeing this error in our log files on some clients:
puppetd[15068]: Could not run Puppet configuration client: undefined
method `initvars' for #
Where do I begin troubleshooting this? The client software versions are:
ruby-1.8.5-5.el5_4.8.x86_64
ruby-libs-1.8.5-5.el5_4.8.x86_64
ruby-shad
On Tue, Jul 26, 2011 at 11:44 AM, Tony G. wrote:
> Try enabling debug and trace on your agent, that will provide more details.
Ok, we gave this a shot. Here's the output with --debug and --trace turned on:
/var/lib/puppet/lib/puppet/type/package.rb:316:in `initialize'
/usr/lib/ruby/site_ruby/1.
We have an issue where sometimes servers get assigned serial number
"0x" in the inventory.txt file. This causes major problems
including SSL cert errors in the log file. Anyone know how to
properly rebuild inventory.txt without tearing everything out and
starting from scratch?
--
You receiv
> 0x is typically the CA cert, was the inventory.txt file blank when
> this occurred? If you have all the certificates, you can use puppet
> cert -pa and extract the serial number, date, and CN info. I'm not
> sure if there's an automated way using openssl commands. This might be
> reasonably c
I have inherited some puppet configurations; there is an exec resource
that looks like this:
exec { "force-reload-httpd":
command => "/etc/rc.d/init.d/httpd force-reload",
refreshonly => true,
}
Should this be paired with a "subscribe" or "notify" somewhere?
--
You received this message bec
Maybe one of you can help with this. I have a class that's got a
file{} type directive in it. It populates /etc/security/limits.conf
with specific settings. I have a small handful of hosts where we want
to manage /etc/security/limits.conf manually. Is there a simple way
to tell puppet to exclud
> You don't say what version of puppet you're using, whether you're using
> an ENC, or whether you're already using either extlookup() or hiera(),
> so it's really difficult to suggest something that integrates well with
> your current environment.
Sorry I didn't provide more detail. We're using
> It's not really the cleanest-looking thing, but the easiest option for
> your particular case is to wrap the file resource in an if statement
> like this:
> if (! $::security_limits_disabled) {
> file { '/etc/security/limits.conf':
> ...
> }
> }
Thanks, this is just what I was
>> It's not really the cleanest-looking thing, but the easiest option for
>> your particular case is to wrap the file resource in an if statement
>> like this:
>> if (! $::security_limits_disabled) {
>> file { '/etc/security/limits.conf':
>> ...
>> }
>> }
>
> Thanks, this is just
It's not really the cleanest-looking thing, but the easiest option for
your particular case is to wrap the file resource in an if statement
like this:
if (! $::security_limits_disabled) {
file { '/etc/security/limits.conf':
...
}
}
Super, thanks
> This has been extremely useful in my environment when importing the odd
> 'unique snowflake' type server quickly without having to make any code/logic
> changes or introduce large numbers of ENC values to disable certain
> functionality or alter the flow of your puppet code.
Yes. Puppet doesn't
13 matches
Mail list logo
