all seems to be fine and well… BUT not everything:
mariadb/mysql on my “server” is no longer working…
it seems that it could be a corrupted file… THE most important file… (ibdata1)
but I’m not yet convinced…
** - could it be that the upgrade broke the database or the database file or … ?? OR… it was just a BIG coincidence ? Any ideas?
**as a side note… this “server” had been running 24/7 for several months without any problem (with 15.2)… and this makes me suspect that indeed it was not a coincidence…
2021-06-11 15:05:32 0 [ERROR] InnoDB: Invalid flags 0x4800 in ./ibdata1
2021-06-11 15:05:32 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
this is not critical to me because I can recreate the databases from SVN… but it means that I will (or lost already) some data… plus, it will give me the work of setting the databases again and so on… so, not so great
Anyone with the same problem? or anyone had this already and knows a fix?
Please always include the line with the command together with the output. And do not leave out lines (except when it is very, very long). Now we have only some lines without any informationabout what you did to get them.
The strange fact here is not replacing mysql with mariadb because this is the default behavior since some years (maybe from opensuse 42)
the strange is that you replaced mariadb with mysql and you forgot it
While it is true that mariadb Obsoletes mysql and mysql-server-community Provides mysql, so mariadb replaces it, the package mysql-server-community 8.0.25-1.sl15 is not from openSUSE, so it has different vendor and I would not expect it to be removed without any warning.
so OP got what was asked for - zypper got carte blanche to switch vendor.
Yet another example that one should never blindly execute random commands one happened to have found on Internet without actually understanding what these commands do and (probably, more important) why exactly those commands were suggested.
I forgot it? You might think this is funny… but it is not.
I upgraded the OS… I was not expecting that by upgrading the OS… the database would be replaced… my mysql database has nothing to do with the OS.
and btw… I’m not an expert in opensuse or linux… I use it because I like it… and have been using Linux for decades… from the time that configuring wifi was an herculean task for several days with lots of debugging and try/error…
Anyway… did your comment help? No, it did not.
did I receive any warning about this replace during the upgrade?
honestly I don’t know. I did the upgrade on my laptop (that doesn’t have mysql) and all went well… so days after I did the same on my home server… and did not pay much attention… it was just go go go… and the server has much more stuff… svn, nfs, backups, databases, web server and so on and so on… but like I said… I took measures… but did not expect the upgrade to touch my databases.
if you bother to read my upgrade post… you will see that I did my upgrade without that parameter.
I suggested that parameter to a user that had +200 conflicts to solve… and some moderator edited my post (as it is stated there)… if you read…
And I don’t copy/paste commands… either I know what commands do, or I read/investigate to learn what commands/options/parameters do.
I’m not an expert… but I’m not that dumb
I try to stay objective, so, just a request in advance: If anyone feels offended by my post, I’m sorry. I noticed this already heated up a bit and I don’t want to “spill oil into the fire”, but do want to throw in my two cents:
In fact: I’m using opensuse on my server for quite a few years now, starting back from somewhen around mid-2014 - so it was some 13.x back then - or maybe even some 12.x - don’T remember, I have to look it up in some time chart. Back then MySQL was still the main vendor on a clean install. I don’t remember the exact version, but if I have to guess it maybe was already in some 13.x - or maybe with the first 42 release - but opensuse switched to MariaDB a few years ago. So, anyone still using MySQL had to set it specific at some point in the past. Hence I’m more tend to go with Max here: At some point in the past you decided to stick to MySQL and didn’t move over to MariaDB when opensuse did. Now it bid you in the arse as, for whatever reason, your upgrade just now switched the vendor from MySQL to MariaDB - something opensuse did a few years ago - and MariaDB and MySQL already diverged enough so the current MariaDB server is no longer able to read files written by MySQL v8.
A possible solution could be to copy over the data files onto another system still running leap 15.2 and MySQL v8 which should be able to load the data and migrate them via database-vendor independed SQL.
In addition to that: Although I still have no explanation, for some reason it seems that the binaries availble from the opensuse repos are in some way altered than what one gets from mariadb.org repo. I’m using Apache James for years now, and every time I upgrade to the new release I get some strange exception when setting up the database when using the opensuse version. Switching to the mariadb.org repo anything works fine. I also had two threads about it - but both still not got any conclusion as for WHY this happen. So, although that MAY be just some special edge case I experience with my Apache James mail server when setting up the database - at least I personally would recommend to ditch what ever you got from the opensuse repos - add the mariadb.org repo and use it instead. Be aware: That still wouldn’t solve your issue as that’s still some specific to the differences between MariaDB and MariaDB.
cryptearth,
I have been using opensuse for quite some time… and so upgrading from version to version… and my mysql 8 database has been there working quietly and fine for quite some time…
I had no ideia about opensuse including mariadb and not mysql… And honestly… I don’t care… just that before… for example, when I did the upgrade to 15.2… mysql was there and remained there.
Anyway, I’m now using maria!
I recreated my dbs from svn… loaded the data… all is back online… except that now my dbs are maria
about getting offended… no no… all is good and fine no stress… peace!
and thanks for your two cents
-rw-r--r-- 1 root root 264 10 jun 18:03 mariadb-10.5.8-1.5-something
BORG:/var/adm/update-messages # more mariadb-10.5.8-1.5-something
WARNING: You are upgrading from different stable version of MySQL!
Your database will be migrated automatically during next restart of MySQL.
Before you do that make sure you have up to date backup of your data. It
should be mainly in /var/lib/mysql directory.
BORG:/var/adm/update-messages #
Glad to hear you were able to restore your data from a backup / another source.
~ rest of wall-of-text cut due to not fit into this topic
if someone is interested in some issues about MySQL vs MariaDB on opensuse over the years in combination with using it for managing two redundant e-mail-servers - hit me up
