Known Issues Status Page - cPanel version 84

[jacobcolton]

Looks like they have now released it: Index of /10.3/centos7-amd64/rpms/

 

[cPanelLauren]

Looks like they have now released it: Index of /10.3/centos7-amd64/rpms/

I just came here to update with that information. The affected versions are removed and the fix version is available. Please let us know if you experience any further issues but as far as we understand this issue is resolved.

 

[t_lababidi]

hi
we need to know if it's now safe or not ?
and i have servers with :
10.2.28 what i must do just update or i need to downgrade to 10.2.27 then update??

 

[cPanelLauren]

hi
we need to know if it's now safe or not ?
and i have servers with :
10.2.28 what i must do just update or i need to downgrade to 10.2.27 then update??

Hello,

As indicated in my previous response MariaDB has updated their packages with the resolution for this issue. The affected versions were removed from their repository and you should be able to update without experiencing this issue at this time.

 

[chirpy]

I've upgraded ours to the new latest MariaDB v10.1 and v10.3 without issues.

 

[WhiteDog]

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

And... why exactly? Because they have one bad release in 5+ years?
I'll take <random open source database> over Oracle anyday, even if it's 5% slower.
If you really want to go back to MySQL, just dump your data, install MySQL and import all your tables again?

I'd rather see support for MariaDB 10.4!

 

[emaskui]

@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.

thnks
helpfull for me.

 

[t_lababidi]

last update works with me without any problems on 8 Servers
Now All Servers work with MariaDB 10.2.29

thanks

 

[popeye]

Does this update upgrade the database ? because it thought that was manully done. Also i have had operating system package updates to never update. So is it safe to turn this back on now.

 

[cPanelLauren]

Does this update upgrade the database ? because it thought that was manully done. Also i have had operating system package updates to never update. So is it safe to turn this back on now.

Minor version updates are done automatically when yum update is run. Major upgrades are not done this way. It should be safe to set system packages to automatically update once more as well.

 

[popeye]

Minor version updates are done automatically when yum update is run. Major upgrades are not done this way. It should be safe to set system packages to automatically update once more as well.

have had operating system package updates to never update. So is it safe to turn this back on now.

 

[cPanelLauren]

have had operating system package updates to never update. So is it safe to turn this back on now.

It should be safe to set system packages to automatically update once more as well.

As I noted it should be.

 

[popeye]

As I noted it should be.

Can i ask how would i check if it's updated once i set them to update again ?

 

[jcn50]

And... why exactly? Because they have one bad release in 5+ years?

More bec MySQL 8 is coming up and we need a bridge between the two engines. It is already the case with CloudLinux.

If you really want to go back to MySQL, just dump your data, install MySQL and import all your tables again?

This is not workable due to the user/pass changes.

 

[jackp89]

Hello,

As indicated in my previous response MariaDB has updated their packages with the resolution for this issue. The affected versions were removed from their repository and you should be able to update without experiencing this issue at this time.

thanks sir it was so helpful for me.

 

[payamprivate]

@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.

Thanks a lot, it was so much helpful