FS#47678 - [smokeping] daemon is not running after reboot
Attached to Project:
Community Packages
Opened by Doron Blass (doronb) - Saturday, 09 January 2016, 06:36 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 09 January 2016, 16:22 GMT
Opened by Doron Blass (doronb) - Saturday, 09 January 2016, 06:36 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 09 January 2016, 16:22 GMT
|
Details
Description:
After installing smokeping and rebooting - smokeping is started very early in the boot process, before host resolving is operational. This causes it to fail start. Issuing "systemdctl start smokeping" later will start the daemon successfully. To solve - add the following lines to usr/lib/systemd/system/smokeping.service: [Unit] Description=SmokePing Daemon After=network.target Additional info: * package version: smokeping-2.6.11-1 * Example log: Jan 01 08:20:01 server systemd[1]: Started smokeping.service. Jan 01 08:20:08 server smokeping[355]: WARNING: Hostname 'www.google.com' does currently not resolve to an IPv4 address Jan 01 08:20:08 server smokeping[355]: WARNING: Hostname 'www.google.com' does currently not resolve to an IPv4 address Jan 01 08:20:26 server smokeping[355]: ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*) Jan 01 08:20:26 server smokeping[355]: at (eval 35) line 1. Jan 01 08:20:27 server systemd[1]: smokeping.service: Main process exited, code=exited, status=9/n/a Jan 01 08:20:27 server systemd[1]: smokeping.service: Unit entered failed state. Jan 01 08:20:27 server systemd[1]: smokeping.service: Failed with result 'exit-code'. Steps to reproduce: * Install smokeping * Reboot |
This task depends upon
Closed by Florian Pritz (bluewind)
Saturday, 09 January 2016, 16:22 GMT
Reason for closing: Fixed
Additional comments about closing: smokeping 2.6.11-2
Saturday, 09 January 2016, 16:22 GMT
Reason for closing: Fixed
Additional comments about closing: smokeping 2.6.11-2