On Thu, 25 May 2023 17:53:25 +0200 gregor herrmann <gre...@debian.org> wrote: > Control: tag -1 + unreproducible > > On Fri, 05 May 2023 14:16:53 +0000, Holger Levsen wrote: > > > On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote: > > > That bug is currently blocking from using munin on not systemd systems. > > I'm not planning on supporting legacy initscripts myself. And despite > > tagging > > this bug 'wontfix' for the time being I will accept patches, so IOW I'm just > > tagging this 'wontfix' to set expectations right. > > In general I'm happy to help with the sysv initscript; in practice I > can only notice that I'm running munin-node (from testing or > unstable) on several machines with sysvinit, and that I haven't > encountered the issue. I just tried to restart and stop/start > munin-node on 3 machines, and it also just worked. > > I guess we need more information from those who hit the issue …
I have a system where munin-node won't start from sysvinit (and also one where it does). The problem seems to be that munin-node itself doesn't start: # munin-node --foreground --debug ; echo $? 1 It doesn't say what the problem is and doesn't leave anything in the logs. Is there any way to make it say what it's problem is? On a side note, the --foreground option is not documented in the man page. Regards Carsten
