On Tuesday, November 27, 2012 8:55:47 PM UTC-6, go8ose wrote:
>
> 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.
>
So you're saying that *none* of the collected Execs are running? In that
case, check the cached catalog to see whether it contains those Execs at
all. That will establish whether it is a problem with resource collection
or with the individual resources. It should also allow you to verify the
resource parameters.
As for the individual resources, you would be well advised to use curly
brackets around variable names inside strings. Especially, you should use
them in "/srv/mnt/.${hostname}_commvault_backed_up" and similar strings
(else Puppet will think you want the variable named
$hostname_commvault_backed_up), but it's a good habit to use curly brackets
in every variable reference.
Actually, the brackets are probably your issue: you presumably don't define
a variable named $hostname_commvault_backed_up, so it interpolates as
nothing. That means what you've written is equivalent to "creates =>
'/srv/mnt/.'", which is in turn equivalent to "creates => '/srv/mnt'".
Since that directory already exists, applying the Execs will not result in
their commands running.
John
--
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/-/57dgbGqke24J.
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.
