MySQL monitoring graph is not updating or blank in Munin

Munin is a network resource monitoring tool that can help to analyze and report back all kinds of server statistics. Munin is used to monitor the the performance of computers/servers, networks, SANs, applications, databases, weather measurements and other parameters.



To download and install Munin: click here



After successful installation, Munin will start colleting required data and will show you the graphs, including MySQL nodes such as MySQL throughputs, MySQL queries, MySQL Slow Queries, and MySQL threads. However, if you restart the server, Munin will fail to monitor MySQL nodes and it will stop showing graphs for MySQL.



Fix for Munin installed by cPanel/WHM



1. Find the path where mysqladmin is installed using one of the following commands:



which mysqladmin

type mysqladmin

locate mysqladmin



The above command will return a path to mysqladmin (i.e. /usr/bin/mysqladmin)



2. Edit Munin configuration file /etc/munin/plugin-conf.d/cpanel.conf and modify the [mysql*] as below:



[mysql*]

user root

group wheel

env.mysqladmin /usr/bin/mysqladmin

env.mysqlopts –defaults-extra-file=/root/.my.cnf



Ensure the env.mysqladmin value is path returned by step 1. Also ensure that /root/.my.cnf contains correct MySQL root password.



3. Restart Munin service:



/etc/init.d/munin-node restart



4. Wait a while for MySQL statistics to be gathered, and check the graphs again.



Fix for the host or server without cPanel Control Panel:



Simply add the “env.mysqladmin /usr/bin/mysqladmin” (ensure that the path is correct according to your system) to the /etc/munin/plugin-conf.d/munin-node file will do the trick.



Tags:-cPanel,Whm,Munin,network statistics,Munin Mysql monitoring is not showing

500 internal server issues

It is the most common php issue.ouurs mostly on servers with suPhp or PHP running as CGI.

Check the logs so that you can quickly find the issue:

/usr/local/apache/logs/error_log /usr/local/apache/logs/suphp.log

Here are some common errors:

SoftException in Application.cpp:357: UID of script "/home/user/public_html/test.php" is smaller than min_uid SoftException in Application.cpp:422: Mismatch between target UID (511) and UID (510) of file "/home/user/public_html/test.php"

SoftException in Application.cpp:264: File "/home/user/public_html/test.php" is writeable by others

These are all permission/ownership issues, indicating that the owner of the PHP file being called in incorrect, or the permissions are higher than what is allowed in suphp.conf.

Invalid directions in .htaccess

If you’re running PHP in CGI or suPHP mode, you can’t use php_flag or php_value directives in .htaccess – you either need to use htscanner to allow Apache to parse those commands, or make php-related changes in php.ini within the user’s account. You can check the Apache error log in /usr/local/apache/logs/error_log to see if you get something like this:

/home/user/public_html/.htaccess:

Invalid command 'php_flag', perhaps misspelled or defined by a module not included in the server configuration

If the error log indicates a problem with .htaccess, you need to remove the directives indicated and make sure your ssyntax is correct, and that they are in the correct places.

Incorrect ownership or permissions

You can adjust suPHP’s permissions allowances in /opt/suphp/etc/suphp.conf to allow ‘group’ and ‘other’ writable permissions if it’s necessary by modifying these values:

allow_file_group_writeable=false
allow_file_others_writeable=false
allow_directory_group_writeable=false
allow_directory_others_writeable=false

If the problem is with the min_uid value being too low (such as if you’re running a PHP script as root), you can also modify the “min_uid” and “min_gid” values to be more permissive. Changing anything in the suphp.conf requires a restart of Apache.

SuPHP binary missing its “sticky” permissions

Take a look at the suphp binary. It should look a bit like this, and in most shells, will be highlighted in red:

-rwsr-xr-x 1 root root 341K Mar 30 12:25 /opt/suphp/sbin/suphp*

If it’s missing the ‘s’ in the permissions column, you need to re-add the sticky bit to allow users on the system to execute it properly:

chmod +s /opt/suphp/sbin/suphp

Tags:-cpanel,cpanel issues,webhosting issues,cpanel admin,Linux,Linux techs