Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-2997

puppetserver version: 7.1.0 wont open up port 8140

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: SERVER 7.1.0
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version: 7.5.0
      Puppet Server Version: 7.1.0
      OS Name/Version: Centos / Rhel 7

       

      Desired Behavior: when installed , and puppetserver service has started , default port 8140 should be listening.

      Actual Behavior: Puppetserver starts but service fails complete startup

      Apr 16 20:50:43 puppet systemd[1]: puppetserver.service start operation timed out. Terminating.
      Apr 16 20:50:44 puppet puppetserver[3266]: Startup script was terminated before completion
      Apr 16 20:50:45 puppet systemd[1]: puppetserver.service: control process exited, code=exited status=1
      Apr 16 20:50:45 puppet 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.
      Apr 16 20:50:45 puppet systemd[1]: Unit puppetserver.service entered failed state.
      Apr 16 20:50:45 puppet systemd[1]: puppetserver.service failed.
      Apr 16 20:50:45 puppet systemd[1]: puppetserver.service holdoff time over, scheduling restart.
      Apr 16 20:50:45 puppet 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.
      Apr 16 20:50:45 puppet polkitd[670]: Unregistered Authentication Agent for unix-process:3172:1621353 (system bus name :1.48, object path /org/freedesktop/PolicyKit1/Aut
      Apr 16 20:50:45 puppet 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.

      puppetserver.log

      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. SIGILL (0x4) at pc=0x00007ff7e2364be4, pid=1176, tid=0x00007ff7938fa700
        #
      3. JRE version: OpenJDK Runtime Environment (8.0_282-b08) (build 1.8.0_282-b08)
      4. Java VM: OpenJDK 64-Bit Server VM (25.282-b08 mixed mode linux-amd64 compressed oops)
      5. Problematic frame:
      6. J 8311 C1 org.jruby.ir.instructions.CallBase.potentiallySend(Ljava/lang/String;I)Z (41 bytes) @ 0x00007ff7e2364be4 [0x00007ff7e2364be0+0x4]
        #
      7. Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
        #
      8. If you would like to submit a bug report, please visit:
      9. https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%207&component=java-1.8.0-openjdk

      puppet.conf

      main]
      certname = puppet
      server = puppet
      environment = production
      dns_alt_names = puppet
      runinterval = 1h
      strict_variables = true

      [master]
      dns_alt_names = puppetmaster,puppet
      reports = puppetdb
      storeconfigs_backend = puppetdb
      storeconfigs = true
      environment_timeout = unlimited

      [server]
      vardir = /opt/puppetlabs/server/data/puppetserver
      logdir = /var/log/puppetlabs/puppetserver
      rundir = /var/run/puppetlabs/puppetserver
      pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid
      codedir = /etc/puppetlabs/code

       

      sysconfig puppetserver

      [agent]
      server = puppet
      [root@puppet puppet]# cat /etc/sysconfig/puppetserver
      ###########################################

      1. Init settings for puppetserver
        ###########################################
      1. Location of your Java binary (version 8)
        JAVA_BIN="/usr/bin/java"
      1. Modify this if you'd like to change the memory allocation, enable JMX, etc
        JAVA_ARGS="-Xms1g -Xmx1g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"
        #JAVA_ARGS=" -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"

       

      1. Modify this as you would JAVA_ARGS but for non-service related subcommands
        JAVA_ARGS_CLI="${JAVA_ARGS_CLI:-}"
      1. Modify this if you'd like TrapperKeeper specific arguments
        TK_ARGS=""
      1. These normally shouldn't need to be edited if using OS packages
        USER="puppet"
        GROUP="puppet"
        INSTALL_DIR="/opt/puppetlabs/server/apps/puppetserver"
        CONFIG="/etc/puppetlabs/puppetserver/conf.d"
      1. Bootstrap path
        BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/"
      1. SERVICE_STOP_RETRIES can be set here to alter the default stop timeout in
      2. seconds. For systemd, the shorter of this setting or 'TimeoutStopSec' in
      3. the systemd.service definition will effectively be the timeout which is used.
        SERVICE_STOP_RETRIES=60
      1. START_TIMEOUT can be set here to alter the default startup timeout in
      2. seconds. For systemd, the shorter of this setting or 'TimeoutStartSec'
      3. in the service's systemd.service configuration file will effectively be the
      4. timeout which is used.
        START_TIMEOUT=300
      1. Maximum number of seconds that can expire for a service reload attempt before
      2. the result of the attempt is interpreted as a failure.
        RELOAD_TIMEOUT=120

       

      For memory issues with server heap dumps are also helpful.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            welsh1lad welsh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support