Control: retitle -1 puppet: service fails to start
Control: tags -1 moreinfo
Hi,
On 14:21 Fri 06 Jan , Nigel Horne wrote:
> Puppet fails to start but doesn't say why or what to change to correct
> it.
>
> systemctl start puppet.service
> Job for puppet.service failed because the control process exited with error
> code.
> See "systemctl status puppet.service" and "journalctl -xe" for details.
> root@gateway:/var/log/syslog/local# systemctl status puppet.service
> ● puppet.service - LSB: puppet agent
> Loaded: loaded (/etc/init.d/puppet; generated; vendor preset: enabled)
^ Now, this is a bit weird since puppet-agent
4.8.1-1 includes a native systemd unit, but your system seems to be
using the one generated from the initscript (and this should never
happen). Did you reboot since upgrading puppet?
> Active: failed (Result: exit-code) since Fri 2017-01-06 14:18:05 GMT; 5s
> ago
> Docs: man:systemd-sysv-generator(8)
> Process: 14879 ExecStart=/etc/init.d/puppet start (code=exited,
> status=1/FAILURE)
>
> Jan 06 14:18:05 gateway systemd[1]: Starting LSB: puppet agent...
> Jan 06 14:18:05 gateway puppet[14879]: Starting puppet agent failed!
> Jan 06 14:18:05 gateway systemd[1]: puppet.service: Control process exited,
> code=exited status=1
> Jan 06 14:18:05 gateway systemd[1]: Failed to start LSB: puppet agent.
> Jan 06 14:18:05 gateway systemd[1]: puppet.service: Unit entered failed state.
> Jan 06 14:18:05 gateway systemd[1]: puppet.service: Failed with result
> 'exit-code'.
You could also check /var/log/syslog for puppet-agent messages. However,
the "Control process exited" line tells us there's probably something
wrong with the initscript itself, so you might want to call it directly
using:
_SYSTEMCTL_SKIP_REDIRECT=true /etc/init.d/puppet start
and see if it reports any errors.
Regards,
Apollon
