What action should you take to fix the error and allow the service to start?

Consider the MySQL Enterprise Audit plugin.
On attempting to start the MySQL service after a crash, notice the following error:
[ERROR] Plugin ‘audit_log’ init function returned error.
In the audit log file, you notice the final entry:
…
<AUDIT_RECORD
TIMESTAMP=”2013-07-09T02:12:35”
NAME=”Connect”
CONNECTION_ID=”98”
STATUS=”0”
USER=”Kate”
PRIV_USER=”kate”
OS_LOGIN=””
HOST=”localhost”
DB=””/>
What action should you take to fix the error and allow the service to start?

Consider the MySQL Enterprise Audit plugin.
On attempting to start the MySQL service after a crash, notice the following error:
[ERROR] Plugin ‘audit_log’ init function returned error.
In the audit log file, you notice the final entry:
…
<AUDIT_RECORD
TIMESTAMP=”2013-07-09T02:12:35”
NAME=”Connect”
CONNECTION_ID=”98”
STATUS=”0”
USER=”Kate”
PRIV_USER=”kate”
OS_LOGIN=””
HOST=”localhost”
DB=””/>
What action should you take to fix the error and allow the service to start?

A.
Re-install the audit plugin.

B.
Execute the command FLUSH LOGS.

C.
Execute the command SET GLOBAL audit_log_fiush= ON.

D.
Move or rename the existing audit.log file.

Explanation:

Show Hint

Leave a Reply 5

Your email address will not be published. Required fields are marked *

Jules

Jules

https://dev.mysql.com/doc/refman/5.6/en/audit-log-plugin-logging-control.html
If the log file exists at open time, the plugin checks whether the file ends with an tag and truncates it if so before writing any elements. If the log file exists but does not end with or the tag cannot be truncated, the plugin considers the file malformed and fails to initialize. This can occur if the server crashes or is killed with the audit log plugin running. No logging occurs until the problem is rectified.

Reply