maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #03134
Re: After Fedora 22->23 update maria db doesn't start
-
To:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
From:
Reindl Harald <h.reindl@xxxxxxxxxxxxx>
-
Date:
Tue, 24 Nov 2015 12:40:45 +0100
-
In-reply-to:
<CALOnaUASCkzF-piYkqvvcYN-kxHf17XmY=o6Ez_h=8voQ4craQ@mail.gmail.com>
-
Openpgp:
id=13540402D67A7F71C6E974EA866063CF7F780279; url=https://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt
-
Organization:
the lounge interactive design
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
Am 24.11.2015 um 11:25 schrieb Carl Whalley:
From the log after systemctl restart mariadb.service:
InnoDB: wrong number of columns in SYS_INDEXES record
151124 9:51:40 [Note] InnoDB: Percona XtraDB (http://www.percona.com)
5.6.25-73.1 started; log sequence number 583845802
151124 9:51:40 [Note] Plugin 'FEEDBACK' is disabled.
InnoDB: wrong number of columns in SYS_INDEXES record
151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/plugin from
the internal data dictionary of InnoDB though the .frm file for the
table exists. See
http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for
how you can resolve the problem.
151124 9:51:40 [ERROR] Can't open the mysql.plugin table. Please run
mysql_upgrade to create it.
InnoDB: wrong number of columns in SYS_INDEXES record
151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/servers from
the internal data dictionary of InnoDB though the .frm file for the
table exists. See
http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for
how you can resolve the problem.
151124 9:51:40 [ERROR] Can't open and lock privilege tables: Table
'mysql.servers' doesn't exist in engine
151124 9:51:40 [Note] Server socket created on IP: '::'.
151124 9:51:40 [ERROR] Fatal error: mysql.user table is damaged or in
unsupported 3.20 format.
151124 09:51:40 mysqld_safe mysqld from pid file
/var/run/mariadb/mariadb.pid ended
i wonder what is going wrong here because Fedora 22/23 have the same
MariaDB version when i look at
https://koji.fedoraproject.org/koji/packageinfo?packageID=15262
since i use my self-compiled packages with unchanged SPEC files from
Fedora 21 to Fedora 23 without any issues i suggest ask the Fedora
package maintainers
anyways, mysql_upgrade can't work when the server don't start at all
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References