Start raintank-probe on bootup

#1

Any hints on how to get raintank-probe to start on reboot?

This works to start raintank-probe:
[root@tcs-grafana-01 ~]# service raintank-probe start

All the other systemctl commands work w/o issue (start, restart, staus, stop)
BUT, trying to use “systemctl” to enable raintank-probe as a service then it doesn’t start up on reboot:

systemctl enable raintank-probe
shutdown -r now

[root@tcs-grafana-01 ~]# systemctl status raintank-probe
● raintank-probe.service - Raintank probe monitoring agent
Loaded: loaded (/usr/lib/systemd/system/raintank-probe.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Sun 2019-04-07 14:38:52 PDT; 2min 26s ago
Process: 3444 ExecStart=/usr/bin/raintank-probe -config=/etc/raintank/probe.ini (code=exited, status=2)
Main PID: 3444 (code=exited, status=2)
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: Unit raintank-probe.service entered failed state.
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: raintank-probe.service failed.
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: raintank-probe.service holdoff time over, scheduling restart.
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: Stopped Raintank probe monitoring agent.
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: start request repeated too quickly for raintank-probe.service
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: Failed to start Raintank probe monitoring agent.
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: Unit raintank-probe.service entered failed state.
Apr 07 14:38:52 tcs-grafana-01 systemd[1]: raintank-probe.service failed.

Thanks,
Dan

#2

I resolved this with the help of Grafana support. Oddly, the service was starting but failing a DNS lookup on startup. I set the service to start with a 30 second delay.