Thanks . I tried also the obvious, complete removal and reinstallation with the same results :-( [root@tiger log]# dnf remove mariadb mariadb-server Dependencies resolved. ============================================================================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================================================================= Removing: mariadb x86_64 1:10.0.21-1.fc23 @updates 37 M mariadb-server x86_64 1:10.0.21-1.fc23 @updates 86 M Transaction Summary ============================================================================================================================================================================================================================================= Remove 2 Packages Installed size: 124 M Is this ok [y/N]: y Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Erasing : mariadb-server-1:10.0.21-1.fc23.x86_64 1/2 Erasing : mariadb-1:10.0.21-1.fc23.x86_64 2/2 Verifying : mariadb-server-1:10.0.21-1.fc23.x86_64 1/2 Verifying : mariadb-1:10.0.21-1.fc23.x86_64 2/2 Removed: mariadb.x86_64 1:10.0.21-1.fc23 mariadb-server.x86_64 1:10.0.21-1.fc23 Complete! [root@tiger log]# dnf install mariadb mariadb-server Failed to synchronize cache for repo 'Dropbox' from ' http://linux.dropbox.com/fedora/23/': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried, disabling. Last metadata expiration check performed 1:07:58 ago on Tue Nov 24 10:51:11 2015. Dependencies resolved. ============================================================================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================================================================= Installing: mariadb x86_64 1:10.0.21-1.fc23 updates 6.0 M mariadb-server x86_64 1:10.0.21-1.fc23 updates 18 M Transaction Summary ============================================================================================================================================================================================================================================= Install 2 Packages Total download size: 24 M Installed size: 124 M Is this ok [y/N]: y Downloading Packages: (1/2): mariadb-10.0.21-1.fc23.x86_64.rpm 1.8 MB/s | 6.0 MB 00:03 (2/2): mariadb-server-10.0.21-1.fc23.x86_64.rpm 1.1 MB/s | 18 MB 00:16 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 1.3 MB/s | 24 MB 00:18 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Installing : mariadb-1:10.0.21-1.fc23.x86_64 1/2 Installing : mariadb-server-1:10.0.21-1.fc23.x86_64 2/2 Verifying : mariadb-1:10.0.21-1.fc23.x86_64 1/2 Verifying : mariadb-server-1:10.0.21-1.fc23.x86_64 2/2 Installed: mariadb.x86_64 1:10.0.21-1.fc23 mariadb-server.x86_64 1:10.0.21-1.fc23 Complete! [root@tiger log]# systemctl restart mariadb.service Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. [root@tiger log]# On Tue, Nov 24, 2015 at 11:40 AM, Reindl Harald <h.reindl@thelounge.net> wrote:
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
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp