我刚安的MYSQL5无法启动，日志：

bqsc

[root@proxy var]# more proxy.err
060414 13:26:51  mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
060414 13:26:51  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
060414 13:26:53  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
060414 13:26:53  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
060414 13:26:55  InnoDB: Started; log sequence number 0 0
060414 13:26:55 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
060414 13:26:55  mysqld ended

060414 13:31:50  mysqld started
060414 13:31:53  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...
060414 13:31:54  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 36808.
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
060414 13:31:54  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
060414 13:31:54  InnoDB: Started; log sequence number 0 43655
060414 13:31:54 [Note] Recovering after a crash using mysql-bin
060414 13:31:54 [Note] Starting crash recovery...
060414 13:31:54 [Note] Crash recovery finished.
InnoDB: Apply batch completed
060414 13:31:54  InnoDB: Started; log sequence number 0 43655
060414 13:31:54 [Note] Recovering after a crash using mysql-bin
060414 13:31:54 [Note] Starting crash recovery...
060414 13:31:54 [Note] Crash recovery finished.
060414 13:31:55 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
060414 13:31:55  mysqld ended

060414 13:33:11  mysqld started
060414 13:33:11  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...
060414 13:33:11  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 36808.
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
060414 13:33:11  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
060414 13:33:11  InnoDB: Started; log sequence number 0 43655
060414 13:33:11 [Note] Recovering after a crash using mysql-bin
060414 13:33:11 [Note] Starting crash recovery...
060414 13:33:11 [Note] Crash recovery finished.
060414 13:33:11 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
060414 13:33:11  mysqld ended

什么原因啊？

bqsc

原来是这个mysql_install_db程序初始化没做好，但是我执行的时候，提示：

Neither host 'proxy' nor 'localhost' could be looked up with
/usr/local/mysql/bin/resolveip
Please configure the 'hostname' command to return a correct hostname.
If you want to solve this at a later stage, restart this script with
the --force option

怎么能够正常通过resolveip检测呢？

[ 本帖最后由 bqsc 于 2006-4-14 14:22 编辑 ]

bqsc

我现在把以前的数据库全部<导入新的MYSQL5,在使用phpmyadmin管理用户时，提示：
Warning: Your privilege table structure seems to be older than this MySQL version!
Please run the script mysql_fix_privilege_tables that should be included in your MySQL server distribution to solve this problem!

怎么能刷新用户表呢?

rainy_lsh

导入mysql库时,因为其中包含用户权限表及数据库权限表,所以需要刷新权限:flush privilieges  或者重启一下mysql

rardge

原帖由 bqsc 于 2006-4-14 14:22 发表
Warning: Your privilege table structure seems to be older than this MySQL version!
Please run the script mysql_fix_privilege_tables that should be included in your MySQL server distribution to solve this problem!

原因和解决方案它都提示你了，你把 4.x 版本的数据库直接导入到 5.0 的数据库，但是没考虑 5.0 可能已经变动过 mysql 数据库的设计了，所以提示 be older than this MySQL version。
它建议的解决方案就是执行脚本 mysql_fix_privilege_tables 来试试。

bqsc

太感谢楼上的了！！！