Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Puppet Users
Home
+ new post
About this group
Join this group
PuppetDB Connection Failures
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Worker Bee  
View profile  
 More options Oct 17 2012, 4:42 pm
From: Worker Bee <beeworke...@gmail.com>
Date: Wed, 17 Oct 2012 16:41:59 -0400
Local: Wed, Oct 17 2012 4:41 pm
Subject: PuppetDB Connection Failures
Print | Individual message | Show original | Report this message | Find messages by this author

Hi Everyone;

I am now getting a puppetdb connection error when I attempt to run
#puppet agent --test

Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed to submit 'replace facts' command for puppetdev to PuppetDB at
puppetdev:8081: Connection refused - connect(2)

puppet.conf
[master]
storeconfigs = true
storeconfigs_backend = puppetdb

puppetdb.conf
[main]
server = puppetdev04
port = 8081
JAVA_ARGS="-Xmx192m"

I am running 3.0 open source with passenger....
Using postgres

I have the puppetdb daemin running

Any advice, as always, would be greatly appreciated!

Bee


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Chris Price  
View profile  
 More options Oct 18 2012, 12:33 pm
From: Chris Price <ch...@puppetlabs.com>
Date: Thu, 18 Oct 2012 09:33:24 -0700 (PDT)
Local: Thurs, Oct 18 2012 12:33 pm
Subject: Re: PuppetDB Connection Failures
Print | Individual message | Show original | Report this message | Find messages by this author

Hello Bee,

This message is often the result of one of the following:

1) Firewall blocking the puppetdb port
2) DNS issue with the hostname specified in your puppetdb.conf
3) DNS issue with the ssl-host specified in your jetty.ini on the puppetdb
server

Are you able to connect (e.g. via telnet) from the master machine to port
8081 on the puppetdb machine?

Please feel free to jump on the #puppet channel in Freenode if you need
rapid assistance!  We'll be happy to help.

Thanks
Chris


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jacqueline Atkins  
View profile  
 More options Oct 18 2012, 1:43 pm
From: Jacqueline Atkins <atkins.jac...@gmail.com>
Date: Thu, 18 Oct 2012 13:43:18 -0400
Local: Thurs, Oct 18 2012 1:43 pm
Subject: Re: [Puppet Users] Re: PuppetDB Connection Failures
Print | Individual message | Show original | Report this message | Find messages by this author

Thanks so much!

I actually got to the bottom of the issue late last night.  It was an issue
with how I had configured postgres.

Thanks everyone!


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google