The MySQL Enterprise Audit Log Plugin Fails to Start After Unclean Shutdown; MySQL Aborts with audit_log = FORCE or FORCE_PLUS_PERMANENT
Last updated on NOVEMBER 18, 2016
Applies to:MySQL Server - Version 5.5 and later
Information in this document applies to any platform.
In versions prior to 5.6.24, the Audit Log plugin fails to start if the audit log is truncated or corrupted, if the Audit Log plugin has been configured with audit_log set to FORCE or FORCE_PLUS_PERMANENT, MySQL aborts the startup altogether. The error log shows this near the end of the start-up phase:
In versions 5.6.24 and newer, the server will start, and there will be appropriate error message about the failures encountered.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms