MySQL ignores a startup or configuration option because the supplied value is invalid, logging error 73 (EE_OPTION_IGNORED_DUE_TO_INVALID_VALUE).
MySQL Error 73: EE_OPTION_IGNORED_DUE_TO_INVALID_VALUE appears when the server or client skips a --option because its value is malformed or unsupported. Correct the value in my.cnf or the command line, then restart the service to resolve the issue.
%s: ignoring option '--%s' due to invalid value '%s'. EE_OPTION_IGNORED_DUE_TO_INVALID_VALUE was added in 8.0.13.
MySQL raises error 73 when it meets a command-line or configuration parameter whose value it cannot parse or validate. The server logs a message like mysqld: ignoring option '--max_connections' due to invalid value 'abc' and continues to start with the default value.
The condition name EE_OPTION_IGNORED_DUE_TO_INVALID_VALUE was added in MySQL 8.0.13, so earlier versions will log a generic warning instead.
Although the server keeps running, the ignored option may lead to unexpected performance or security issues.
The error arises when an option expects a numeric, boolean, or enumerated value but receives something else.
MySQL validates options early in startup, so mistakes in my.cnf, environment variables, or CLI arguments trigger the warning before any data processing occurs.
Copy-pasting configuration from another environment without checking version-specific changes also produces this error, because allowable ranges or names can differ between releases.
Locate the offending option in the error log entry, open the relevant .cnf file or script, and replace the invalid value with a supported one.
Restart the MySQL service and verify that the message no longer appears. Use SHOW VARIABLES LIKE 'option_name' to confirm the active value.
If you run MySQL from a shell, edit the startup script or Docker compose file. Validate numeric limits with the reference manual and test changes in a staging instance before promoting them to production.
Non-numeric strings passed to numeric parameters, such as --max_allowed_packet='one_gig', cause the option to be ignored.
Replace the text with an integer byte value: --max_allowed_packet=1073741824.
Boolean flags incorrectly assigned values trigger the error: --skip_log_bin=off. For simple toggles, omit the value and rely on the --skip_ prefix, or use --log_bin=0.
Keep configuration in source control and apply automated linting that checks option names and value types against the MySQL version you deploy.
Galaxy 2s SQL editor lets teams annotate startup settings in shared notebooks, making review and correction faster.
Use mysqld --verbose --help or mysqladmin variables to list valid options and ranges. Pin MySQL minor versions across environments to avoid silent semantic changes.
Error 74 (EE_OPTION_IGNORED_UNKNOWN_OPTION) appears when an unknown option name is provided. The fix is to remove or rename the parameter.
Error 3168 (ER_VARIABLE_IS_READONLY) occurs when attempting to change a read-only variable at runtime.
Use startup-only options or re-start the server.
.
No. The server skips the bad option and continues with defaults, but unexpected behavior may follow.
Ignoring it risks running with unintended defaults that hurt performance or security. Always correct the value.
Check the error log entry; it prints the option name and value. Use grep -i EE_OPTION_IGNORED for faster lookup.
Galaxy 2s shared SQL snippets and version control make it easier to document and review server settings, reducing bad config pushes.
.avif)
.avif){kind=logo}
