On May 26, 6:14 am, elderdakkar <[email protected]> wrote: > Hello > > i'm managing nagios with exported ressources. > i have some @@nagios_host a lot of @@nagios_service ressources. > Collecting the ressouces itself works fine with Nagios_host <<||>> and > Nagios_service <<||>>. > > BUT :D > > i have a "special" nagios configuration layout: every host has its own > cfg file with the depending servicechecks. This means i have ONE file > with one host definition and all checks for this single host. 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. The means: the first > run writes some of the exported ressources to the nagios cfg. The > restart of nagios fails, because some of the hosts aren't written to > the cfg. The next run does the rest and nagios restarts successful. > > Is there a way, to force puppet to start the collection of > Nagios_service <<||>> after Nagios_host <<||>> finishes? > Some kind of dependency? > > i already tried chaining like: > Nagios_host <<||>> -> Nagios_service <<||>> , but then the puppetrun > does nothing.
I cannot solve your problem, but for the record, the only way I can imagine the exported resource angle factoring into it is if you have a resource title crash among the resources you are trying to collect. Otherwise, you should have the same behavior with collected resources as you would have if you declared all the same resources locally. John -- 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.
