CPANEL-40556 - DNS Only Manage Plugins
WHM/cPanel 102.0.11 (a version with horrible interface)
The Plugin Manager interface appears to have been removed, preventing for example munin, to be installed.
A manual invocation using cpsession ID and /scripts2/manage_plugins produces a 403 forbidden error.
Pre-existing 3rd party plugins, such as from waytotheweb/ConfigServer appear to be unaffected.
Since when was this removed and can we have it back?
Is there a backdoor method to install munin, meantime?
-
Thanks! Not so bad for only 4 additional nameservers but others may get frustrated. ;) (I started to think about a post-update script, to do the needful.) 0 -
I talked to the team, and we all agreed we don't like this behavior. I've opened case CPANEL-41346 to see if they can keep Munin from being removed during updates. I'll post more details once I hear back from the team. At that point, a post-upcp script is likely the best way to go to keep this around inside the WHM interface. 0 -
Just an update 'cos I've had a nameserver come back online, after a few weeks: Version 104.0.7 --> 104.0.10 [2022-08-24 17:53:09 -0400] Uninstalling unneeded rpms: cpanel-perl-532-date-manip cpanel-perl-532-rrds cpanel-munin cpanel-perl-532-net-server cpanel-rrdtool [2022-08-24 17:53:09 -0400] - uninstalling munin [2022-08-24 17:53:09 -0400] Removed /etc/systemd/system/multi-user.target.wants/munin-node.service. [2022-08-24 17:53:10 -0400] warning: /etc/munin/plugin-conf.d/cpanel.conf saved as /etc/munin/plugin-conf.d/cpanel.conf.rpmsave [2022-08-24 17:53:10 -0400] munin_addon unregistered
Sure glad of the instructions above. ;) Now where's that "chattr +i" ? ..0 -
Epilogue It seems that munin is also removed from standard WHM/cPanel installations too. :-( Rather than appending /etc/munin/plugin-conf.d/cpanel.conf, create /etc/munin/plugin-conf.d/custom.conf with the entries detailed in a previous post. Currently, this is preserved during the auto-removal and subsequent reactivation. Hey, at least we still get the spam-enabling mailman stuff! /s 0 -
@ejsolutions - that one I can't reproduce - I haven't seen Munin be removed as part of an update on a standard machine and couldn't make that happen with my testing just now. If you have a machine where that is happening, could you submit a ticket so we can do some more testing? 0 -
I haven't seen Munin be removed as part of an update on a standard machine
Thanks for the correction. Apologies, I appear to have been mistaken. Just ran a 11.104.0.10 to 11.106.0.4 upgrade and it has kept munin. Oops! :oops: i did have the config file set as immutable, however I see no evidence that an attempt to replace it was made. Still, creating a custom.conf is now my preferred method, to retain changes.0
Please sign in to leave a comment.
Comments
36 comments