mysql 5.7 to mariadb 10.2 failed
Hello
The whm upgrade schipt fails, and I can't see why...
Starting process with log file at /var/cpanel/logs/mysql_upgrade.20200414-104208/unattended_upgrade.log
Obtained version information from system.
Beginning "MariaDB 10.2" upgrade...
Obtained version information from system.
Ensuring the "MariaDB102" repository is available and working.
checkyum version 22.3 (excludes: bind-chroot ruby)
Restarting mysql service.
Waiting for "mysql" to restart ""waiting for "mysql" to initialize "finished.
Service Status
mysqld (/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid) is running as mysql with PID 73696 (systemd+/proc check method).
Startup Log
Apr 14 10:42:12 v1.rulmentionline.ro systemd[1]: Stopped MySQL Server.
Apr 14 10:42:12 v1.rulmentionline.ro systemd[1]: Starting MySQL Server...
Apr 14 10:42:13 v1.rulmentionline.ro systemd[1]: Started MySQL Server.
Log Messages
2020-04-14T10:42:13.400679Z 0 [Note] /usr/sbin/mysqld: ready for connections.
2020-04-14T10:42:12.406608Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
mysql restarted successfully.
Multiple versions of the coreutils are installed: package MariaDB-client is not installed
package MariaDB-common is not installed
package MariaDB-compat is not installed
package MariaDB-devel is not installed
package MariaDB-server is not installed
package MariaDB-shared is not installed
coreutils 8.22-23.el7
coreutils 8.22-24.el7
grep 2.20-3.el7
perl-DBI 1.627-4.el7
shadow-utils 4.1.5.1-25.el7_6.1
shadow-utils 4.6-5.el7 at /usr/local/cpanel/Cpanel/SysPkgs/YUM.pm line 594.
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Critical: MariaDB enables "strict mode" by default as of version 10.2. Strict mode controls how MariaDB and MySQL handle invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MariaDB are compatible before upgrading. More information about strict mode is available here. Normal: When you upgrade from MySQL" to MariaDB 10.2 or later, the mysql_upgrade utility may emit several database table-related errors. The discrepancies in the tables between MySQL and MariaDB versions produce the errors; however, the upgrade process will resolve these issues.
Normal: MariaDB does
notutilize the sys schema. If you upgrade from MySQL 5.7 to MariaDB, you
must manually remove the sys database, because it can cause unnecessary errors during certain check table calls.-
The only errors are noted here: Critical: MariaDB enables "strict mode" by default as of version 10.2. Strict mode controls how MariaDB and MySQL handle invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MariaDB are compatible before upgrading. More information about strict mode is available here. Normal: When you upgrade from MySQL" to MariaDB 10.2 or later, the mysql_upgrade utility may emit several database table-related errors. The discrepancies in the tables between MySQL and MariaDB versions produce the errors; however, the upgrade process will resolve these issues. Normal: MariaDB does notutilize the sys schema. If you upgrade from MySQL 5.7 to MariaDB, you must manually remove the sys database, because it can cause unnecessary errors during certain check table calls.
But what came after these?0 -
nothing, that's why I don't understand it either. I even dropped the sys database 0 -
Which version of cPanel are you running? When removing the sysschema tables does the update complete? 0 -
v86.0.18 No, it made no difference. I also checked the mysql upgrade script log files, but there no other info in there. I think the data in the webpage is exactly the same as in the logs 0 -
Can you please open a ticket using the link in my signature? I feel like changes to MySQL are too sensitive in nature to provide advice over the forums. Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks! 0 -
Your Support Ticket ID is: 93472650 0 -
Thanks! I've updated the ticket with the thread information here and I'm following it. I'll note any information here when there are any updates available. 0 -
Following the ticket: "The upgrade process completed successfully." For future readers: the problem was caused by duplicate packages installed on the system: coreutils-8.22-24.el7.x86_64 coreutils-8.22-23.el7.x86_64 And was fixed with package-cleanup --cleandupes If we look at the logs, the duplicate package was indeed listed in the log, but not as the cause of the problem, just as an info Thank you 0
Please sign in to leave a comment.
Comments
8 comments