After upgrading to puppet 4 on Red Hat Satellite 6.3, puppet-server fails to start

Solution Verified - Updated -

Issue

  • After upgrading to puppet 4 on Red Hat Satellite 6.3, puppet-server fails to start

    [root@satellite ~]# systemctl start puppetserver.service -l
    Job for puppetserver.service failed because the control process exited with error code. See "systemctl status puppetserver.service" and "journalctl -xe" for 
    details.
    [root@satellite ~]# systemctl status puppetserver.service -l
    ● puppetserver.service - puppetserver Service
      Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; disabled; vendor preset: disabled)
      Active: activating (start) since Fri 2018-03-02 18:27:50 IST; 7s ago
     Control: 13622 (bash)
      CGroup: /system.slice/puppetserver.service
              ├─13622 bash /opt/puppetlabs/server/apps/puppetserver/cli/apps/start
              ├─13629 /usr/bin/java -Xms2g -Xmx2g -XX:MaxPermSize=256m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp 
    /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar 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
              └─13660 sleep 1
    
    Mar 02 18:27:50 satellite.redhat.com systemd[1]: Starting puppetserver Service...
    Mar 02 18:27:50 satellite.redhat.com puppetserver[13622]: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
    

Environment

  • Red Hat Satellite 6.3
  • puppet 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In