On Wed, Sep 4, 2019 at 12:16 PM 'Prentice Bisbal' via Puppet Users <
[email protected]> wrote:

> I'm doing a fresh install of Puppet6 on CentOS 7.6:
>
> # rpm -qa | grep puppet
> puppetserver-6.4.0-1.el7.noarch
> puppetdb-termini-6.3.4-1.el7.noarch
> puppet-bolt-1.26.0-1.el7.x86_64
> puppet-client-tools-1.2.6-1.el7.x86_64
> puppetdb-6.3.4-1.el7.noarch
> puppet-agent-6.8.1-1.el7.x86_64
> puppet6-release-6.0.0-5.el7.noarch
>
> # cat /etc/redhat-release
> CentOS Linux release 7.6.1810 (Core)
>
> I believe I have everything configured correctly, but when I try to
> start puppetserver, it fails to start:
>
> # systemctl start puppetserver
> Job for puppetserver.service failed because the control process exited
> with error code. See "systemctl status puppetserver.service" and
> "journalctl -xe" for details.
>
> The output of "systemctl status ..." and "journalctl -xe" aren't very
> helpful to me:
>
> # systemctl status puppetserver.service
> ● puppetserver.service - puppetserver Service
>     Loaded: loaded (/usr/lib/systemd/system/puppetserver.service;
> enabled; vendor preset: disabled)
>     Active: activating (start) since Wed 2019-09-04 15:10:53 EDT; 19s ago
>    Control: 21586 (bash)
>      Tasks: 39 (limit: 4915)
>     CGroup: /system.slice/puppetserver.service
>             ├─21586 bash
> /opt/puppetlabs/server/apps/puppetserver/cli/apps/start
>             ├─21593 /usr/bin/java -Xms2g -Xmx2g
> -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger
> -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /...
>             └─21708 sleep 1
>
> Sep 04 15:10:53 puppet.pppl.gov systemd[1]: Starting puppetserver
> Service...
>
> # journalctl -xe
> Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: at
> org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:970)
> Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: at
>
> RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:59)
> Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: at
> RUBY.<main>(uri:classloader:/puppetserver-lib/puppet/server.rb:1)
> Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: at
> org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:970)
> Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: at
>
> RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1)
> Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: at
>
> RUBY.<main>(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:59)
>

This looks like part of stacktrace. Is there a full stacktrace in
/var/log/puppetlabs/puppetserver/puppetserver.log ? If there is it might
give more info.

Sep 04 15:11:58 puppet.pppl.gov puppetserver[21871]: Background process
> 21878 exited before start had completed
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: puppetserver.service:
> control process exited, code=exited status=1
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: Failed to start puppetserver
> Service.
> -- Subject: Unit puppetserver.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit puppetserver.service has failed.
> --
> -- The result is failed.
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: Unit puppetserver.service
> entered failed state.
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: puppetserver.service failed.
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: puppetserver.service holdoff
> time over, scheduling restart.
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: Stopped puppetserver Service.
> -- Subject: Unit puppetserver.service has finished shutting down
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit puppetserver.service has finished shutting down.
> Sep 04 15:11:58 puppet.pppl.gov systemd[1]: Starting puppetserver
> Service...
> -- Subject: Unit puppetserver.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit puppetserver.service has begun starting up.
>
> However, the output of 'ps -ef | grep puppet' shows it's running:
>
> # ps -ef | grep puppet
> puppet   22299     1  0 15:12 ?        00:00:00 bash
> /opt/puppetlabs/server/apps/puppetserver/cli/apps/start
> puppet   22306 22299 99 15:12 ?        00:00:08 /usr/bin/java -Xms2g
> -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger
> -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp
> /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar:/opt/puppetlabs/server/data/puppetserver/jars/*
>
> clojure.main -m puppetlabs.trapperkeeper.main --config
> /etc/puppetlabs/puppetserver/conf.d --bootstrap-config
> /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/
>
> --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter
>
> But nmap doesn't show anything listening on port 8140, whether I use the
> public address or the loopback address:
>
> # nmap localhost
>
> Starting Nmap 6.40 ( http://nmap.org ) at 2019-09-04 15:13 EDT
> Nmap scan report for localhost (127.0.0.1)
> Host is up (0.0000050s latency).
> Other addresses for localhost (not scanned): 127.0.0.1
> Not shown: 997 closed ports
> PORT     STATE SERVICE
> 22/tcp   open  ssh
> 25/tcp   open  smtp
> 5432/tcp open  postgresql
>
> # nmap 172.16.0.52
>
> Starting Nmap 6.40 ( http://nmap.org ) at 2019-09-04 15:13 EDT
> Nmap scan report for puppet.pppl.gov (172.16.0.52)
> Host is up (0.000011s latency).
> Not shown: 999 closed ports
> PORT   STATE SERVICE
> 22/tcp open  ssh
>
> Nmap done: 1 IP address (1 host up) scanned in 0.19 seconds
>
> Iptables is off and SELinux is in permissive mode as I troubleshoot
> this. Any idea what is wrong with my setup?
>
> Any help will be appreciated.
>
> Prentice
>
>
>
>
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/b02cd57e-5fa6-a1f5-e320-1249e42394cf%40pppl.gov
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2B%3DBEqU3mWuoBD0TuNg2H2G1Bnqe1kCwgkbvSAz6uhMZR-yaKw%40mail.gmail.com.

Reply via email to