>> Also your routes.yaml doesn't match the documentation I gave you >> either, nor should you be setting thin_storeconfigs any more as stated >> in another section. > > Yeah, but if I remove the section for catalog, I don't get "replacing > catalogs" in puppetdb log... But since my initial problem was wrong section > name in puppet.conf, maybe I can do without storing catalog cache in > puppetdb? Because, things work as a charm now that [puppetmasterd] is > renamed to [master]
This should be the case, take a look here: https://gist.github.com/4706585 You can see without those lines in routes.yaml it still sends a replace catalog. You simply shouldn't need that part. If for some reason you do, then something isn't right, and we are probably better to drill into the 'why' now rather than later :-). Please, if you can take a second look, and try removing the lines to confirm that would be appreciated. I just simply cannot replicate your case. > BTW documentation says that thin_storeconfigs must be set to false or > removed, mine were set to false so that was OK I presume. Okay, fair enough. > Thank you very very much... what a bad typo on my side :-/ No problemo :-). ken. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
