puppet 8140 port is not listening

3,316 views
Skip to first unread message

moons...@gmail.com

unread,
Feb 29, 2016, 10:09:09 AM2/29/16
to Puppet Users
Hi All,

I have installed 4.3 puppet enterprise. It was running till yesterday but suddenly it stopped running. Please let me know where to look and what to do.

puppet agent --test error message

Error:

Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140
Info: Retrieving pluginfacts
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140
Info: Retrieving plugin
Error: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140
Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140
Info: Loading facts
Error: Could not retrieve catalog from remote server: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140

Thanks,

Lowe Schmidt

unread,
Feb 29, 2016, 2:29:14 PM2/29/16
to puppet...@googlegroups.com

On 29 February 2016 at 16:09, <moons...@gmail.com> wrote:
Warning: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140

Is the puppetmaster up and listening on that name?


--
Lowe Schmidt | +46 723 867 157

warron.french

unread,
Feb 29, 2016, 8:00:22 PM2/29/16
to puppet...@googlegroups.com

Sorry to interject, but does your master and agent machine have enough space in /var?

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAC-wWcSjaUJ36R1h3zLcu%2BARUn4W3dD5OYm%2BS7nu2URq9FX-dA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jason Hatman

unread,
Jul 19, 2016, 2:27:02 PM7/19/16
to Puppet Users
Hello.  I had this issue as well.  My VM only has 2GB of RAM total and puppetserver was configured to use the same, 2GB.  That's why it failed. The puppetserver service never was starting. I edited /etc/default/puppetserver to only allow puppet server to use 1GB and then the service started sucessfully. Change -Xms1G and -Xmx1G to reflect how many GB of RAM you want to allocate. (i.e. -Xms2G or -Xms4G)

JAVA_ARGS="-Xms1G -Xmx1G -XX:MaxPermSize=256m"


Afterwards run sudo service puppetserver restart and see if it loads.

Chris Lamontagne

unread,
Jan 26, 2017, 8:48:07 PM1/26/17
to Puppet Users
Thanks a bunch for this post Jason as this was exactly my problem!  I'm surprised how much digging I had to do to get to this solution finally.
Reply all
Reply to author
Forward
0 new messages