ARCHIVED: Troubleshooting common Legacy MySQL for Webserve issues

This content has been archived, and is no longer maintained by Indiana University. Information here may no longer be accurate, and links may no longer be available or reliable.
This content has been archived, and is no longer maintained by Indiana University. Information here may no longer be accurate, and links may no longer be available or reliable.
Note:
The Legacy MySQL for Webserve environment has been discontinued for most users, and will be completely retired July 31, 2018. If you have a Legacy MySQL account, you should migrate your service to the New MySQL for Webserve environment before that date. For more, see ARCHIVED: Migrate from Legacy to MySQL for Webserve service.
Important:
The Webserve and Webtest servers use PHP 7.1; PHP 5.6 has been retired and is no longer available. For more about PHP at IU, see PHP server-side scripting language.

On this page:

Correcting common errors

Access denied for user

The error message is similar to: 

 Warning: Access denied for user: 'username@lux.uits.indiana.edu' (Using password: YES) in /ip/account/wwws/index.php on line 5

This means that the user, in this case username, does not have the privileges necessary to access the MySQL database from lux (one of several backend webservers).

Correction

Grant privileges to the username specified in the error message. Instructions on how to grant privileges can be found at ARCHIVED: Legacy MySQL for Webserve privileges.

Access denied for user: username@localhost

This error may occur when attempting to execute the following command on the MySQL server: 

 mysql -u username -p

The access denied error message indicates that username as specified in the command above does not have privileges to access the database.

Correction

Grant the username the appropriate privileges. For example: 

 mysql> GRANT ALL ON *.* to username@localhost IDENTIFIED BY 'password';

You may specify which privileges are set by replacing ALL with the privileges that should be granted. You may also restrict privileges to a specific database rather than all by substituting *.* with the name of the database/table for which these privileges should apply.

For more about granting privileges and the various options available, see ARCHIVED: Legacy MySQL for Webserve privileges.

Unblock with mysqladmin flush-hosts

The error message is similar to: 

Error connecting to MySQL server. Host 'lux.uits.indiana.edu' is blocked because of many connection errors. Unblock with 'mysqladmin flush-hosts'

Correction

Log into your account on the MySQL server (mysql.iu.edu), and stop and restart your MySQL server. For more, see ARCHIVED: Starting/stopping the MySQL server for your account.

Error 28 from table handler/not enough space

This error message is usually accompanied by a message that indicates a space issue.

Correction

While this error message indicates a space issue, there are no disk quota enabled on mysql.iu.edu or mysql-test.iu.edu. Your master configuration file .my.cnf might need to be adjusted to accommodate more temporary tables during queries, etc. For assistance in making changes in your master configuration file, .

Account-related issues

Forgotten port number

Contact Web Services Support for assistance.

Unable to log into mysql.iu.edu with the port number provided

Your web applications use the MySQL port number to access your MySQL server on Webserve. When making an SSH connection, such as with the PuTTY client, a port number (22) is referenced; do not change it. Changing the port number will prevent you from being able to log into your account.

This is document bfor in the Knowledge Base.
Last modified on 2021-09-08 10:22:20.