Control Web Panel

WebPanel => MySQL => Topic started by: leebrimlow on August 17, 2024, 10:34:34 PM

Title: Can not update MariaDB
Post by: leebrimlow on August 17, 2024, 10:34:34 PM
Hello, I want to update MariaDB from 10.4 to 10.11

i followed the Wiki steps and got this error:


[root@panel ~]# yum -y update "MariaDB-*"
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
epel/x86_64/metalink                                                                                                            | 5.1 kB  00:00:00
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"


 One of the configured repositories failed (Unknown),
 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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: extras/7/x86_64
Title: Re: Can not update MariaDB
Post by: overseer on August 17, 2024, 11:36:50 PM
Now that CentOS is EOL, you should update your mirror list:
https://www.alphagnu.com/topic/534-fix-centos-7-repo-due-to-eol-could-not-retrieve-mirrorlist/ (https://www.alphagnu.com/topic/534-fix-centos-7-repo-due-to-eol-could-not-retrieve-mirrorlist/)
Title: Re: Can not update MariaDB
Post by: Starburst on August 18, 2024, 05:01:21 AM
I think some of the MariaBD mirrors are killing off CentOS also to save space.

So if you get errors there, don't be surprised.

Maybe try RHEL 7, if still an option.
Title: Re: Can not update MariaDB
Post by: leebrimlow on August 18, 2024, 10:42:18 AM
Thank you so much , your replies helped ot  :D
Title: Re: Can not update MariaDB
Post by: Namaste on May 21, 2025, 11:37:08 PM
Where is the tut on updated mysql 10.2
Title: Re: Can not update MariaDB
Post by: overseer on May 22, 2025, 12:48:19 AM
sorry, what?
Title: Re: Can not update MariaDB
Post by: Starburst on May 22, 2025, 09:26:40 PM
Erh?  ???

Do yo mean MariaDB 10.2? or MySQL (which current version is only 9.2.0)

If you do mean MariaDB 10.2, that version is way past EOL, so is 10.3, which ended 11 months ago (29 May 2024)
MariaDB 10.4 is a LTS that ends in in 4 years (29 May 2029).
Title: Re: Can not update MariaDB
Post by: overseer on May 22, 2025, 10:42:24 PM
I suppose you mean 11.4? I always refer to this chart for MariaDB version lifetimes:
https://endoflife.date/mariadb (https://endoflife.date/mariadb)
Title: Re: Can not update MariaDB
Post by: Starburst on May 22, 2025, 11:43:10 PM
If you look at the error also they are using CentOS 7, hence my reply back in August.

Guess they decided to stick with an EOL OS with no support.
I'm guessing it is MariaDB 10.2.  :-\