MySQL Bugs: #98256: setting audit-log from workbench and manually does not work ..server no start

Bug #98256	setting audit-log from workbench and manually does not work ..server no start
Submitted:	16 Jan 2020 16:36	Modified:	24 Mar 2020 14:49
Reporter:	Mx Dog	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S4 (Feature request)
Version:	8.0.16, 8.0.42	OS:	Windows (10 )
Assigned to:		CPU Architecture:	Any
Tags:	sever_logs audit_logs

Description:
I don't know if this is a workbench or server problem or both. I've gone over the text on the web site and could not get it to work on my server. 

setting these options in my.ini causes the server to not start from services.msc 

# Not Working

#audit-log = ON
#audit_log_file = "F:/Database/Mysql8/Logs/audit.log"
#audit_log_policy = LOGINS

At first I changed them from workbench then played with them by hand.

so if audit logs are not available in community edition ..workbench needs fixed to not show those options. 

and the server should ignore them in the options file.

IF it is a viable option in community then something is wrong with the server or the option names.

 

How to repeat:
put those options in my.ini and start server

Suggested fix:
possibly mark non-available or remove options from workbench if the server does not support them 

other then that 
NONE .. no idea what the problem stems from ..

Hello David Marlow,

Thank you for the feedback.
Agree, verifying as a feature request.

Regards,
Ashwini Patil

So did you determine which it is ?  
unavailable to community server ?  or a server options error ?

Bug #118608 marked as duplicate of this one.

Dear MySQL Team,

I hope this message finds you well. I’m writing to kindly inquire if there are any updates regarding a long-standing issue affecting MySQL Community Edition on Windows platforms. The bug, which appears to persist since January 16, 2020 (totaling 1,991 days as of July 9, 2025), causes the MySQL service to fail upon accidental misconfiguration by entry-level users.

Many new users encounter this when managing settings (e.g., accidental corruption of configuration files), leading to service startup failures. As the Community Edition is vital for learners and small-scale developers, this experience can be particularly discouraging.

Would you be able to share:

Any progress on resolving this issue?

If a fix is planned for upcoming releases?

Suggested workarounds for affected users meanwhile?

We truly appreciate your dedication to MySQL’s ecosystem. Thank you for your time and insights!

Best regards,
Anrew Cao