I overlooked the puppetmasterd syslog (*headslap*) which gave me the key piece of information I needed: the classifier did not have permissions to read my SQLite database.
It would have been useful to have this error message passed on to puppetd: Apr 15 16:39:23 newinstance puppetmasterd[7949]: Could not retrieve external node information for 01.web.test: Execution of '/usr/local/etc/puppet/bin/puppet_node_classifier 01.web.test' returned 255: DBI connect( I'll submit a ticket but will also understand the logic if it gets rejected. Thanks once again for your reply, the key for me was running puppetmasterd in --debug --no-daemonize mode, and then I retroactively went and looked at logs for the message I figured must be there, and it was. Pete On Wed, Apr 15, 2009 at 9:30 AM, Peter Meier <peter.me...@immerda.ch> wrote: > > Hi > > > I'm stuck. All of my puppet clients in my dev environment are reporting > this > > when I do a manual run: > > > > # /usr/sbin/puppetd --server=03.admin.demo.nym1 --test > > err: Could not retrieve catalog: Could not find node '01.web.test'; > cannot > > compile > > warning: Not using cache on failed catalog > > > > Is there a good document that describes tricks of the trade in order to > > figure out what the problem is? > > > > I've added a debug flag to the puppetd call, and don't see any additional > > useful info (or at least to *my* eyes): > > > > debug: Loaded state in 0.01 seconds > > debug: Retrieved facts in 0.13 seconds > > debug: Retrieving catalog > > debug: Calling puppetmaster.getconfig > > err: Could not retrieve catalog: Could not find node '01.web.test'; > cannot > > compile > > warning: Not using cache on failed catalog > > > puppet takes either the catalog for the node or the one for the default > node. And this error tells me that no catalog could be found for the > node 01.web.test nor the default. > So you have to define at least one of these. Every nodes get an error > with '01.web.test'? could you check the fqdn of facter etc. on the host? > > Regarding the error message and if it really was a problem of a not yet > declared node, I agree that this message could be improved. > Would you have thought about this possibility if the error message was > like: "Could not find a catalog for node '01.web.test'; cannot compile" > or what would be a an appropriate message? > Please file a ticket, if you find a better one, so it can be imroved. > > > What are the tools / commands that people use to debug and figure out > what > > to my eyes are cryptic error messages? > > logs of the puppetmaster might give you as well some hints. maybe run it > as well with --debug. > > cheers pete > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
