munin-node gets confused about the machine's name in some cases

Some users report munin is broken because munin and munin-node disagree about the name of the machine. I think this occurs if hostname (used by munin-node) reports a different name than PRIMARY_HOSTNAME (which we put in the munin config).

Hard-code PRIMARY_HOSTNAME in munin-node.conf.

Fixes #474.
See https://discourse.mailinabox.email/t/404-not-found-on-admin-munin/623/24.

CHANGELOG.md

@@ -20,6 +20,7 @@ System:
 * When upgrading, network checks like blocked port 25 are now skipped.
 * Tweaks to the intrusion detection rules for IMAP.
 * Improve the sort order of the domains in the status checks.
+* Munin was not working on machines confused about their hostname.
 
 v0.12c (July 19, 2015)
 ----------------------

setup/munin.sh

@@ -28,5 +28,9 @@ contact.admin.command mail -s "Munin notification ${var:host}" administrator@$PR
 contact.admin.always_send warning critical
 EOF
 
+# ensure munin-node knows the name of this machine
+tools/editconf.py /etc/munin/munin-node.conf -s \
+	host_name=$PRIMARY_HOSTNAME
+
 # generate initial statistics so the directory isn't empty
 sudo -u munin munin-cron