Thank you got it, Will update you once i perform a fresh install.
Any update to the issue, I re-installed OS performed a fresh install of Centmin again but again similar MYSQL issue, here is the Journal log Journal.log
hmmm. The issue should be fixed in 124.00stable and 130.00beta01 If you manually run these commands below, does MariaDB 10.3 start up? Only run these commands on a fresh install with no actual MariaDB MySQL databases imported. Code (Text): systemctl stop mariadb rm -f /var/lib/mysql/ib_logfile* rm -f /var/lib/mysql/aria_log* systemctl start mariadb
This did resolve the issue, Thank you but should i continue with this install or re-install? As i am configuring this server for my Live websites.
If you're using 130.00beta01, try a fresh install as I made one more update for MariaDB install routine to see if it helps.
@eva2000 And again MariaDB whining. Now a mirror that's acting up. Making it impossible to install Centminmod on a fresh server. Without excluding the mirror. This is yet another software package that doesn't work well. Whether it's the software itself or the mirror 'Damaged repomd.xml file'. Always something to struggle. I suggest an in-house mirror with software versions to managed by yourself. It has happened before that a software administrator removes his software (version) from the server. Server-mirror-hardware problems or else. Which leaves little Centminmod to install. Time to take matters into your own hands. Code: mariadb | 2.4 kB 00:00:00 https://mirrors.n-ix.net/mariadb/yum/10.3/centos7-amd64/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for mariadb: Damaged repomd.xml file Trying other mirror. One of the configured repositories failed (MariaDB), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=mariadb ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable mariadb or subscription-manager repos --disable=mariadb 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=mariadb.skip_if_unavailable=true failure: repodata/repomd.xml from mariadb: [Errno 256] No more mirrors to try. https://mirrors.n-ix.net/mariadb/yum/10.3/centos7-amd64/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for mariadb: Damaged repomd.xml file
problem is mirrors.n-ix.net mirror, I would of thought it would be stable hence i setup Germany or EU detected servers to use mirrors.n-ix.net mirror. from status page https://mirmon.mariadb.org/ seems ok though Unfortunately, setting up own local MariaDB mirror takes a lot of disk space for MariaDB 10.1 all the way to 10.9 !
Just too much work to just have a single point of failure again - you'd need multiple servers for redundancy - just not in the budget right now. For now, I've updated 130.00beta01 and switched out Germany/EU mirror target mirrors.n-ix.net
Yup therefore i wrote about 'excluding the mirror'. And yes checked the mirror status on Mariadb. Monitor uptime monitor is ok but the file repomd.xml seems not to be synced to the specific mirror. If setting your own mirror is a problem. Maybe you could specific and version lock the version and hash check the rpm's as you did with other downloadble content. Seems as the specific mirror is synced during the weekend. Which is not smart on MariaDB's part, anyway. Because most of the staff will be on weekend leave. Adding to that the fact that Mariadb has been managing to push a gawky releases more often lately. Just another reason to lock in the version. And only allow the script to upgrade to a newer update if there is ... hour no problems have been reported to Mariadb.
Indeed, that might be a way to double check FYI Mirror Sites for MariaDB as such ~500+ GB of disk space is needed.
Version lock and hash check could be the solution. Not @eva2000 fault for the general reader. It's been a mess for a while now since MariaDB believes it can do without MySQL.
Yeah I imagine they've heavily replying on individual distro OS's mirror systems so haven't put much investment into their own.
Looks like that mirror just hasn't been updated May 19, 2022 last update at https://mirrors.n-ix.net/mariadb/yum/10.3/centos7-amd64/repodata/ and empty repomd.xml versus working Index of /mariadb/yum/10.3/centos7-amd64/repodata with repomd.xml populated file
You could create your own repo with 'createrepo' on EL. No need to sync source, arm, and non supported versions anyway. Won't be too big in the end.
Yeah that is an option too. But for now rather not have the added work to maintain a repo Thanks for updating me - glad to hear