Re: [Puppet Users] PuppetDB doesn't work in Puppet 4: Error Executing http request
Thanks for the advice, running the puppetserver process ion the foreground showed quite clearly it was a hostname related issue which I've now fixed and it works perfectly. On 9 June 2015 at 14:44, Ken Barber k...@puppetlabs.com wrote: I am trying to use PuppetDB with a Puppet 4 server that I am testing. I have set it up as per the official docs but now I get this error when trying to do a Puppet run (it worked before adding PuppetDB): # puppet agent -t --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for ip-172-30-2-43.eu-west-1.compute.internal: Failed to find facts from PuppetDB at puppetdb.solutions.exmaple.co.uk:8081: Error executing http request Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for ip-172-30-2-43.eu-west-1.compute.internal to PuppetDB at puppetdb.solutions.example.co.uk:8081: Error executing http request Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run The error is a little generic, do you have the error and stack trace from the master process, so we can see what line of code is causing this perhaps? Unfortunately the agent error is just a mirror of the error on the server, you need to look into the master process to dig further - potentially even turn on debugging. The puppetdb termini will also log its actions as well in the master log, so it would be good to see a full run here, where it breaks and the stack trace to figure out why. I re-followed the instructions on a Puppet 3.8.1 master and PuppetDB worked as expected. DNS correctly resolves the hostname, security groups in AWS are open to allow the connection. The only differing factor between the two setups was the use of Puppet 4 for the one that is failing. If you can provide the normal diagnostic info, like distro, version of distro and exact version of all the elements (like puppetdb puppetdb-terminus) this might be useful. Also - what does your /etc/puppet/puppetdb.conf file look like? ken. -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/sZQxFX6uBo8/unsubscribe. To unsubscribe from this group and all its topics, 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/CAE4bNTmogdjkh9SjxCA-Pc67S9doV1YLrctHo9SqXLhTRaEHCQ%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- Kind Regards Danny R Website: http://danny-roberts.info/ -- 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/CAMAFyt%3DxF1YG_WuvcPZkTFSuo9Y0r-kpqFcfPPcKk5cMjBtJng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] PuppetDB doesn't work in Puppet 4: Error Executing http request
I am trying to use PuppetDB with a Puppet 4 server that I am testing. I have set it up as per the official docs but now I get this error when trying to do a Puppet run (it worked before adding PuppetDB): # puppet agent -t --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for ip-172-30-2-43.eu-west-1.compute.internal: Failed to find facts from PuppetDB at puppetdb.solutions.exmaple.co.uk:8081: Error executing http request Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for ip-172-30-2-43.eu-west-1.compute.internal to PuppetDB at puppetdb.solutions.example.co.uk:8081: Error executing http request Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I re-followed the instructions on a Puppet 3.8.1 master and PuppetDB worked as expected. DNS correctly resolves the hostname, security groups in AWS are open to allow the connection. The only differing factor between the two setups was the use of Puppet 4 for the one that is failing. -- 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/3a89c5f9-b9e1-41b5-8e77-7971e6e79669%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] PuppetDB doesn't work in Puppet 4: Error Executing http request
I am trying to use PuppetDB with a Puppet 4 server that I am testing. I have set it up as per the official docs but now I get this error when trying to do a Puppet run (it worked before adding PuppetDB): # puppet agent -t --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for ip-172-30-2-43.eu-west-1.compute.internal: Failed to find facts from PuppetDB at puppetdb.solutions.exmaple.co.uk:8081: Error executing http request Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for ip-172-30-2-43.eu-west-1.compute.internal to PuppetDB at puppetdb.solutions.example.co.uk:8081: Error executing http request Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run The error is a little generic, do you have the error and stack trace from the master process, so we can see what line of code is causing this perhaps? Unfortunately the agent error is just a mirror of the error on the server, you need to look into the master process to dig further - potentially even turn on debugging. The puppetdb termini will also log its actions as well in the master log, so it would be good to see a full run here, where it breaks and the stack trace to figure out why. I re-followed the instructions on a Puppet 3.8.1 master and PuppetDB worked as expected. DNS correctly resolves the hostname, security groups in AWS are open to allow the connection. The only differing factor between the two setups was the use of Puppet 4 for the one that is failing. If you can provide the normal diagnostic info, like distro, version of distro and exact version of all the elements (like puppetdb puppetdb-terminus) this might be useful. Also - what does your /etc/puppet/puppetdb.conf file look like? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTmogdjkh9SjxCA-Pc67S9doV1YLrctHo9SqXLhTRaEHCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
