Munin not updating
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? On closer inspection, I think I need to retract my prior statement.
But on closer inspection, I realize two things happened that day, and it was actually the other thing that "broke" munin, and it was a mistake interpreting the munin status pages that made me thing the sysvinit workaround "fixed" it.
The sysvinit hack "fixing" things was a false positive, and it was really fixing the other problem (a network issue preventing data collection from most nodes) that made munin start working for me.
When using sysv init, the /etc/init.d/munin script does that, and exits.Package: munin Version: 2.0.25-1 Severity: normal Dear Maintainer, It seems the systemd control scripts are missing for this package.#systemctl restart munin.service gives this error message : Failed to restart munin.service: Unit munin.service is masked.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: Stretch currently, munin doesn't work at all.In fact, things work because munin server relies on cron.