MariaDB 10.2 to 10.3 upgrade fails - The preinstall check failed. MariaDB cannot be installed.

sadadkjhasd

• October 19, 2019 16:01

The upgrade from MariaDB 10.2 to 10.3 doesn't work in cPanel. Output: Starting process with log file at /var/cpanel/logs/mysql_upgrade.20191019-133724/unattended_upgrade.log Obtained version information from system. Beginning "MariaDB 10.3" upgrade... Obtained version information from system. Ensuring the "MariaDB103" repository is available and working. checkyum version 22.3 (excludes: bind-chroot ruby) Ensuring that the package "MariaDB-client" with version matching "10.3" is available. Ensuring that the package "MariaDB-common" with version matching "10.3" is available. Ensuring that the package "MariaDB-compat" with version matching "10.3" is available. Ensuring that the package "MariaDB-devel" with version matching "10.3" is available. Ensuring that the package "MariaDB-server" with version matching "10.3" is available. Ensuring that the package "MariaDB-shared" with version matching "10.3" is available. Ensuring that the package "coreutils" is available. The package "coreutils" with version matching "" is already installed. Ensuring that the package "grep" is available. The package "grep" with version matching "" is already installed. Ensuring that the package "perl-DBI" is available. The package "perl-DBI" with version matching "" is already installed. Ensuring that the package "shadow-utils" is available. The package "shadow-utils" with version matching "" is already installed. The "MariaDB103" repository is available and working. Installing pre-known MariaDB dependencies. Installed pre-known MariaDB dependencies. Ensuring MariaDB RPMs for version "10.3". Verifying that the system is in a state where MariaDB packages can be installed. Verifying that the MariaDB packages can be installed by doing a test install. checkyum version 22.3 (excludes: bind-chroot) Loaded plugins: fastestmirror, tsflags, universal-hooks Loading mirror speeds from cached hostfile * EA4: 74.50.120.123 * cpanel-addons-production-feed: 74.50.120.123 * cpanel-plugins: 74.50.120.123 * base: repos.mia.quadranet.com * extras: mirror.facebook.net * updates: mirror.dal.nexril.net Resolving Dependencies --> Running transaction check ---> Package MariaDB-client.x86_64 0:10.2.27-1.el7.centos will be updated ---> Package MariaDB-client.x86_64 0:10.3.18-1.el7.centos will be an update ---> Package MariaDB-common.x86_64 0:10.2.27-1.el7.centos will be updated ---> Package MariaDB-common.x86_64 0:10.3.18-1.el7.centos will be an update ---> Package MariaDB-compat.x86_64 0:10.2.27-1.el7.centos will be updated ---> Package MariaDB-compat.x86_64 0:10.3.18-1.el7.centos will be an update ---> Package MariaDB-devel.x86_64 0:10.2.27-1.el7.centos will be updated ---> Package MariaDB-devel.x86_64 0:10.3.18-1.el7.centos will be an update ---> Package MariaDB-server.x86_64 0:10.2.27-1.el7.centos will be updated ---> Package MariaDB-server.x86_64 0:10.3.18-1.el7.centos will be an update ---> Package MariaDB-shared.x86_64 0:10.2.27-1.el7.centos will be updated ---> Package MariaDB-shared.x86_64 0:10.3.18-1.el7.centos will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: MariaDB-client x86_64 10.3.18-1.el7.centos MariaDB103 11 M MariaDB-common x86_64 10.3.18-1.el7.centos MariaDB103 81 k MariaDB-compat x86_64 10.3.18-1.el7.centos MariaDB103 2.8 M MariaDB-devel x86_64 10.3.18-1.el7.centos MariaDB103 7.1 M MariaDB-server x86_64 10.3.18-1.el7.centos MariaDB103 24 M MariaDB-shared x86_64 10.3.18-1.el7.centos MariaDB103 112 k Transaction Summary ================================================================================ Upgrade 6 Packages Total download size: 46 M Exiting on user command Your transaction was saved, rerun it with: yum load-transaction /root/tmp/yum_save_tx.2019-10-19.13-37.QftUir.yumtx Restarting mysql service. Waiting for "mysql" to restart ""waiting for "mysql" to initialize "finished. Service Status mariadb (/usr/sbin/mysqld) is running as mysql with PID 1193 (systemd+/proc check method). Startup Log Oct 19 13:37:53 host systemd[1]: Starting MariaDB 10.2.27 database server... Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Warning] 'master-info-repository' is MySQL 5.6 compatible option. Not used or needed in MariaDB. Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Warning] 'relay-log-info-repository' is MySQL 5.6 compatible option. Not used or needed in MariaDB. Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Note] /usr/sbin/mysqld (mysqld 10.2.27-MariaDB) starting as process 1193 ... Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Warning] Could not increase number of max_open_files to more than 10000 (request: 10055) Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Warning] Changed limits: max_open_files: 10000 max_connections: 2000 (was 2000) table_cache: 3985 (was 4000) Oct 19 13:37:56 host systemd[1]: Started MariaDB 10.2.27 database server. mysql restarted successfully. The preinstall check failed. MariaDB cannot be installed. at /usr/local/cpanel/Cpanel/Yum/Install.pm line 470. Obtained version information from system. Proceeding with MySQL/MariaDB upgrade despite the following: Critical: In MariaDB" 10.3, the mysqldump client includes logic for the mysql.transaction_registry table. You cannot use the mysqldump client from an earlier MariaDB release on MariaDB 10.3 and later. For more information about how to upgrade to MariaDB 10.3, read the documentation. 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.

• 

  sadadkjhasd

  • October 19, 2019 21:15

  Nevermind on this, I removed a somewhat unrelated repo that was no longer working. I wish it told me this was the issue or at least some kind of helpful error

  0
• 

  cPanelLauren

  • October 21, 2019 17:49

  An unrelated repository caused the Mariadb upgrade to encounter seems to be odd. The errors indicate the following: Critical: In MariaDB" 10.3, the mysqldump client includes logic for the mysql.transaction_registry table. You cannot use the mysqldump client from an earlier MariaDB release on MariaDB 10.3 and later. For more information about how to upgrade to MariaDB 10.3, read the documentation. 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.
  But it does indicate that it was proceeding with the upgrade The specific errors present on your system show up in the MariaDB startup log: Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Warning] 'master-info-repository' is MySQL 5.6 compatible option. Not used or needed in MariaDB. Oct 19 13:37:53 host mysqld[1193]: 2019-10-19 13:37:53 140352008001728 [Warning] 'relay-log-info-repository' is MySQL 5.6 compatible option. Not used or needed in MariaDB.
  

  0

Please sign in to leave a comment.