Hi all,
I''ve hit a wall trying to get external nodes working on our production
puppet master. I''m using the foreman to supply the external nodes
information and have it all working in the dev environment.
I''ve started all processes in debug - running Puppet 0.25
puppetd -
debug: Puppet::Network::Format[json]: false value when expecting true
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find default node or by name with ''sl01.domain.sl,
sl01.domain, sl01'' on node sl01.domain.sl
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
puppetmasterd -
info: Not using expired node for sl01.domain.sl from cache; expired at
Mon Sep 28 09:28:47 +0100 2009
debug: Executing ''/etc/puppet/node.rb sl01.domain.sl''
info: Caching node for sl01.domain.sl
....
err: Could not find default node or by name with ''sl01.domain.sl,
sl01.domain, sl01'' on node sl01.domain.sl
err: Could not find default node or by name with ''sl01.domain.sl,
sl01.domain, sl01'' on node sl01.domain.sl
foreman -
Processing HostsController#externalNodes (for 127.0.0.1 at 2009-09-28
09:39:30) [GET]
Parameters: {"fqdn"=>"sl01.domain.sl",
"action"=>"externalNodes",
"controller"=>"hosts"}
Completed in 9ms (View: 0, DB: 1) | 200 OK
[http://localhost/hosts/externalNodes?fqdn=sl01.domain.sl]
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
Anyone have any idea how I can find out whats going on?
The only difference I can see between the production and dev boxes is
that the production box uses certdnsnames, as it has both external and
internal clients -
certname=sl02.domain.com
certdnsnames=sl02.domain.com:sl02.domain.sl
Thanks,
Matt
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Matt schrieb:> Hi all, > > I''ve hit a wall trying to get external nodes working on our production > puppet master. I''m using the foreman to supply the external nodes > information and have it all working in the dev environment. > > 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 > - gangliaMaybe it is just a typo in this mail, but the classes (env and ganglia) should be indented to be a valid yaml list as value for the classes key. regards Christian
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
2009/9/28 Matt <mattmoran76@gmail.com>:> Hi all,
>
> I''ve hit a wall trying to get external nodes working on our
production
> puppet master. I''m using the foreman to supply the external nodes
> information and have it all working in the dev environment.
>
> I''ve started all processes in debug - running Puppet 0.25
>
> puppetd -
> debug: Puppet::Network::Format[json]: false value when expecting true
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find default node or by name with
''sl01.domain.sl,
> sl01.domain, sl01'' on node sl01.domain.sl
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>
> puppetmasterd -
> info: Not using expired node for sl01.domain.sl from cache; expired at
> Mon Sep 28 09:28:47 +0100 2009
> debug: Executing ''/etc/puppet/node.rb sl01.domain.sl''
> info: Caching node for sl01.domain.sl
> ....
> err: Could not find default node or by name with ''sl01.domain.sl,
> sl01.domain, sl01'' on node sl01.domain.sl
> err: Could not find default node or by name with ''sl01.domain.sl,
> sl01.domain, sl01'' on node sl01.domain.sl
>
> foreman -
> Processing HostsController#externalNodes (for 127.0.0.1 at 2009-09-28
> 09:39:30) [GET]
> Parameters: {"fqdn"=>"sl01.domain.sl",
"action"=>"externalNodes",
> "controller"=>"hosts"}
> Completed in 9ms (View: 0, DB: 1) | 200 OK
> [http://localhost/hosts/externalNodes?fqdn=sl01.domain.sl]
>
> 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
>
>
> Anyone have any idea how I can find out whats going on?
>
> The only difference I can see between the production and dev boxes is
> that the production box uses certdnsnames, as it has both external and
> internal clients -
> certname=sl02.domain.com
> certdnsnames=sl02.domain.com:sl02.domain.sl
>
> Thanks,
>
> Matt
>
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
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 runLooks 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''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 <nszalay@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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Matt, Thats a bit odd, when using external nodes you shouldn''t need any node definitions within your manifests. any chance you have some leftover nodes definitions? Ohad On Mon, Sep 28, 2009 at 5:52 PM, Matt <mattmoran76@gmail.com> wrote:> > 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 > > > > 2009/9/28 Matt <mattmoran76@gmail.com>: > > Hi all, > > > > I''ve hit a wall trying to get external nodes working on our production > > puppet master. I''m using the foreman to supply the external nodes > > information and have it all working in the dev environment. > > > > I''ve started all processes in debug - running Puppet 0.25 > > > > puppetd - > > debug: Puppet::Network::Format[json]: false value when expecting true > > err: Could not retrieve catalog from remote server: Error 400 on > > SERVER: Could not find default node or by name with ''sl01.domain.sl, > > sl01.domain, sl01'' on node sl01.domain.sl > > warning: Not using cache on failed catalog > > err: Could not retrieve catalog; skipping run > > > > puppetmasterd - > > info: Not using expired node for sl01.domain.sl from cache; expired at > > Mon Sep 28 09:28:47 +0100 2009 > > debug: Executing ''/etc/puppet/node.rb sl01.domain.sl'' > > info: Caching node for sl01.domain.sl > > .... > > err: Could not find default node or by name with ''sl01.domain.sl, > > sl01.domain, sl01'' on node sl01.domain.sl > > err: Could not find default node or by name with ''sl01.domain.sl, > > sl01.domain, sl01'' on node sl01.domain.sl > > > > foreman - > > Processing HostsController#externalNodes (for 127.0.0.1 at 2009-09-28 > > 09:39:30) [GET] > > Parameters: {"fqdn"=>"sl01.domain.sl", "action"=>"externalNodes", > > "controller"=>"hosts"} > > Completed in 9ms (View: 0, DB: 1) | 200 OK > > [http://localhost/hosts/externalNodes?fqdn=sl01.domain.sl] > > > > 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 > > > > > > Anyone have any idea how I can find out whats going on? > > > > The only difference I can see between the production and dev boxes is > > that the production box uses certdnsnames, as it has both external and > > internal clients - > > certname=sl02.domain.com > > certdnsnames=sl02.domain.com:sl02.domain.sl > > > > Thanks, > > > > Matt > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---