The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
2-space indent in puppetdb.conf confuses puppet
|Keywords:||Affected PuppetDB version:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
This is on puppetdb-0.9.0-1.el5 with a centos 5 master running PE 2.5.0
I had a puppetdb.conf file that looked like this:
[main] server = puppetmaster.puppetlabs.vm port = 8081
And Puppet gave me this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for puppetmaster.puppetlabs.vm to PuppetDB at puppetmaster.puppetlabs.vm port = 8081:8080: getaddrinfo: Name or service not known warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run
It appears as if it thought the server for PuppetDB was “puppetmaster.puppetlabs.vm\n port = 8081” Killing the 2-space indent made things work!