Failed to open TCP connection to puppet:8140 (Connection refused)

3,159 views
Skip to first unread message

Prentice Bisbal

unread,
Feb 24, 2020, 3:35:40 PM2/24/20
to puppet...@googlegroups.com
I'm suddenly getting this error with my puppetserver:

# puppetserver ca list
Fatal error when running action 'list'
  Error: Failed connecting to
https://puppet:8140/puppet-ca/v1/certificate_statuses/any_key
  Root cause: Failed to open TCP connection to puppet:8140 (Connection
refused - connect(2) for "puppet" port 8140)

I set up my puppet server nearly a year ago, and never had any issues
with it. I was issuing 'puppetserver ca' commands all day Friday w/o any
issue, and now this Monday I'm getting this error. My IP tables rules
allowed port 8140 through, but I turned off iptables altogether while
troubleshooting, SELinux is also temp. disabled while I troubleshoot.

Any idea what is causing this, or how I could troubleshoot further?
/var/log/messages entries don't look very helpful to me, but here's a
sample of what I'm seeing in /var/log/messages:

Feb 24 15:32:08 puppet systemd: Starting puppetserver Service...
Feb 24 15:32:24 puppet puppetserver: Failed to load feature test for
posix: can't find user for 0
Feb 24 15:32:24 puppet puppetserver: Puppet::Error: Cannot determine
basic system flavour
Feb 24 15:32:24 puppet puppetserver: <main> at
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/feature/base.rb:19
Feb 24 15:32:24 puppet puppetserver: require at
org/jruby/RubyKernel.java:987
Feb 24 15:32:24 puppet puppetserver: require at
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54
Feb 24 15:32:24 puppet puppetserver: <module:(root)> at
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:1
Feb 24 15:32:24 puppet puppetserver: <main> at
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:86
Feb 24 15:32:24 puppet puppetserver: require at
org/jruby/RubyKernel.java:987
Feb 24 15:32:24 puppet puppetserver: <main> at
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:38
Feb 24 15:32:24 puppet puppetserver: <main> at
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
Feb 24 15:32:24 puppet puppetserver: require at
org/jruby/RubyKernel.java:987
Feb 24 15:32:24 puppet puppetserver: require at
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54
Feb 24 15:32:24 puppet puppetserver: <main> at
uri:classloader:/puppetserver-lib/puppet/server.rb:1
Feb 24 15:32:24 puppet puppetserver: require at
org/jruby/RubyKernel.java:987
Feb 24 15:32:24 puppet puppetserver: (root) at
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
Feb 24 15:32:24 puppet puppetserver: <main> at
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54
Feb 24 15:32:25 puppet puppetserver: Execution error (RuntimeError) at
RUBY/<main>
(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/feature/base.rb:19).
Feb 24 15:32:25 puppet puppetserver: (Error) Cannot determine basic
system flavour
Feb 24 15:32:25 puppet puppetserver: Full report at:
Feb 24 15:32:25 puppet puppetserver: /tmp/clojure-2036241659099880319.edn
Feb 24 15:32:25 puppet puppetserver: Background process 22815 exited
before start had completed
Feb 24 15:32:25 puppet systemd: puppetserver.service: control process
exited, code=exited status=1
Feb 24 15:32:25 puppet systemd: Failed to start puppetserver Service.
Feb 24 15:32:25 puppet systemd: Unit puppetserver.service entered failed
state.
Feb 24 15:32:25 puppet systemd: puppetserver.service failed.
Feb 24 15:32:25 puppet systemd: puppetserver.service holdoff time over,
scheduling restart.
Feb 24 15:32:25 puppet systemd: Stopped puppetserver Service.
Feb 24 15:32:25 puppet systemd: Starting puppetserver Service...

Any help will be greatly appreciated.

--
Prentice

Prentice Bisbal

unread,
Feb 24, 2020, 3:39:53 PM2/24/20
to puppet...@googlegroups.com
I found the solution here:

https://puppet.com/docs/pe/2017.3/known_issues_server.html#puppet_server_known_issues__puppet_server_run_issue_when_tmp_directory_mounted_noexec

My /tmp was mounted noexec. Weird that this problem just popped up no,
when it had been configured like that for a long time.

Prentice
Reply all
Reply to author
Forward
0 new messages