The error is due to a bug in a Perl library Munin uses which causes $PATH variable to be lost, and then causes the plugin cannot find the mysqladmin program which it needs to retrieve the numbers to populate in the graphs. Uninstall and reinstall Munin Service Monitor may make it works again, however, a more permanent solution is to hardcode the path of the program, which will fix the problem. Here the guide on how to specify the path to mysqladmin to Munin.

Fix for Munin installed by cPanel/WHM

   1. Determine where is mysqladmin program located with the one of the following command:

      which mysqladmin
      type mysqladmin
      locate mysqladmin

      If should return a path to mysqladmin which looks similar or the same to /usr/bin/mysqladmin.

   2. Edit the /etc/munin/plugin-conf.d/cpanel.conf Munin configuration file, and modify the [mysql*] to look like below:
      [mysql*]
      user root
      group wheel
      env.mysqladmin /usr/bin/mysqladmin
      env.mysqlopts –defaults-extra-file=/root/.my.cnf
Read the rest of this entry…

Phpmyadmin is a free software tool written in PHP intended to handle the administration of MySQL over the World Wide Web. phpMyAdmin supports a wide range of operations with MySQL. Since Windows doesn’t include a GUI  managment tool for Mysql, you will need to install phpMyadmin to acess a GUI  rather than administratering Mysql via the command line interface.

Please be sure that your php installation already has the GD/GD2 Library, Mysql and MBString extensions active. You can see this by going to your IIS server and accessing the php test page. If you do not have one, you can make one by going to “C:\inetpub\wwwroot\ and my creating a text with the following line;

<? phpinfo(); ?>

Save the file as phptest.php.

This will allow you to goto Http://localhost/phptest.php. If you don’t see the Mysql or MBstring sections, you will need to have them enabled to proceed as phpMyadmin requires this.
Read the rest of this entry…

I’ve found that in my journies, the easist way to reset a mysql password, assuming you have SSH / Shell access is to log into the server and change it. To do this, you need to do the following;

1. Login to the server via SSH.

2. Once logged in, you’ll need to modify the my.cnf file to force your mysql to skip the grant tables. This will allow you to reset mysql so you can gain access without providing the password. One of the benefits of SSH access.

The my.cnf file will look like this;

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
#skip-grant-tables  <— This is the line we add. Remove the # to enable it. Once done remove that or place the # back into place.
[mysql.server]
user=mysql
basedir=/var/lib

[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

3. Now that you added this, reset mysql.

4. Once mysql is restarted, you can gain access to it directly by typing ;

$ mysql -u root

It may ask for a password, but you can ignore it.

5. Now that you are logged in, will need to access the mysql database;

use mysql;

6. Lastly, we need to change the password by running the following;

UPDATE user SET password=PASSWORD(’newpassword’) WHERE user=’root’;

7. Now you can remove the line in the my.cnf that we added in step 2. Once you remove it, save the configuration and restart mysql.

That’s it. The password has been changed!

MySQL max_allowed_packet

In which case, try adding one to your my.cnf file;

set-variable=max_allowed_packet=xM
Change ‘x’ to 1 (or increase it if you’re still getting errors)

If you are using the mysql client program, its default max_allowed_packet variable is 16MB. That is also the maximum value before MySQL 4.0. To set a larger value from 4.0 on, start mysql like this:

mysql> mysql –max_allowed_packet=32M

That sets the packet size to 32MB.

The server’s default max_allowed_packet value is 1MB. You can increase this if the server needs to handle big queries (for example, if you are working with big BLOB columns). For example, to set the variable to 16MB, start the server like this:

mysql> mysqld –max_allowed_packet=16M

Before MySQL 4.0, use this syntax instead:

mysql> mysqld –set-variable=max_allowed_packet=16M

You can also use an option file to set max_allowed_packet. For example, to set the size for the server to 16MB, add the following lines in an option file:

[mysqld]
max_allowed_packet=16M

Before MySQL 4.0, use this syntax instead:

[mysqld]
set-variable = max_allowed_packet=16M

It’s safe to increase the value of this variable because the extra memory is allocated only when needed. For example, mysqld allocates more memory only when you issue a long query or when mysqld must return a large result row. The small default value of the variable is a precaution to catch incorrect packets between the client and server and also to ensure that you don’t run out of memory by using large packets accidentally.

You can also get strange problems with large packets if you are using large BLOB values but have not given mysqld access to enough memory to handle the query. If you suspect this is the case, try adding ulimit -d 256000 to the beginning of the mysqld_safe script and restarting mysqld.

The max_allowed_packet option specifies how large your MySQL Query/Data Packet can be, and NOT the Maximum File Size that MySQL can maintain. MySQL can theoretically handle database files upto 1 Terrabyte in size.

Error: Fantastico is unable to connect to your MySQL server at this time.

If you are trying to access your Fantastico instance and are not able to access it, there are several things you can try;

This problem can be caused by a wide variety of issues, please run through the following checklist:

1.) Restart MySQL on your server. Watch for errors. If MySQL doesn’t restart successfully, skip to #5 and try that next. (Note that in some rare instances, clients report the need to restart their server to get MySQL working properly.)
2.) The cPanel account is out of disk space or out of available mysql slots. Increase one or both of these and try again.
3.) The cPanel account account reports plenty of available disk space and mysql slots, but the user data/plan assignment is corrupt. Try assigning the account to a new featureset/hosting plan and see if that resolves it. If so, you may need to recreate or reassign the original plan to get things working again.
4.) The server itself is out of disk space on one or more partitions. Clean out unneeded files or accounts in this case.
5.) MySQL is malfunctioning on the server or the Perl DBD module is corrupt or missing. Run /scripts/mysqlup –force via SSH as root and watch for errors if any.
6.) The backend version of PHP is corrupt. Check the items here for a resolution:
http://netenberg.com/forum/viewtopic.php?t=1960.0
7.) If this only affects a single account, the account data may be corrupt. Do a full backup of the account, terminate it and then use the full backup to restore the account.
8.) Ensure your server is running Perl 5.8.8 (or whatever the latest approved version from cPanel Inc. happens to be — see http://layer1.cpanel.net/ ). Fantastico does not use Perl, but cPanel uses it extensively and if Perl isn’t a recent version, cPanel and thus Fantastico will have problems.
9.) Ensure you’re using the latest version of cPanel for your preferred build track. Run /scripts/upcp –force (or force the cPanel update from WHM) to make sure all files are installed and are the latest versions. If you run EDGE, try backing down to Current, Release or Stable and see if that helps.
10.) If all else fails, try removing Fantastico:
http://www.netenberg.com/forum/index.php?topic=3164.0
and reinstalling it:
http://www.netenberg.com/forum/index.php?topic=950.0

HOWEVER!!!!!!!

Before you try any of those recomended fixes, simply SSH to the server and goto /usr/local/cpanel/3rdparty/fantastico/includes/mysqlconfig.php and look for the following;

if ( ‘mysqlconfig.php’ == basename ( $_SERVER['PHP_SELF'] ) ) { die ( __FILE__ ) ; }

$MYSQLHOST = “127.0.0.1″ ;
$MYSQLPATH = “mysql” ;
If the path shows $MYSQLHOST = “localhost” , it needs to be changed to $MYSQLHOST = “127.0.0.1″ and save it in the file and also into a file called mysqlconfig.local.php (if doesn’t exist, create it).

Once you do this, you can restart mysql and Fantastico should connect again.