Control: tags 837788 + moreinfo
On Fri, 10 Mar 2017 at 07:46:17 +0100, Stig Sandbeck Mathisen wrote:
> Munin needs /run/munin created with the correct permissions.
>
> When using sysv init, the /etc/init.d/munin script does that, and exits.
Aha. So the boot process (systemd or sysvinit) in jessie and stretch is
not meant to start munin at all, only prepare the necessary directory for
it to be started by the web server?
If that's the case, then perhaps this bug could be closed as "working as
intended", or downgraded to wishlist and retitled "systemctl restart munin
does nothing".
However, Matthew Gabeler-Lee's reply:
> I argue this merits worse than "important" -- in a default install of
> Stretch currently, munin doesn't work at all.
suggests that there may be something else going on.
Matthew, please could you describe what you did (before applying any
workarounds), what you expected to happen, and what actually happened,
including any syslog, Journal or web server log messages that look
potentially relevant?
S
