On Tuesday, November 27, 2012 2:56:45 AM UTC+11, jcbollinger wrote: > > This looks like http://projects.puppetlabs.com/issues/11049. You can > vote for that issue. To work around the it, I think you'll need to arrange > for the host that collects those resources to declare its own > nagios_service and nagios_host resources as ordinary instead of exported > resources. Of course, that's a bust if more than one node needs to collect > those resources. > > There are probably other workarounds, but they depend on details of your > site. Many of them involve substituting something else for exported > resources; the rest involve collecting onto a node that does not export > (and therefore is not affected by the bug), and then sharing the result > somehow. > > > John > > Thanks for the reply John. I think the bug report you mention (but 11049) isn't relevant for my situation. Perhaps I shouldn't have mentioned my working nagios resources in my original post. They aren't part of my problem, they are just illustrating that I have some exported resources and collection working.
In my situation I want to collect the exec's on a different host to the hosts that are exporting these execs. I've got some working exports (the nagios ones, and some local definitions involving NFS mounts), but my exec exports aren't working, and I don't know why. Cheers, Geoff -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/lNbGegRSGkYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
