Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41180 - [mariadb] Upgrading to 10.0.12 Requires Innodb Tables

Attached to Project: Arch Linux
Opened by Witit Sujjapong (bsujja) - Saturday, 12 July 2014, 23:01 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 26 July 2014, 15:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:After upgrading to 10.0.12-1, there are errors relating to innodb, although the database server seems to work alright.


Additional info:
* package version(s)
* config and/or log files etc.
Manually creating innodb related files per instruction here: http://dba.stackexchange.com/questions/54608/innodb-error-table-mysql-innodb-table-stats-not-found-after-upgrade-to-mys fixed the problem.

Steps to reproduce:Upgrade to 10.0.12-1 and check journalctl -f
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Saturday, 26 July 2014, 15:58 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Friday, 25 July 2014, 12:19 GMT
This should be handled by the mysql_upgrade script. We don't run these scripts on upgrades for the same reason we don't restart your services.
Comment by Bartłomiej Piotrowski (Barthalion) - Saturday, 26 July 2014, 08:14 GMT
I'm afraid that I'm unable to reproduce the problem, either on my servers and clean container. Have you executed mysql_upgrade after restarting the service?
Comment by Witit Sujjapong (bsujja) - Saturday, 26 July 2014, 15:51 GMT
In my case I didn't do mysql_upgrade. That must be the cause of my problem. If so, I'd agree this is not a bug.

Loading...