Verified:
echo "invalid_mysql_option=foo" >> /etc/mysql/my.cnf.
Then on upgrade it should fail to start and complain - now with a reasonable message.
Going from Trusty -> Xenial-Proposed now with aforementioned change in place I see:
ERROR: Unable to start MySQL server:
2016-07-20T13:15:02.743028Z 0 [ERROR] unknown variable 'key_buffer=16M'
2016-07-20T13:15:02.746251Z 0 [ERROR] Aborting
Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues.
That is one of the old variables (now key_buffer_size) which just reflects what would happen on old custom-config.
=> Verified
Verified: mysql_option= foo" >> /etc/mysql/my.cnf.
echo "invalid_
Then on upgrade it should fail to start and complain - now with a reasonable message.
Going from Trusty -> Xenial-Proposed now with aforementioned change in place I see:
ERROR: Unable to start MySQL server: 20T13:15: 02.743028Z 0 [ERROR] unknown variable 'key_buffer=16M' 20T13:15: 02.746251Z 0 [ERROR] Aborting /wiki.debian. org/Teams/ MySQL/FAQ for tips on fixing common upgrade issues.
2016-07-
2016-07-
Please take a look at https:/
That is one of the old variables (now key_buffer_size) which just reflects what would happen on old custom-config.
=> Verified