[root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x86_64]# /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-x86_64]# 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 ${INSTALL_DIR}/ezbake-functions.sh wait_for_app (code=exited, status=1/FAILURE)
Process: 12638 ExecStart=/opt/puppetlabs/server/bin/java $JAVA_ARGS -XX:OnOutOfMemoryError=kill -9 %%p -Djava.security.egd=/dev/urandom -cp ${INSTALL_DIR}/puppet-server-release.jar clojure.main -m puppetlabs.trapperkeeper.main --config ${CONFIG} -b ${BOOTSTRAP_CONFIG} $@ (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-x86_64]# /bin/systemctl stop pe-puppetserver
[root@ip-172-31-42-247 puppet-enterprise-2016.1.2-el-7-x86_64]# /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-x86_64]# 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-x86_64]# 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/listinfo/systemd-devel
--
-- 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[523]: DHCPREQUEST on eth0 to 172.31.32.1 port 67 (xid=0x4fb50bf1)
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dhclient[523]: DHCPACK from 172.31.32.1 (xid=0x4fb50bf1)
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: address 172.31.42.247
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: plen 20 (255.255.240.0)
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: gateway 172.31.32.1
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: server identifier 172.31.32.1
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: lease time 3600
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: hostname 'ip-172-31-42-247'
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: nameserver '172.31.0.2'
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: domain name 'us-west-2.compute.internal'
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal NetworkManager[492]: (eth0): DHCPv4 state changed bound -> bound
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dhclient[523]: bound to 172.31.42.247 -- renewal in 1747 seconds.
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dbus[499]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.free
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dbus-daemon[499]: dbus[499]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' u
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Starting Network Manager Script Dispatcher Service...
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dbus[499]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal dbus-daemon[499]: dbus[499]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal systemd[1]: Started Network Manager Script Dispatcher Service.
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is done.
Jun 17 16:57:19 ip-172-31-42-247.us-west-2.compute.internal nm-dispatcher[12707]: Dispatching action 'dhcp4-change' for eth0
lines 1474-1516/1516 (END)
↧