You're right, I removed all /var/lib/puppet/* from the client except
the ssl directory and the next poll worked.
Still requires me to have a default node though on the puppetmaster.
Should the client really cache bad catalogs?
2009/9/28 Nicolas Szalay <nsza...@qualigaz.com>:
> Le lundi 28 septembre 2009 à 10:52 +0100, Matt a écrit :
>> Update:-
>>
>> I added a default node to a manifest file, just -
>>
>> node default {
>> include env
>> }
>>
>> This appears to have made the puppetmasterd kick in to action and
>> compile the catalog from the foreman for that node. i.e. I see
>> puppetmasterd compile all the correct classes for the node and not
>> just the default one.
>>
>> notice: Compiled catalog for sl01.domain.sl in 0.14 seconds
>>
>> But the client is still giving -
>> warning: Not using cache on failed catalog
>> err: Could not retrieve catalog; skipping run
>
>
> Looks like your YAML is invalid
>
>> > manually -
>> > # su - puppet
>> > -bash-3.2$ cd /etc/puppet
>> > -bash-3.2$ ./node.rb sl01.domain.sl
>> > ---
>> > parameters:
>> > s3: "false"
>> > puppetmaster: sl02.domain.sl
>> > java: jre16007
>> > domainname: domain.sl
>> > classes:
>> > - env
>> > - ganglia
>> >
>
> ./scripts/ext_node.rb fluor.XXX
> ---
> classes:
> - mount::webserver::pool
> - webserver::pool
> - webserver::zend
> - common
> parameters:
> wwwpool: pool1
>
> Nico.
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
