Various Munin graph values 'nan' after upgrade to CLOUDLINUX 7.4
Hi, Gang.
I hope that all is well. Recently, I finished migrating to a CentOS 7.4 system and then did an in-place upgrade to use the CloudLinux kernel. Since that time, various Munin graphs have values as nan, i.e., "not a number". The graphs with these values are as follows:
Firewall Throughput
Netstat
VMstat
Swap in/out
The Munin version from the WHM 68.0.30 installed is 2.0.30-1.cp1162.
Does anybody have any idea how I can restore these graphs to their former glory?
Edited to Update: I uninstalled Munin and nuked /var/lib/munin, then reinstalled Munin. This resulted in Exim and Munin processing updating normally.
-
Hello, I'm glad to see you were able to solve the issue. Thank you for sharing the outcome. 0 -
Not quite. Only Exim and Munin processing were corrected. The other graphs remain problematic: Firewall Throughput Netstat VMstat Swap in/out 0 -
Hello, There's a CloudLinux forums thread on this topic at: Restrictions on Munin In that case, here's the response to the support ticket referenced by the user in that thread: [QUOTE]The virtualized filesystem is setup to prevent users from looking at the other users /proc/ processes. Since the user 'munin' is a regular user, we went to make sure that it could see /proc/ for the root user. It appeared that it wasn't. We used the GID for munin with the sysctl option: fs.proc_super_gid Once we added it, and restarted munin, the graphs started working. You may wish to give it some time to see it update for all the graphs, but on the 'daily' graphs are seeing some updates.
Here's the updated URL to the CloudLinux document referenced on that thread: CloudLinux Documentation Thank you.0 -
Thanks, Michael. Unfortunately, this made no difference. It's rather curious. All other graphs update normally. Just those four outliers. 0 -
Belay that. There was simply a longer delay than expected in repopulating those graphs. An hour later, all is working as I hoped. Super! Many thanks for your help and patience, Michael. 0 -
Hello, I'm glad to see the issue is now solved! Thank you for sharing the outcome. 0
Please sign in to leave a comment.
Comments
6 comments