I guess the determination of bug vs local configuration problem is rather subjective. I am able to get around the problem by removing innodb_additional_mem_pool_size from the config file. So from that perspective it could be viewed as a local problem.
But, innodb_additional_mem_pool_size seems to be a valid parameter in 5.5, at least there are no complaints when I start up a 5.5 system using that. If 5.5 -> 5.7 is a valid upgrade path, then the upgrade process should handle an obsolete parameter gracefully. Let me know if you'd like to see the my.cnf from my 5.5 system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622659 Title: package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1622659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
