% date ; sudo /etc/init.d/munin-node restart Wed Sep 5 15:18:17 UTC 2012 * Stopping munin-node ... * start-stop-daemon: fopen `/var/run/munin-node.pid': No such file or di [ ok ] * Starting munin-node ... % date ; sudo /etc/init.d/munin-node restart Wed Sep 5 15:18:18 UTC 2012 * Stopping munin-node ... * start-stop-daemon: fopen `/var/run/munin-node.pid': No such file or di [ ok ] * Starting munin-node ... [ ok ] So, something goes wierd in the init script. I am using stable x86 with ~arch munin.
Uhm, I can't reproduce this.. is it correct in your /etc/munin/munin-node.conf ?
I'm having the some problem on two different machines (both x86_64) # /etc/init.d/munin-node restart * Stopping munin-node ... * start-stop-daemon: fopen `/var/run/munin-node.pid': No such file or directory [ ok ] * Starting munin-node ... [ ok ] # grep pid /etc/munin/munin-node.conf pid_file /var/run/munin-node.pid # ls /var/run/munin-node.pid ls: cannot access /var/run/munin-node.pid: No such file or directory
Is munin-node running at that point for real? Do note that the pid file is created by the node itself, and not from the init script. Also, can you post the full munin-node.conf?
Yes, munin-node was running at that time. My problem is now solved, but I am not sure why exactly. I did not touch the config file, the only thing I did in the meantime was: I killed munin-node manually, re-emerged munin and then started it via init script. This time the pid file was created.
I have a hunch — was that just after an update?
If your hunch is, that the problem occurred after the last update and the new init script did not kill the old munin-node instance, and ever since that an old version of munin-node was running in the background. I would think the same (as I did update munin at about a week ago).
Yeah that was the thing. William, does it feel like it might make sense to store the pidfile path at start, and use it during stop by default? I know I should be able to store/load it myself, but maybe solving it in runscript is easier on the long term.
(In reply to comment #7) > William, does it feel like it might make sense to store the pidfile path at > start, and use it during stop by default? I know I should be able to > store/load it myself, but maybe solving it in runscript is easier on the > long term. I'm not sure I am following. If the pidfile variable is set to the correct value it is used in the default start/stop functions, so I'm not sure what you mean.
Sorry, the only thing that might happen in this case is that the pidfile changes before/after update. Before update, the configuration file used /var/run/munin/munin-node.pid (which requires a checkpath). After update, the configuration file uses /var/run/munin-node.pid (no checkpath needed). But if you update, the stop is executed already with the new pidfile (which no longer matches) instead of the old one.
William any hope on this?
This was brought to my attention as an issue which should be fixed in OpenRC itself. The fix is in commit 6b3a411 and will be included in openrc-0.12.
