Resolving MySQL Privilege Table Missing Error: Complete Fix Guide for RHEL 5 Environment

Problem Background and Error Analysis

When installing MySQL server in RHEL 5 operating system environments, users frequently encounter startup failures due to missing privilege tables. The typical error message displays: [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist. This error indicates that core privilege tables in the MySQL system database were not properly created or initialized.

Root Cause Investigation

Missing privilege tables typically stem from several key factors: First, improper permission settings on the MySQL data directory prevent the mysqld process from accessing or creating necessary system tables. Second, during software package installation, database initialization steps might be skipped or incompletely executed. Additionally, residual files from previous installations may conflict with new installations.

Complete Solution Implementation

Based on validated effective methods, we recommend the following systematic resolution steps:

Step 1: Thorough Cleanup of Existing Installation

First, remove potentially problematic existing installations. Execute the following command to completely uninstall MySQL-related packages:

yum remove mysql*

Then manually delete residual directories and configuration files:

rm -rf /usr/bin/mysql
rm -rf /var/lib/mysql
rm -f /etc/my.cnf.rpm

Step 2: System Status Verification

Before reinstalling, ensure no MySQL-related processes are still running:

ps -e | grep mysql

If related processes are found, terminate them using the kill command. To thoroughly clear system state, recommend performing a server reboot:

reboot

Step 3: Reinstall MySQL Server

After system reboot, use the yum package manager to reinstall MySQL server:

yum install mysql-server

This command automatically installs the MySQL client as a dependency, ensuring component completeness.

Step 4: Permission Configuration and Database Initialization

After installation completion, the critical step is correctly setting data directory permissions. Execute the following commands to grant ownership and group permissions of the /var/lib/mysql directory to the mysql user:

chown -R mysql /var/lib/mysql
chgrp -R mysql /var/lib/mysql

Next, initialize the MySQL system database. Depending on the system environment, it may be necessary to specify base directory parameters:

mysql_install_db --user=mysql --ldata=/var/lib/mysql

In some distributions, if the MySQL package installation path differs from expectations, additional base directory specification may be required:

mysql_install_db --user=mysql --basedir=/usr/ --ldata=/var/lib/mysql/

Step 5: Service Startup and Verification

After completing the above configuration, start the MySQL daemon:

service mysqld start

Verify service status to ensure no error messages are output:

service mysqld status

Technical Points In-depth Analysis

Privilege tables form the core of MySQL's security mechanism. The mysql.host table stores host-level access permission information, and its absence prevents the entire privilege system from functioning normally. In Linux systems, correct file permissions and SELinux contexts are crucial for MySQL's proper operation.

Preventive Measures and Best Practices

To prevent similar issues from recurring, recommend following these best practices: Ensure system package managers are updated to the latest version before installation; Use official MySQL repositories rather than system default repositories; Consider using configuration management tools for automated deployment processes in production environments; Regularly backup MySQL data directories as a precaution.

Cross-Platform Applicability Explanation

Although this article uses RHEL 5 as the example environment, the core principles of the described solutions apply to most Linux distributions. The main differences between distributions lie in package manager commands and default installation paths, but the basic steps of permission setting and database initialization remain consistent.