MySQL Bugs: #7372: InnoDB not shut down properly when mysql.host missing

Bug #7372	InnoDB not shut down properly when mysql.host missing
Submitted:	17 Dec 2004 0:16	Modified:	17 Dec 2004 9:25
Reporter:	Jeremy Cole (Basic Quality Contributor) (OCA)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.7	OS:	FreeBSD (FreeBSD)
Assigned to:		CPU Architecture:	Any

Description:
InnoDB isn't shut down properly when mysqld exits due to missing privilege tables.

How to repeat:
Don't run mysql_install_db, but do configure InnoDB.  Start mysqld.

041216 16:11:10  InnoDB: Started; log sequence number 0 0
041216 16:11:10 [ERROR] Fatal error: Can't open privilege tables: Table 'mysql.h
ost' doesn't exist
041216 16:11:10  mysqld ended

041216 16:12:07  mysqld started
041216 16:12:07  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.

Jeremy,

for InnoDB, exit(1) is a totally legal way to shut it down. It will do a crash recovery at the next startup. I think it does not pay to shut it down gracefully in this case. Therefore I am changing the status of this bug report to 'Won't fix'.

Regards,

Heikki