Unit pe-puppetserver.service has failed

asked 2016-06-17 16:04:55 -0500

[root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x8664]# /bin/systemctl start pe-puppetserver Job for pe-puppetserver.service failed because the control process exited with error code. See "systemctl status pe-puppetserver.service" and "journalctl -xe" for details. [root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x8664]# systemctl status pe-puppetserver.service ● pe-puppetserver.service - pe-puppetserver Service Loaded: loaded (/usr/lib/systemd/system/pe-puppetserver.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2016-06-17 16:54:30 EDT; 11s ago Process: 12639 ExecStartPost=/bin/bash ${INSTALLDIR}/ezbake-functions.sh waitforapp (code=exited, status=1/FAILURE) Process: 12638 ExecStart=/opt/puppetlabs/server/bin/java $JAVAARGS -XX:OnOutOfMemoryError=kill -9 %%p -Djava.security.egd=/dev/urandom -cp ${INSTALLDIR}/puppet-server-release.jar clojure.main -m puppetlabs.trapperkeeper.main --config ${CONFIG} -b ${BOOTSTRAPCONFIG} $@ (code=exited, status=1/FAILURE) Process: 12637 ExecStartPre=/usr/bin/install --group=pe-puppet --owner=pe-puppet -d /var/run/puppetlabs/puppetserver (code=exited, status=0/SUCCESS) Main PID: 12638 (code=exited, status=1/FAILURE)

Jun 17 16:54:29 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: pe-puppetserver.service: control process exited, code=exited status=1 Jun 17 16:54:29 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Failed to start pe-puppetserver Service. Jun 17 16:54:29 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Unit pe-puppetserver.service entered failed state. Jun 17 16:54:29 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: pe-puppetserver.service failed. Jun 17 16:54:30 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: pe-puppetserver.service holdoff time over, scheduling restart. Jun 17 16:54:30 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: start request repeated too quickly for pe-puppetserver.service Jun 17 16:54:30 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Failed to start pe-puppetserver Service. Jun 17 16:54:30 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Unit pe-puppetserver.service entered failed state. Jun 17 16:54:30 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: pe-puppetserver.service failed. [root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x8664]# /bin/systemctl stop pe-puppetserver [root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x8664]# /bin/systemctl start pe-puppetserver Job for pe-puppetserver.service failed because the control process exited with error code. See "systemctl status pe-puppetserver.service" and "journalctl -xe" for details. [root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x8664]# journalctl -xe status pe-puppetserver Failed to add match 'status': Invalid argument Failed to add filters: Invalid argument [root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x8664]# journalctl -xe Jun 17 16:55:34 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: pe-puppetserver.service holdoff time over, scheduling restart. Jun 17 16:55:34 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: start request repeated too quickly for pe-puppetserver.service Jun 17 16:55:34 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Failed to start pe-puppetserver Service. -- Subject: Unit pe-puppetserver.service has failed -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit pe-puppetserver.service has failed.

-- The result is failed. Jun 17 16:55:34 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Unit pe-puppetserver.service entered failed state. Jun 17 16:55:34 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: pe-puppetserver.service failed. Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dhclient ... (more)

edit retag flag offensive close merge delete

Comments

try `service pe-puppetserver restart`

rajeevsharma ( 2016-06-22 02:41:31 -0500 )edit

and/or `journalctl -u pe-puppetserver`

cprice404 ( 2016-06-22 08:17:16 -0500 )edit

add a comment

answered 2016-10-21 00:01:10 -0500

greynolds
46 ●1 ●2 ●5

Here is what I noticed...

if [ "$0" = "$BASHSOURCE" ] ;then COMMAND={$1:?} export $(systemctl show -p MainPID pe-puppetserver.service) case $COMMAND in waitforapp) waitforapp ${MainPID:?} ${STARTTIMEOUT:-300} ;;

COMMAND=${1:?} changed to COMMAND={$1:?} = line 65 The change was made here

[root@centos7 puppetserver]# bash -x ezbake-functions.sh + '[' ezbake-functions.sh = ezbake-functions.sh ']' + COMMAND='{:?}' ++ systemctl show -p MainPID pe-puppetserver.service + export MainPID=20770 + MainPID=20770 + case $COMMAND in

[root@centos7 puppet-enterprise-2016.4.0-el-7-x8664]# service pe-puppetserver status Redirecting to /bin/systemctl status pe-puppetserver.service ● pe-puppetserver.service - pe-puppetserver Service Loaded: loaded (/usr/lib/systemd/system/pe-puppetserver.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2016-10-20 21:44:51 PDT; 2s ago Process: 20005 ExecStartPost=/bin/bash ${INSTALLDIR}/ezbake-functions.sh waitforapp (code=exited, status=0/SUCCESS) Process: 20002 ExecStartPre=/usr/bin/install --group=pe-puppet --owner=pe-puppet -d /var/run/puppetlabs/puppetserver (code=exited, status=0/SUCCESS) Main PID: 20004 (java) CGroup: /system.slice/pe-puppetserver.service └─20004 /opt/puppetlabs/server/bin/java -Xms2048m -Xmx2048m -XX:On...