Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-05-02 Thread Cameron Davidson
Hi Gabriel, thanks for getting back to me - the timing was good, because the issue  has just recurred on my system. You are of course correct in what _should_ have happened based on the contents of the unit file. I just jumped to the wrong conclusion based on the error message, and that my

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-05-01 Thread Gabriel Filion
Hi Cameron, Sorry it took me so much time to reply. I've just now fixed my local discardable VM setup for testing so I'm able to dive in again. On Tue, 11 Feb 2020 11:23:19 +1000 Cameron Davidson wrote: > This has just started hapenning to my also. > > The cause, I think, that evenutally a

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-02-10 Thread Cameron Davidson
This has just started hapenning to my also. The cause, I think, that evenutally a tmpfile cleanup will delete /run/smokeping - maybe depends on age and/or  because it is not owned by root. One solution (I found for other systemd processes run as non-root) is to add a config file:

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-02-10 Thread Cameron Davidson
Sorry, a followup to my incomplete previous post... After upgrade from Debian 9 to 10... /run on my system is now mounted on a tmpfs and is therefore recreated empty at reboot.  The old pidfile location /var/run is symlinked to /run. The folder /run/smokeping needs to be recreated each reboot

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-08-25 Thread Gabriel Filion
On Sat, 6 Jul 2019 13:01:12 -0400 Gabriel Filion wrote: > On Tue, 2 Apr 2019 10:46:38 -0400 Gabriel Filion > wrote: > > On 2019-03-26 3:26 p.m., BERTRAND Joël wrote: > > >> Did you recently upgrade smokeping? if so what version were you > > >> using before? (maybe check your dpkg logs for signs

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-07-06 Thread Gabriel Filion
Hi again Bertrand, On Tue, 2 Apr 2019 10:46:38 -0400 Gabriel Filion wrote: > On 2019-03-26 3:26 p.m., BERTRAND Joël wrote: > >> 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) > >

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-04-02 Thread Gabriel Filion
Hello, On 2019-03-26 3:26 p.m., BERTRAND Joël wrote: >> 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) > Yes, I have. > > -> 2019-03-17 03:26:38 upgrade smokeping:all 2.7.2-3

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-03-26 Thread BERTRAND Joël
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Gabriel Filion a écrit : > On 2019-03-26 2:43 p.m., Gabriel Filion wrote: >> 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) > > I just

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-03-26 Thread BERTRAND Joël
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Gabriel Filion a écrit : > Hi Bertrand, Hello, > e.g. the file is in /run/smokeping and systemd is able to use it > to restart the servce. In my case, systemd doesn't create /run/smokeping. > Did you recently upgrade smokeping?

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-03-26 Thread Gabriel Filion
On 2019-03-26 2:43 p.m., Gabriel Filion wrote: > 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) I just thought of something else: if you were using the 2.7.3-1 package previously, it's

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-03-26 Thread Gabriel Filion
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. > >

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2019-03-25 Thread BERTRAND Joël
Package: smokeping Version: 2.7.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, 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