I understand your concern. My installation had a separate cnf file in the conf.d directory with a couple of personal settings affecting the mysqld, among them the old slow-query variables.
This was done in order to have the my.cnf upgrade smoothly among time. What happened is that mysql-server did not restart, probably throwing a complain but without stopping (and upgrading from 14.04 to 16.04 means 2900 MB of stuff to download, running on an SSD you really don't even notice what is passing on the screen!), the other packages complaining about not being able to connect to the socket... not exactly a good hint about the server being off. Only at the very end installation ended up with 2 packages misconfigured... I suggest instead of that behaviour to hang the upgrade in case mysql- server is not restarting with a notification showing the offending settings in order for the sysadmin to understand what is going wrong and act before going on. Hope this suggestion will be accepted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571865 Title: mysql fails to start after upgrade if previous defaults were customised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1571865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
