Thanks for the tips Trevor. I did make the change on the puppet server, but my clients are still complaining:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to execute '/pdb/cmd/v1?checksum=5c49765a6d1ef8e77fa85c53f70e9f572615463e&version=4&certname=it-lnx-01.myhost.com&command=replace_facts' on at least 1 of the following 'server_urls': https://puppetmaster.myhost.com:8081 any idea how I can clean that up, or why its happening? On Saturday, June 11, 2016 at 12:54:19 PM UTC-7, Trevor Vaughan wrote: > > Hi James, > > The puppetdb module should take care of your DB certs. However, if it > doesn't, or something goes wrong, you will need to fix the DB certs > manually. > > Also, if you update your Puppet certificates, the PuppetDB module will > *not* notice and you'll need to erase the existing certs and run the > manifests again. > > Of course, the puppet server is probably tied to your DB and you'll need > to disconnect the two before Puppet will run cleanly again. > > Remove any mention of 'puppetdb' from puppet.conf as well as deleting your > routes.yaml file (if PuppetDB is the only thing in there). Restart the > puppet server and things should work again. > > Trevor > > On Fri, Jun 10, 2016 at 11:36 PM, jdehnert <jdeh...@gmail.com > <javascript:>> wrote: > >> Greetings All, >> >> I decided to try and implement the puppetlabs-puppetdb and >> puppetlabs-postgres modules after I had both puppetdb and postgres >> installed and working on my puppet server. This was ill advised as it >> broke my working setup and no amount of re-configuring seems to be able to >> get things working again. >> >> I finally pulled the manifest that "describes" my configuration, but now >> I cannot seem to get puppetdb working at all. My clients are giving me >> these kind of errors: >> >> Error: Could not retrieve catalog from remote server: Error 400 on >> SERVER: Failed to execute >> '/pdb/cmd/v1?checksum=2b3883d84fd2c7f9899bd6280247edbccc31cf15&version=4&certname= >> it-lnx-01.myhost.com&command=replace_facts' on at least 1 of the >> following 'server_urls': https://puppetmaster.myhost.com:8081 >> Warning: Not using cache on failed catalog >> Error: Could not retrieve catalog; skipping run >> >> I have crawled through the puppet docs to try and fix my configurations, >> but I can't seem to get things operating properly. >> >> It seemed pretty clear that I did not need to configure the SSL portion >> of puppetdb, but these errors seem to be flying the the face of what I read. >> >> Do I need to configure SSL for puppetdb to get it to work? and What's >> my best chance of getting things working again. Start from scratch, or am >> I just overlooking something from my configs.? >> >> Thanks, >> jdeh...@gmail.com <javascript:> >> >> >> -- >> 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...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/1f1b527d-9637-4ec4-b214-adf51555927e%40googlegroups.com >> >> <https://groups.google.com/d/msgid/puppet-users/1f1b527d-9637-4ec4-b214-adf51555927e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Trevor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 x788 > > -- This account not approved for unencrypted proprietary information -- > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ac8e8d16-7dbd-48ab-8696-dcc70ac9330f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
