OK So I'm doing something silly here, but this is the behaviour I'm seeing. I am instatiating a large number of virtual @nagios_host objects and @nagios_service objects. Then at run time I see the Nagios_service objects get propagated but it appears like it selects one of the Nagios_host objects. Of course the nagios config fails. If I restart the puppetmaster it will then select the next nagios object in turn. So the nagios_service.cfg is being completely built but nagios_host.cfg gets a only one host added per puppet run.
Maybe I am instatiating virtual resources with the same name? I have looked through the manifests and can't see how this is possible. I also see DNS entries only come through one at a time. So you see: [r...@c008operations01-prod nagios]# puppetd --test info: /Host[c008lvs01-prod]: Adding aliases "c008lvs01-prod.threatmetrix.com " info: /Nagios_host[c003fp02-prod]: Adding aliases "c003fp02-prod" info: /Host[localhost]: Adding aliases "localhost.localdomain" info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run That should be filled with lots of Host[] and Nagios_host[] objects, yet there is only two. Using puppet 0.24.5 on Centos 5.3 Thanks for your help Joel --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
