Problem with MYSQL "mysql.host doesn't exist

[kaltera]

Hi,

I'm encountering a problem with mysql that doesn't want to start. I went into the logs and here comes the fatal error :

[ERROR] Fatal error: Can’t open and lock privilege tables: Table ‘mysql.host’ doesn’t exist

Anybody has an idea to solve that ?

Thank you

[phoenix]

Some idea of Zimbra version and operating system might help. Is this an upgrade, new install or running installation? Did you search the forums for the words "privilege tables", do any of those results help?

Please update your profile with the details from zmcontrol -v

[kaltera]

This is a new install, Zimbra 5.05 NE on Ubuntu 6.06 Server

I'm actually reading the 5 pages topic but doesn't seem to be a solution

i'm searching on the web aswell in case this is not a problem with Zimbra itself

[Krang]

Howdy,

I am also having the same problem as described. I have a new install on a new RHEL5 server. zimbra release 6.0.6_GA_2330 (network edition)

zmcontrol status shows the mailbox is stopped, mysql.server is not running.

I can see an error in the /opt/zimbra/logs/mysql_error.log and I have the entry :
[ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
mysqld ended

any help or pointers in the right direction are always appreciated.

Best regards,
Monte.

[Krang]

Originally Posted by Krang

Howdy,

I am also having the same problem as described. I have a new install on a new RHEL5 server. zimbra release 6.0.6_GA_2330 (network edition)

zmcontrol status shows the mailbox is stopped, mysql.server is not running.

I can see an error in the /opt/zimbra/logs/mysql_error.log and I have the entry :
[ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist
mysqld ended

any help or pointers in the right direction are always appreciated.

Best regards,
Monte.

I resolved my own issue.
I removed the OS/YUM installed version of mysql, and dependencies. Then I reinstalled the zimbra server with the install.sh script which added it's own mysql server, which operates under the /opt/zimbra/db/mysql directory with it's own dependencies.

Now my zimbra server starts and runs as expected.

I strongly recommend that the zimbra team add a check for existing mysql databases, and stop the installation at that point. Some documentation warning of this in the install/quick setup guide would be helpful as well.

best regards,
Monte.