Skip to main content

Munin Graph

Comments

13 comments

  • cPanelMichael
    Hello @zye, Could you try manually initiating the munin cron job to see if it successfully generates the graph? You can use these commands while logged in as the "root" user:
    su - munin --shell=/bin/bash /usr/local/cpanel/3rdparty/perl/522/bin/munin-cron exit
    Thank you.
    0
  • kdean
    i am running 2.0.25-6.cp1158 and my graph for exim mail throughput stopped. only 1 graph but it is very important for me that this one works. any ideas?

    I had noticed the same with related errors in /var/log/munin/munin-node.log Error output from exim_mailstats: Error in tempfile() using template /var/lib/munin/plugin-state/nobody/XXXXXXXXXX: Could not create temp file /var/lib/munin/plugin-state/nobody/2Onyek2qTp: Permission denied at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Munin/Plugin.pm line 280. I added group write permissions to /var/lib/munin/plugin-state/nobody/ and that seemed to fix things. I'm still reverting the http_loadtime plugin to a 1.x version since the 2.x version doesn't work at all.
    0
  • cPanelMichael
    Hello, Internal case CPANEL-9353 is open to address an issue where the "Exim Mail Throughput - by day" and "Exim Mail Throughput - by week" graphs are not working after the update to Munin 2.x. Here's an example of the error output you may notice:
    2016/10/11-21:55:03 [10610] Error output from exim_mailstats: 2016/10/11-21:55:03 [10610] Error in tempfile() using template /var/lib/munin/plugin-state/nobody/XXXXXXXXXX: Could not create temp file /var/lib/munin/plugin-state/nobody/CQbZki3PaU: Permission denied at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Munin/Plugin.pm line 280. 2016/10/11-21:55:03 [10610] Service 'exim_mailstats' exited with status 13/0. 2016/10/11-21:55:03 [10623] Error output from exim_mailstats: 2016/10/11-21:55:03 [10623] Error in tempfile() using template /var/lib/munin/plugin-state/nobody/XXXXXXXXXX: Could not create temp file /var/lib/munin/plugin-state/nobody/v5NO1SPKad: Permission denied at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Munin/Plugin.pm line 280.
    This behavior looks to be by design from Munin, designed to prevent arbitrary commands ran as root on behalf of an unprivileged user, however I'll update this thread with more information on the status of this case as it becomes available. Thank you.
    0
  • zye
    any news on this?
    0
  • zye
    i got it to work again the permissions are chown root /var/lib/munin/plugin-state/root/ chown nobody /var/lib/munin/plugin-state/nobody/ drwxr-xr-x 2 nobody munin 4096 Jan 30 14:55 nobody/ drwxr-xr-x 2 root munin 4096 Jan 30 14:55 root/ now the exim throughput works again
    0
  • cPanelMichael
    Hello, There's no update to report on the status of internal case CPANEL-9353 at this time. I'll update this thread as soon as more information is available. Thank you.
    0
  • dezignguy
    I had this same issue come up after an upgrade jump from v60 to v64 on CentOS 6.9. Munin 2.0.25 was already installed and working previous to the upgrade, and then afterwards it was complaining about all sorts of permission errors. Changing the dir ownership as above seems to have gotten it working again for the graphs.
    0
  • dezignguy
    It seems that there are still various permissions issues though... but at least Exim seems to be working
    2017/07/22-15:00:01 CONNECT TCP Peer: "[::ffff:127.0.0.1]:55152" Local: "[::ffff:127.0.0.1]:4949" 2017/07/22-15:00:02 [5708] Error output from yum: 2017/07/22-15:00:02 [5708] Can't open /var/lib/munin/plugin-state/root/yum.state for reading: No such file or directory 2017/07/22-15:00:02 [5708] Please read 'munindoc yum' to understand why if the file does not exist. 2017/07/22-15:00:02 [5708] Service 'yum' exited with status 2/0. 2017/07/22-15:00:03 [5708] Error output from bind9_rndc: 2017/07/22-15:00:03 [5708] WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf) 2017/07/22-15:00:03 [5708] rndc: error: none:0: open: /etc/rndc.conf: permission denied 2017/07/22-15:00:03 [5708] rndc: could not load rndc configuration 2017/07/22-15:00:03 [5708] /etc/munin/plugins/bind9_rndc: /var/run/named.stats: No such file or directory 2017/07/22-15:00:03 [5708] Service 'bind9_rndc' exited with status 2/0. 2017/07/22-15:00:03 [5708] Error output from bind9_rndc: 2017/07/22-15:00:03 [5708] WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf) 2017/07/22-15:00:03 [5708] rndc: error: none:0: open: /etc/rndc.conf: permission denied 2017/07/22-15:00:03 [5708] rndc: could not load rndc configuration 2017/07/22-15:00:03 [5708] /etc/munin/plugins/bind9_rndc: /var/run/named.stats: No such file or directory 2017/07/22-15:00:03 [5708] Service 'bind9_rndc' exited with status 2/0. 2017/07/22-15:00:09 [5708] Error output from http_loadtime: 2017/07/22-15:00:09 [5708] /etc/munin/plugins/http_loadtime: line 78: syntax error: unexpected end of file 2017/07/22-15:00:09 [5708] Service 'http_loadtime' exited with status 2/0. 2017/07/22-15:00:09 [5708] Error output from http_loadtime: 2017/07/22-15:00:09 [5708] /etc/munin/plugins/http_loadtime: line 78: syntax error: unexpected end of file 2017/07/22-15:00:09 [5708] Service 'http_loadtime' exited with status 2/0.
    0
  • zye
    same happend again on update to v66.0.17 chown root /var/lib/munin/plugin-state/root/ chown nobody /var/lib/munin/plugin-state/nobody/ did the trick
    0
  • cPanelMichael
    Hello, To update, internal case CPANEL-9353 was closed as it appears this only happened on updates from earlier versions of cPanel & WHM and is no longer occurring. Thank you.
    0
  • jmginer
    Same issue after upgrading to v70 To fix:
    chown root /var/lib/munin/plugin-state/root/ chown nobody /var/lib/munin/plugin-state/nobody/
    0
  • ScarecrowB1
    Just received the same error. Fresh install of Munin via WHM 110.0.6
    0
  • cPRex Jurassic Moderator
    @ScarecrowB1 - were you able to run the commands above to fix the permissions? If so, did that help?
    0

Please sign in to leave a comment.