Description of problem: smokeping fails to start on boot Version-Release number of selected component (if applicable): smokeping-2.6.10-3.fc24.noarch How reproducible: Reproducible on each boot Steps to Reproduce: 1. have smokeping installed and run systemctl enable smokeping 2. reboot 3. systemctl status smokeping Actual results: [root@nutshell ~]# systemctl status smokeping ● smokeping.service - Latency Logging and Graphing System Loaded: loaded (/usr/lib/systemd/system/smokeping.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2016-10-25 13:31:27 EDT; 1min 15s ago Process: 1012 ExecStart=/usr/sbin/smokeping --nodaemon (code=exited, status=9) Main PID: 1012 (code=exited, status=9) Oct 25 13:31:08 nutshell.downontheupside.net systemd[1]: Started Latency Logging and Graphing System. Oct 25 13:31:09 nutshell.downontheupside.net smokeping[1012]: WARNING: Hostname 'google.com' does currently not resolve to an IPv4 address Oct 25 13:31:09 nutshell.downontheupside.net smokeping[1012]: WARNING: Hostname 'www.google.com' does currently not resolve to an IPv4 address Oct 25 13:31:09 nutshell.downontheupside.net smokeping[1012]: WARNING: Hostname 'www.datapipe.com' does currently not resolve to an IPv4 address Oct 25 13:31:09 nutshell.downontheupside.net smokeping[1012]: WARNING: Hostname 'xmlrpc.rhn.redhat.com' does currently not resolve to an IPv4 address Oct 25 13:31:27 nutshell.downontheupside.net smokeping[1012]: ERROR: output of '/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*) Oct 25 13:31:27 nutshell.downontheupside.net smokeping[1012]: at (eval 50) line 1. Oct 25 13:31:27 nutshell.downontheupside.net systemd[1]: smokeping.service: Main process exited, code=exited, status=9/n/a Oct 25 13:31:27 nutshell.downontheupside.net systemd[1]: smokeping.service: Unit entered failed state. Oct 25 13:31:27 nutshell.downontheupside.net systemd[1]: smokeping.service: Failed with result 'exit-code'. Expected results: smokeping should be running. Additional info: systemctl start smokeping will start the service as expected. Assuming that it is trying to start before networking is available.
Changing the following line in /usr/lib/systemd/system/smokeping.service from: After=syslog.target network.target to: After=syslog.target network-online.target Seems to have fixed the issue for me.
Hi! Thanks for fix, will push update!
Created attachment 1214026 [details] working smokeping.service Tested on fc24 x86_64 with smokeping-2.6.10-3.fc24.noarch
Great, thank you for the quick response!
Update pushed: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d512bce0a1
smokeping-2.6.11-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-12cfbb1af5
smokeping-2.6.11-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b7dad297bb
smokeping-2.6.11-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d512bce0a1
smokeping-2.6.11-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
smokeping-2.6.11-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
smokeping-2.6.11-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.