Switch to MySQL WHM
I have recently purchased a VPS, however the same was with old version of cPanel. I have run an upgrade of the cPanel to the latest version. However after the upgrade I am unable to switch from MariaDB to MySQL service to 5.6:
Imgur: The most awesome images on the Internet
When I try to upgrade the MySQL service to 5.5 I am able to see next message in the WHM browser console:
[2016-12-23 13:41:40 +0000] file /usr/share/man/man1/mysql_config.1.gz from install of MySQL55-devel-5.5.52-1.cp1156.x86_64 conflicts with file from package MariaDB-devel-5.5.53-1.el6.x86_64 [2016-12-23 13:41:40 +0000] W Error Code: 8 [2016-12-23 13:41:40 +0000] Hooks system enabled. [2016-12-23 13:41:40 +0000] Checking for and running RPM::Versions 'post' hooks for any RPMs about to be installed [2016-12-23 13:41:40 +0000] All required 'post' hooks have been run [2016-12-23 13:41:40 +0000] Restoring service monitoring. Restarting mysql service. Waiting for "mysql" to restart ""waiting for "mysql" to initialize "finished.
Any help will be greatly appreciated, thank you guys! :)
-
Hello, The MariaDB/MySQL Upgrade feature does not support downgrades of database engine versions. We strongly recommend that you do not attempt to downgrade MySQL or MariaDB. This is documented at: MySQL or MariaDB Upgrade - Documentation - cPanel Documentation Is there a particular reason you need MySQL 5.5 instead of MariaDB? Thank you. 0 -
Hello Michael, Thank you for the documentation link. The switch to MySQL 5.6 is currently blocked and I am unable to manage deploying MySQL 5.6 RPM and replace it with the current 5.5 RPM. Please check the attached file. Actually, I want to switch to MySQL 5.6 and not 5.5, however as you can see from the screenshot I am unable to choose the MySQL 5.6. If you would like me to attach a certain log from: /var/cpanel/logs/mysql_upgrade.20161223-134130 Or other directory, please confirm and I will provide all of the necessary information here! I read regularly this forum and I see that Michael always help an issue to get resolved! I am really happy that you have write in my thread Michael, thank you :) 0 -
I guess the question would be why... Why would you want to downgrade from MariaDB to MySQL? Maria handles things a ton better than MySQL ever did. 0 -
Hello twhiting9275, Actually this a requirement of the developer, but this also comes convenient for me as I have never managed a MariaDB SQL service. For additional information, if I try to upgrade to MariaDB 10.1, the WHM console have next output: [2016-12-24 02:38:49 +0000] file /usr/share/man/man1/mysql_config.1.gz from install of MySQL55-devel-5.5.52-1.cp1156.x86_64 conflicts with file from package MariaDB-devel-5.5.53-1.el6.x86_64 [2016-12-24 02:38:49 +0000] W Error Code: 8 [2016-12-24 02:38:49 +0000] Hooks system enabled. [2016-12-24 02:38:49 +0000] Checking for and running RPM::Versions 'post' hooks for any RPMs about to be installed [2016-12-24 02:38:49 +0000] All required 'post' hooks have been run [2016-12-24 02:38:49 +0000] Restoring service monitoring. Restarting mysql service. Waiting for "mysql" to restart ""waiting for "mysql" to initialize "finished. Service Status mysql (/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/node01.differenthosting.com.err --open-files-limit=16384 --pid-file=/var/lib/mysql/node01.differenthosting.com.pid) is running as mysql with PID 30365 (pidfile check method). Startup Log Starting MySQL.161224 02:38:57 mysqld_safe Logging to '/var/lib/mysql/node01.differenthosting.com.err'. . SUCCESS! Log Messages 161224 2:38:58 [Note] /usr/sbin/mysqld: ready for connections. 161224 02:38:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 161224 02:38:56 mysqld_safe mysqld from pid file /var/lib/mysql/node01.differenthosting.com.pid ended 161224 2:38:56 [Note] /usr/sbin/mysqld: Shutdown complete 161224 2:38:55 [Note] /usr/sbin/mysqld: Normal shutdown 161223 13:41:51 [Note] /usr/sbin/mysqld: ready for connections. 161223 13:41:50 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 161223 13:41:49 mysqld_safe mysqld from pid file /var/lib/mysql/node01.differenthosting.com.pid ended 161223 13:41:49 [Note] /usr/sbin/mysqld: Shutdown complete 161223 13:41:46 [Note] /usr/sbin/mysqld: Normal shutdown 161223 13:23:50 [Note] /usr/sbin/mysqld: ready for connections. 161223 13:23:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 161223 13:23:48 mysqld_safe mysqld from pid file /var/lib/mysql/node01.differenthosting.com.pid ended 161223 13:23:48 [Note] /usr/sbin/mysqld: Shutdown complete 161223 13:23:46 [Note] /usr/sbin/mysqld: Normal shutdown mysql restarted successfully. We expected to upgrade to 5.6; however, the system is currently on version 5.5. at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 827.
Thank you too!0 -
Hello @KrasniyRus, Could you open a support ticket using the link in my signature so we can take a closer look at the packages installed on your system? Please post the ticket number here and we will update this thread with the outcome. Thank you. 0 -
Hello Michael, I have just submitted a ticket, thank you! The ticket ID is 8111253 We will be waiting for further information, thank you in advance. 0 -
Hello all, First of all, I would like to express my gratitude to Michael and Ricardo, which assist greatly in resolving this issue! Below, I will explain how the issue was resolved. First it occur that the MySQL 5.6 package was unavailable. This was resolved easy by executing the next command via SSH as root user: /usr/local/cpanel/scripts/update_local_rpm_versions --del target_settings.MySQL56 Afterwards, I was able to choose MySQL 5.6, however on the upgrade console in WHM I was seeing the next error message: mysql restarted successfully. We expected to upgrade to 5.6; however, the system is currently on version 5.5. at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 827. It occur that there was installed custom RMP's from the company where the VPS service is hired: MariaDB-server-5.5.53-1.el6.x86_64 MariaDB-devel-5.5.53-1.el6.x86_64 MariaDB-client-5.5.53-1.el6.x86_64 MariaDB-common-5.5.53-1.el6.x86_64 MariaDB-compat-5.5.53-1.el6.x86_64 I have removed all of the RMP's above with the yum remove command. Then all I have to execute is another built-in script of the great cPanel service: /usr/local/cpanel/scripts/check_cpanel_rpms --fix Afterwards all run smoothly as it was intended. Once again thank to all of the participants in this case! 0 -
I'm happy to see the issue was resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
8 comments