On 11/03/17 02:33, Matthew Gabeler-Lee wrote: > On Fri, 10 Mar 2017, Simon McVittie wrote: > >> 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? > > On closer inspection, I think I need to retract my prior statement. > > I had a problem with munin "not working at all" -- i.e. not collecting > data / updating charts, which correlated with an upgrade of the munin > package. > > 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. > > I think the suggestion that this in fact is not a bug and is just a > confusion with how munin works is correct. > > It is in fact /etc/cron.d/munin that does the "service" work of munin. > > Apologies for the confusion! >
I have discussed similar issue here: http://forums.debian.net/viewtopic.php?f=5&t=130106 |# systemctl enable munin.service Synchronizing state of munin.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable munin Failed to enable unit: Unit file /lib/systemd/system/munin.service is masked. In fact, things work because munin server relies on cron. Still, why has debian maint set an unusable | |munin.service ? In fact, before systemd, munin (server) did not need init script at all; so, writing a .service file for systemd may be useless. Unless you want to add features: a .service file could allow to start and stop munin. This could be an added value to recent Debian version. How to disable the server via a .service ? either add a dot in the name of the cron file, like |/etc/cron.d/munin.disabled (see man cron, it will refuse to run files with a dot), or, comment lines in that file. Yes, this could have been done in sysinit. But, if a .service is created (masked in our case, but still existing link to dev/null), please, make it usefull. Also, the .service file could clearly tell about it's dep upon cron (this is unclear for beginners; munin really does not work like other independant services: ssh, apache, samba ...). There is a .service file for the node; why not make the server one *usefull* ? -- >o_/ DEMAINE Benoît-Pierre (aka DoubleHP) http://benoit.demaine.info/ If computing were an exact science, IT engineers would'nt have work \_o< "So all that's left, Is the proof that love's not only blind but deaf." (FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)
