after install virtualmin script, mysql can't be start

after install virtualmin script, mysql can't be start, therefore, I can't even pass preinstall stage. and there are the message from /var/log/mysql.log. The System is RHEL5 just install it and update to 5.4.

090909 12:04:04 mysqld started 090909 12:04:04 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295 090909 12:04:04 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295 InnoDB: Log scan progressed past the checkpoint lsn 0 36808 090909 12:04:05 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 0 43655 090909 12:04:05 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 090909 12:04:05 InnoDB: Started; log sequence number 0 43655 090909 12:04:05 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist 090909 12:04:05 mysqld ended

Status: 
Closed (fixed)

Comments

Are you trying to do the initial Virtualmin install, using the install.sh script?

If so, and if you don't have any data in MySQL that you care about, I would suggest removing it with the commands :

rpm -e mysql-server
mv /var/lib/mysql /var/lib/mysql.broken
rm -rf /etc/my.cnf*

Then re-running the Virtualmin install script , which will re-install MySQL with a fresh empty DB.

Don't do this if you already have data in MySQL though!

I find the soluation to fix my problem as following:

•Check to make sure that there is no firewall blocking access to MySQL. Your firewall may be configured on the basis of the application being executed, or the port number used by MySQL for communication (3306 by default). Under Linux or Unix, check your IP tables (or similar) configuration to ensure that the port has not been blocked. Under Windows, applications such as ZoneAlarm or the Windows XP personal firewall may need to be configured not to block the MySQL port. •The grant tables must be properly set up so that the server can use them for access control. For some distribution types (such as binary distributions on Windows, or RPM distributions on Linux), the installation process initializes the mysql database containing the grant tables. For distributions that do not do this, you must initialize the grant tables manually by running the mysql_install_db script. For details, see Section 2.17.2, “Unix Post-Installation Procedures”. To determine whether you need to initialize the grant tables, look for a mysql directory under the data directory. (The data directory normally is named data or var and is located under your MySQL installation directory.) Make sure that you have a file named user.MYD in the mysql database directory. If not, execute the mysql_install_db script. After running this script and starting the server, test the initial privileges by executing this command: shell> mysql -u root test The server should let you connect without error. •After a fresh installation, you should connect to the server and set up your users and their access permissions: shell> mysql -u root mysql The server should let you connect because the MySQL root user has no password initially. That is also a security risk, so setting the password for the root accounts is something you should do while you're setting up your other MySQL accounts. For instructions on setting the initial passwords, see Section 2.17.3, “Securing the Initial MySQL Accounts”.

Ok .. so did the install complete successfully now?

yes, it did, thank you very much!!

Automatically closed -- issue fixed for 2 weeks with no activity.