Known Issues Status Page - cPanel version 84

[JIKOmetrix]

Running the downgrade allow the DB services to come back online for me.

yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel

 

[Dimiany]

We have lost access to our WHM so I cannot open any tickets, any advice? please ASAP

 

[cPAusaf]

We have lost access to our WHM so I cannot open any tickets, any advice? please ASAP

Are you able to access the server via SSH? You can get the cPanel support ID with this command:

/usr/local/cpanel/cpanel -S

SSH access will be needed to investigate the issue. If you are unable to access SSH, then we recommend reaching out to your provider to see what issues may be occurring.

 

[GOT]

It will update again. You should exclude it in yum.conf for now

 

[techAMIGO]

Hi All,

yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel

it worked in some of my clients servers...

 

[slabby]

It will update again. You should exclude it in yum.conf for now

What is the best way to exclude it in the yum.conf?

 

[cPanelMichael]

Hello Everyone,

MariaDB has fixed the issue in the following unpublished versions:

10.1.43 [ 23703 ]
10.2.29 [ 23911 ]
10.3.20 [ 23909 ]
10.4.10 [ 23907 ]

We don't have a specific time frame to share on the publication of the updated RPMs, but we'll update this thread as soon as they are published. We strongly recommend avoiding workarounds that take the extra step of disabling automatic updates unless you or your system administration team has a process in-place to monitor the issue and enable automatic updates again once the issue is solved.

Thank you.

 

[plague]

@GOT the problem appears on databases using FULLTEXT KEY indexes. Moving/removing those databases from the data directory enables the server to startup.
You can find this databases looking for file names starting with "FTS*" inside the database directory:

user_database/FTS_000000000005cf3b_CONFIG.ibd

 

[cPanelLauren]

Update: We've found that MariaDB has removed all affected versions from their repository - At this time the instructions to prevent update using yum-versionlock are no longer necessary.

If you did update and were affected, you would still need to downgrade until the issue is resolved and a new build is pushed out by MariaDB but you will not be upgraded to an affected version.

 

[quietFinn]

Update: We've found that MariaDB has removed all affected versions from their repository - At this time the instructions to prevent update using yum-versionlock are no longer necessary.

If you did update and were affected, you would still need to downgrade until the issue is resolved and a new build is pushed out by MariaDB but you will not be upgraded to an affected version.

Had to run yum clean all, then it worked.

 

[iero]

I was so angry in the morning, we have a couple of servers down this morning, we are [Moderator Note: Removed Link To Third-Party URL] and we usually have latest version of whm and litespeed, I had no idea what was wrong until i decided to open a ticket, then i found the issue and we finally resolved downgrading, but it was like 2 hours trying ourselves with our customers calling, not good at all

 

[kennysamuerto]

Hello,

In my case, one of my clients was affected by this problem.

The solution in our case, to the little information 24 hours ago when it happened, was to restore a backup of the databases, even though we tried all kinds of alternatives to solve it.

At that point, we decided to remove the databases, and replace them with a backup a few hours earlier.

Therefore, in our case, the bug version is maintained, but everything works correctly after recovering the databases from a backup.

So... What can be expected from the behavior of this server? Should it work well? Should we do downgrade even though everything works correctly?

Thanks

 

[webtipster]

Praying they have a fix for this soon... Downgrading only solved the problem for some of my servers, might have to roll back more on others. cPanel team please post an update when you know more. Thanks!

 

[porkchopzz4]

Update: We've found that MariaDB has removed all affected versions from their repository - At this time the instructions to prevent update using yum-versionlock are no longer necessary.

If you did update and were affected, you would still need to downgrade until the issue is resolved and a new build is pushed out by MariaDB but you will not be upgraded to an affected version.

Is this a guarantee? I'm scared to turn automatic updates back on and go through this again. I was down 16 hours until support found out what was going on.

 

[Leonidas Savvides]

yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel

Note: The above workaround is intended as a temporary workaround only. If your cPanel & WHM server is configured to automatically update your system packages, the issue will re-occur each time the MariaDB RPMs are upgraded until MariaDB publishes a fix for case MDEV-19073.

from this quote
"
If your cPanel & WHM server is configured to automatically update your system packages, the issue will re-occur each time the MariaDB RPMs are upgraded until MariaDB publishes a fix for case MDEV-19073.
"

how to disable server updates from WHM??? is it here:// ??

• Home »
• Server Configuration »
• Update Preferences

if yes choose MANUAL UPDATES ONLY
From
Daily Updates

1. Automatic
2. Manual Updates Only
3. Never Update

????

Or From OS updates

Operating System Package Updates

1. Automatic
2. Manual Updates Only
3. Never Update

disable - choose second option???
this only??

So FINALLY
Set first

Operating System Package Updates

To
Manual Updates Only
And after ssh run downgrade command...?

• YES CORRECT
• No

 

[Leonidas Savvides]

I Set first

Operating System Package Updates

To
Manual Updates Only
And after went ssh run the downgrade command...?

I can Not enter SSH I think forgot where is a public key and in what machine (PC)--- I have over 3 years to login since

$ ssh [email protected]

[email protected]: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

Is it OK - give the command from WHM/Terminal in the browser as shown below????? What other solutions exist???





I mean this cmd here ^^^ >>>

yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel

 

[Leonidas Savvides]

yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel

I ran this on Browser/WHM/Terminal and now all working MariaDB....!!

 

[plague]

Hello,

In my case, one of my clients was affected by this problem.

The solution in our case, to the little information 24 hours ago when it happened, was to restore a backup of the databases, even though we tried all kinds of alternatives to solve it.

At that point, we decided to remove the databases, and replace them with a backup a few hours earlier.

Therefore, in our case, the bug version is maintained, but everything works correctly after recovering the databases from a backup.

So... What can be expected from the behavior of this server? Should it work well? Should we do downgrade even though everything works correctly?

Thanks

@kennysamuerto downgrade your MariaDB anyway. After the restore if you restart MariaDB, or run a mysqlcheck on databases that use FULLTEXT indexes, it will probably crash again.
I tried the restore before downgrading the installation, and the server crashed in the first restart, after restoring one of those specific databases.

 

[cPanelLauren]

from this quote
"
If your cPanel & WHM server is configured to automatically update your system packages, the issue will re-occur each time the MariaDB RPMs are upgraded until MariaDB publishes a fix for case MDEV-19073.
"

how to disable server updates from WHM??? is it here:// ??

Again, I'd like to point out the following:

Update: We've found that MariaDB has removed all affected versions from their repository - At this time the instructions to prevent update using yum-versionlock are no longer necessary.

If you did update and were affected, you would still need to downgrade until the issue is resolved and a new build is pushed out by MariaDB but you will not be upgraded to an affected version.

Furthermore, MariaDB have fixed the affected packages and we're just waiting on them to be pushed - we will update here when that is complete, we're hoping for today.

 

[jcn50]

Guys,

We need a way to switch from MariaDB back to MySQL (like it is possible with CloudLinux), please upvote this request here:

https://features.cpanel.net/topic/revert-to-mysql-from-mariadb-migration