Hi Bertrand, On 2019-03-25 2:57 a.m., BERTRAND Joël wrote: > I have restarted a server last sunday and I have seen that smokeping doesn't > start anymore. > > In systemd config file, smokeping is launched with --pid-dir=/run/smokeping > and > systemd complains about non existent pid file. > > I have tried to launch smokeping in command line : > [~] > /usr/sbin/smokeping --pid-dpid-dir=/run/smokepingir=/run/smokeping > > and pid file is created in... /run and not in /run/smokeping, that confuses > systemd.
I've tried to reproduce this in a vanilla debian buster VM in which I
installed smokeping and the behaviour you mentioned wasn't showing up.
e.g. I see this which is what is expected:
root@debian-10-amd64:~# ls -l /run/smokeping/
total 4
-rw-r--r-- 1 smokeping smokeping 5 Mar 26 18:32 smokeping.pid
root@debian-10-amd64:~# ls -l /run/ | grep smokeping
drwxr-xr-x 2 smokeping smokeping 60 Mar 26 18:32 smokeping
root@debian-10-amd64:~# service smokeping restart
root@debian-10-amd64:~# ls -l /run/ | grep smokeping
drwxr-xr-x 2 smokeping smokeping 60 Mar 26 18:33 smokeping
root@debian-10-amd64:~# ls -l /run/smokeping/
total 4
-rw-r--r-- 1 smokeping smokeping 5 Mar 26 18:33 smokeping.pid
e.g. the file is in /run/smokeping and systemd is able to use it to
restart the servce.
Did you recently upgrade smokeping? if so what version were you using
before? (maybe check your dpkg logs for signs of upgrade of the
smokeping package)
Do you have an override in place for the smokeping.service systemd unit?
"service smokeping status" will show you if there is an override in
place. e.g. it would look similar to this:
root@debian-10-amd64:~# service smokeping status
● smokeping.service - Latency Logging and Graphing System
Loaded: loaded (/lib/systemd/system/smokeping.service; enabled;
vendor preset: enabled)
Drop-In: /etc/systemd/system/smokeping.service.d
└─slave_mode.conf
cheers!
signature.asc
Description: OpenPGP digital signature
