Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

MYSQL is not starting after a improper shutdown

Joe Reyna August 7, 2012

We had to do a forceful shutdown on our confluence server and after it came up, then mysql wouldn't start all the way. It just keeps trying to start and I see these messages in the /var/mysql/*log:

120807 14:20:19 ERROR Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

120807 14:20:29 Warning Setting lower_case_table_names=2 because file system for /var/mysql/ is case insensitive

InnoDB: The InnoDB memory heap has been disabled.

InnoDB: Mutex and rw_lock use GCC atomic builtins.

InnoDB: The log sequence number in ibdata files does not match

InnoDB: the log sequence number in the ib_logfiles!

120807 14:20:29 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...

120807 14:20:29 InnoDB: Started; log sequence number 0 43655

120807 14:20:29 ERROR Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

3 answers

0 votes
Joe Reyna September 20, 2012

I think the problem was that we are using a separate DB on the server yet MySQL was still running and not configured properly. All is well now and was well even while I was getting those errors.

0 votes
Deleted user August 9, 2012

Is your mysql DB in the default location (/var/lib)?

If not, follow the below commands to fix this issue:

mysql_install_db –user=mysql –ldata=/newlocation

once you do that you can restart mysql

/etc/init.d/mysqld restart

The error basically means it can't find your DB.

0 votes
AlysonA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 9, 2012

Hello Joe,

I strongly believe this issue should be reviewed by your DBA, since it seems to be entirely database-related. Can you try reaching him on this and letting us know the results?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events