Puppet users - Jun 2009 - Exporting and collecting resources on the multiple hosts problem

Hi,

I''m using puppet to generate nagios configs in what I guess is the
''usual'' way; by having each host export config a files for
each nagios
check using  @@file {...tag=nagios...}, which are then collected onto
the nagios server with File <<|tag == ''nagios'' |>>


I have two nagios servers, and I want each of them to collect all of
the config files.

The nagios servers also define nagios checks of their own (having two
means they can check each other, which is handy).

Now, what''s strange is that the nagios servers don''t appear
collect
each others'' checks. So each nagios server gets the checks for itself,
and for all the other non-nagios servers, but not for the other
nagios.

Looking in the database, it seems that the nagios config file
resources, on both  servers, are marked as "exported=0". So they
appear on their own server by virtue of being ''real'' 
resources,
despite being defined with @@file...

I guess this is something to do with the fact that the same node is
exporting the resource and collecting it - could this somehow cause
puppet to think that, since the resource is being collected locally,
it doesn''t need to be exported?

Is there a way around this?

Thanks

Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi,

On which version of puppet is running on your puppetmaster?
Various versions had some issues with exported/collected resources (0.24.7
was one of them, if I remember correctly).

On Thu, June 11, 2009 13:44, Chris wrote:
>
> I''m using puppet to generate nagios configs in what I guess is the
> ''usual'' way; by having each host export config a files
for each nagios
> check using  @@file {...tag=nagios...}, which are then collected onto
> the nagios server with File <<|tag == ''nagios''
|>>
Yes, this looks like pretty standard.
> I have two nagios servers, and I want each of them to collect all of
> the config files.
No issue, each one has to File <<||>>.
> The nagios servers also define nagios checks of their own (having two
> means they can check each other, which is handy).
>
> Now, what''s strange is that the nagios servers don''t
appear collect
> each others'' checks. So each nagios server gets the checks for
itself,
> and for all the other non-nagios servers, but not for the other
> nagios.
>
> Looking in the database, it seems that the nagios config file
> resources, on both  servers, are marked as "exported=0". So they
> appear on their own server by virtue of being ''real'' 
resources,
> despite being defined with @@file...
This really looks like one of the issue in 0.24.7.
> I guess this is something to do with the fact that the same node is
> exporting the resource and collecting it - could this somehow cause
> puppet to think that, since the resource is being collected locally,
> it doesn''t need to be exported?
>
> Is there a way around this?
If you''re running a version affected, upgrade to the 0.24.8 version on
your master.

-- 
Brice Figureau
Days of Wonder


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

> If you''re running a version affected, upgrade to the 0.24.8
version on
> your master.
>
Ah, that would explain it.  I''m running the version that comes with
OpenCSW (the solaris package repo.), which is currently at 0.24.7.
I''ll see if there are any plans to upgrade that in the near future,
and if not, I''ll see about doing a re-install from source.

Thanks!

Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---