Major Issues Lately with MariaDB Upgrades and Updates via WHM

[HenrikSCH]

Working now .. thank you for your help

 

[HenrikSCH]

Now i have another issue MariaDB stopped working today .. no idea why .. i was not on the server when it happened.

(XID 2qsvqs) The “mysql” service is down. The subprocess “/usr/local/cpanel/scripts/restartsrv_mysql” reported error number 2 when it ended.

Aug 19 18:05:54 host.****.com systemd[1]: Starting MariaDB 10.6.9 database server... Aug 19 18:05:54 host.****.com mariadbd[757800]: 2022-08-19 18:05:54 0 [Note] /usr/sbin/mariadbd (server 10.6.9-MariaDB) starting as process 757800 ... Aug 19 18:05:54 host.****.com mariadbd[757800]: 2022-08-19 18:05:54 0 [Warning] Could not increase number of max_open_files to more than 32768 (request: 640863) Aug 19 18:05:54 host.****.com mariadbd[757800]: 2022-08-19 18:05:54 0 [Warning] Changed limits: max_open_files: 32768 max_connections: 800 (was 800) table_cache: 15969 (was 40000) Aug 19 18:05:56 host.****.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Aug 19 18:05:56 host.****.com systemd[1]: mariadb.service: Failed with result 'exit-code'. Aug 19 18:05:56 host.****.com systemd[1]: Failed to start MariaDB 10.6.9 database server.

How to fix the i already tried to set /usr/lib/systemd/system/mariadb.service to

# Number of files limit. previously [mysqld_safe] open-files-limit
LimitNOFILE=infinity
and
LimitNOFILE=650000

But none of them did it .. how do i fix this?

 

[vacancy]

Unable to upgrade from mysql 5.7 to mariadb 10.3

In the error logs, 404 error response comes from mariadb 10.2 repository, the update cannot continue because the updates were made to 10.2 first to update to 10.3.

The system was not able to ensure the availability of the “MariaDB-client” package: (XID se5akg) “/usr/bin/yum” reported error code “1” when it ended: https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
failure: repodata/repomd.xml from MariaDB102: [Errno 256] No more mirrors to try.
https://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

 

[vacancy]

I edited the mariadb 10.2 repo file according to the following document, but when I start the update process again, the repo file returns to its original state and the repo files cannot be found again.

https://support.cpanel.net/hc/en-us/articles/8172026033687-Updates-failed-due-to-MariaDB-repo-reporting-404-error-

 

[vacancy]

...

 

[cPRex]

@vacancy - that sounds right, and until the fix is 100% applied to all systems, which will happen this week, people will continue to see errors.

If you need to manually perform an update you can run this:

echo '142.4.217.28 yum.mariadb.org' >> /etc/hosts

then run the update, then remove that hosts file entry.

 

[ellaliamop]

After going through 2 days of hell in the last few months, I am sharing my thoughts here:

1) I no longer trust anything to do with WHM's ability to run any type of upgrade or update on MariaDB databases. Within the last few months I've had 2 major crashed database incidents due to:

• a) a more major upgrade from MariaDB 10.5 to 10.6 using WHM update mysql app;
• b) a "minor" update to MariaDB 10.6 using the standard yum update command;

I am not sure what is going on since WHM was purchased by a larger company, but to me it's all bad and after more than 10 years I'm now considering switching to an alternative. I've run WHM DB upgrade and updates for over 10 years without such issues, so having such major problems lately breaks my trust in WHM.



2) Why are there not more built in options to automatically repair DBs that have issues, or in an emergency dump a DB and re-create the DB within the WHM interface? Certainly you could offer far more tools to fix database issues than what you currently offer, which is nearly nothing. How hard would it be to offer an emergency tool that would try to perform a mysql dump and extraction in to a new DB with a "-copy" name added to the DB name. After it ran, if successful, it could display a simple message saying:

• "success-a new DB was created that was tested to have no issues with the name of db-name-copy. To test this with your tutu app be sure to change the DB name in the config file of your site,"

Adding more repair options might at least mitigate the many problems now created when using WHM to upgrade or update MariaDB.

 

[cPRex]

It's important to note the most recent issue was caused by MariaDB changing their repository structure. I did see the feature request that was submitted about repair options, so we'll see if we can get something like that added in the future.

 

[bigadmin]

@HenrikSCH
The correct baseurl for AlmaLinux8 would be Index of /yum/10.6/rhel8-amd64/

The repository /etc/yum.repos.d/MariaDB106.repo file should look like:


[MariaDB106]
name = MariaDB106
baseurl = https://yum.mariadb.org/10.6/rhel8-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1


Replace baseurl correctly in your repository file, and try again after clearing yum cache

Thank you @ServerHealers the solution provided by you worked like charm .

 

[ServerHealers]

Thank you @ServerHealers the solution provided by you worked like charm .

Happy to help always!