> 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
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,
requi
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
On 08.12.2009 17:53, Rus Hughes wrote:
> Hi,
>
> We're using thin stored configs heavily to manage things like Munin
> and Nagios and we're currently wondering what to do when nodes go
> away, or change considerably.
>
> If we get rid of a server then all it's stored config is still present
> in th
Hi,
We're using thin stored configs heavily to manage things like Munin
and Nagios and we're currently wondering what to do when nodes go
away, or change considerably.
If we get rid of a server then all it's stored config is still present
in the database, as well as it's nagios and munin configur
