I build munin-node from source on my servers, as I then get things set up exactly how I want it, and it's a reliable way to have munin-node without the full munin. I've learnt that on 11.36, I need to change target_settings: munin to "unmanaged" in /var/cpanel/rpm.versions.d/local.versions. If it says "installed", the cPanel RPM maintains the installation.
Well, last night during nightly upcp, I got a notification from lfd that /etc/init.d/munin-node had been altered. So I had a look, and my munin master had stopped receiving updates from that node a few minutes earlier. This was because the remote IP was no longer Allowed in /etc/munin/munin-node.conf. Sure enough as I suspected, cPanel's nightly update had updated Munin for me, to 1.4x (from the 2.1x that I had compiled from source).
I then checked /var/cpanel/rpm.versions.d/local.versions, because this is supposed to prevent this. Munin had changed from unmanaged to installed.
Surely, /scripts/upcp should respect, rather than overwrite, target_settings in the local.versions file?
This is the second time this has happened to me - the previous occurrence was on a different server during a different upcp run.
Well, last night during nightly upcp, I got a notification from lfd that /etc/init.d/munin-node had been altered. So I had a look, and my munin master had stopped receiving updates from that node a few minutes earlier. This was because the remote IP was no longer Allowed in /etc/munin/munin-node.conf. Sure enough as I suspected, cPanel's nightly update had updated Munin for me, to 1.4x (from the 2.1x that I had compiled from source).
I then checked /var/cpanel/rpm.versions.d/local.versions, because this is supposed to prevent this. Munin had changed from unmanaged to installed.
Surely, /scripts/upcp should respect, rather than overwrite, target_settings in the local.versions file?
This is the second time this has happened to me - the previous occurrence was on a different server during a different upcp run.
