On Thu, May 26, 2011 at 7:14 AM, elderdakkar <[email protected]> wrote:
> And this
> results in one problem on the puppet side: it seems, that
> Nagios_service <<||>> locks the config file and the Nagios_host <<||>>
> process can't write its config to the same file.
Is it a requirement that all puppet-written nagios configuration go
into the same file? Personally I do something like
@@nagios_host { $fqdn: target => "/etc/nagios/conf.d/nagios_host.cfg" }
@@nagios_hostextinfo { $fqdn: target =>
"/etc/nagios/conf.d/nagios_hostextinfo.cfg" }
@@nagios_service { "check_ping_$fqdn": target =>
"/etc/nagios/conf.d/$fqdn.cfg" }
@@nagios_service { "check_http_$fqdn": target =>
"/etc/nagios/conf.d/$fqdn.cfg" }
So my services are grouped by host, but other configuration types all
go into the same file.
That said -- if I had it to do again, I think I would assign my
services to hostgroups in a static cfg file, and just have puppet do
host configuration.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
