" .. that mysql_upgrade *complains* about", I meant. On Tue, Nov 24, 2015 at 3:01 PM, Peter Laursen <[email protected]> wrote:
> I think that maybe the MySQL installation was damaged before the OS > upgrade (for instance files accidentially deleted but going un-noticed). > > @Carl - do you have .frm, .MYI and .MYD files for the tables that > mysql_upgrade completes about? > > > -- Peter > > On Tue, Nov 24, 2015 at 2:27 PM, Reindl Harald <[email protected]> > wrote: > >> >> >> Am 24.11.2015 um 14:10 schrieb Carl Whalley: >> >>> This server just runs the tape backups so there are no users to worry >>> about. >>> I'm very out of my depth now, normally just use MySQL/Mariadb with a >>> little admin,. never had to repair this way. >>> >> >> i know it's too late, but normally before upgrades i just rsync >> /var/lib/mysql/ with all permissions and attributes to /var/lib/mysql-bkp/ >> the first time hot while the server is running, followed by stop the >> server, run rsync again to backup the fresh differences and get a >> consistent backup before doing the upgrades >> >> restore in the other direction is way faster then from external backups >> >> i still have no idea how that state coul have happened at all because >> F22->F23 has no version change for MariaDB, both have 10.0.x and even the >> F22 binaries are running unchanged after the dist-upgrade on my >> build/testserver before rebuild all self maintained packages >> >> P.S.: get rid of "reply-all" on mailing lists, i receive everytime your >> offlist copy and the message from the listserver is purged as duplicate >> which breaks reply-list and threading for anybody else >> >> On Tue, Nov 24, 2015 at 1:00 PM, Reindl Harald <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Am 24.11.2015 um 13:52 schrieb Carl Whalley: >>> >>> Oh boy ...well I did get the service to start this way at least, >>> but ... >>> >>> [root@tiger etc]# systemctl restart mariadb.service >>> [root@tiger tmp]# mysql >>> >>> >>> well, i see a lot of error i can't explain >>> >>> how many users do you have? >>> >>> i would try to purge the whole "mysql" folder after stop the service >>> and fire "mysql_install_db" to re-create the mysql-database or even >>> go so far to configure mysqld for a different datadir, initialize it >>> there and replace the "mysql" folder with the so new created >>> >>> on any of my setups the whole "mysql" database is MyISAM and so >>> table spaces should not matter, not sure if maraidb switched also to >>> "innodb" as default engine >>> >>> in doubt drop the whole database from your current instance runnign >>> with "skip-grant" before stop it to get rid of tablespace rferences >>> and at least for the fresh instance "default-storage-engine = myisam" >>> >>> that way you should be able to merge the new created mysql-database >>> with your current setup >>> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
