Also you can use puppetdb on every master and configure PostgreSQL streaming replication. Then use database and read-database puppetdb options in database.ini to configure puppetdb for read and write.
On Sunday, February 28, 2016 at 2:39:33 AM UTC+3, robert.davidson wrote: > > I'm quite certain that there's something in the documentation that I'm > missing here. (It has all the hallmarks of an Own Damn Fault situation.) > Nonetheless, as I'm getting nowhere, I figure I'll fling out a cry for > help. > > How do you configure puppetdb so it will permit multiple puppetmasters to > talk to it? The only master that can successful submit facts/reports is the > one that the puppetdb machine was puppeted from. > All others get (hostnames stripped out, of course): > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > Failed to submit 'replace facts' command for $HOSTNAME to PuppetDB at > $PUPPETDBHOSTNAME:8081: SSL_connect returned=1 errno=0 state=SSLv3 read > server certificate B: certificate verify failed: [unable to get local > issuer certificate for /CN=$PUPPETDBHOSTNAME] > > > What incredibly obvious thing have I overlooked entirely? > > -- > Robert Davidson > > > -- 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/7b37b8e0-6281-48d8-a16b-71c9da776669%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
