Skip to main content

Error Updating cPanel to Version 68

sbhooley
I am on version cPanel & WHM 64.0 (build 42), trying to update to 68.0.26 When I try to update through WHM, I get the following error: [2018-01-18 18:41:34 +0000] cpanel-perl-524-Net-FTPSSL-0.35-1.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Perl-Strip-1.1-1.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Devel-CheckLib-1.09-1.cp1162.x86_64.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Net-FastCGI-0.14-2.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Acme-Damn-0.08-1.cp1162.x86_64.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Crypt-Format-0.07-1.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Selenium-Remote-Driver-1.12-1.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-TestRail-API-0.041-1.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Crypt-OpenSSL-DSA-0.19-1.cp1162.x86_64.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-Email-Simple-2.213-1.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] cpanel-perl-524-cPanel-TaskQueue-0.800-7.cp1162.noarch.rpm already downloaded [2018-01-18 18:41:34 +0000] All files Staged [2018-01-18 18:41:34 +0000] Testing if the newly downloaded RPMS can be installed without conflict [2018-01-18 18:41:34 +0000] Testing RPM transaction [2018-01-18 18:41:35 +0000] error: Failed dependencies: [2018-01-18 18:41:35 +0000] MySQL-server is needed by cpanel-perl-524-munin-2.0.30-1.cp1162.x86_64 [2018-01-18 18:41:35 +0000] W Exit Code: 180 [2018-01-18 18:41:35 +0000] ***** FATAL: Test install failed: error: Failed dependencies: [2018-01-18 18:41:35 +0000] MySQL-server is needed by cpanel-perl-524-munin-2.0.30-1.cp1162.x86_64 [2018-01-18 18:41:35 +0000] The Administrator will be notified to review this output when this script completes [2018-01-18 18:41:35 +0000] ***** FATAL: Error testing if the RPMs will install: Test install failed: error: Failed dependencies: [2018-01-18 18:41:35 +0000] MySQL-server is needed by cpanel-perl-524-munin-2.0.30-1.cp1162.x86_64 [2018-01-18 18:41:35 +0000] see RPM Installation Failures - cPanel Knowledge Base - cPanel Documentation for more information [2018-01-18 18:41:35 +0000] The Administrator will be notified to review this output when this script completes => Log closed Thu Jan 18 18:41:35 2018 [2018-01-18 18:41:35 +0000] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1516300832.log` failed, exited with code 1 (signal = 0) => Log closed Thu Jan 18 18:41:35 2018
I looked at mysql and everything is functioning. Sites are functioning. The only thing I can think of is that a server admin that assists me installed Percona 5.7 -- which to my understanding now, can cause problems? This is a production server, so I am not sure how to make the upgrade happen with no downtime. Please assist.

Comments

7 comments

Date Votes
  • cPanelMichael
    [2018-01-18 18:41:35 +0000] MySQL-server is needed by cpanel-perl-524-munin-2.0.30-1.cp1162.x86_64

    The only thing I can think of is that a server admin that assists me installed Percona 5.7 -- which to my understanding now, can cause problems? This is a production server, so I am not sure how to make the upgrade happen with no downtime.

    Hello, It looks like the Munin RPM update is failing due to the use of Percona. You could try setting the Munin RPM to unmanaged to temporarily workaround this issue until you are able to revert from Percona back to MySQL or MariaDB: /scripts/update_local_rpm_versions --edit target_settings.munin unmanaged
    Let us know if that helps. Thank you.
    0
  • sbhooley
    And if I want to "manage" it again, then I would do " /scripts/update_local_rpm_versions --edit target_settings.munin managed"? Also is there any danger in temporarily workaround this, and proceeding with the upgrade?
    0
  • sbhooley
    Hello, It looks like the Munin RPM update is failing due to the use of Percona. You could try setting the Munin RPM to unmanaged to temporarily workaround this issue until you are able to revert from Percona back to MySQL or MariaDB: /scripts/update_local_rpm_versions --edit target_settings.munin unmanaged
    Let us know if that helps. Thank you.

    And if I want to "manage" it again, then I would do " /scripts/update_local_rpm_versions --edit target_settings.munin managed"? Also is there any danger in temporarily workaround this, and proceeding with the upgrade?
    0
  • twhiting9275
    The workaround shouldn't affect your server at all, except to say that it will allow the server to update to 68 It's odd that the packagers didn't take into account that others require other DB's in this case . cPanel should be the ones supplying these specific RPMs
    0
  • cPanelMichael
    Also is there any danger in temporarily workaround this, and proceeding with the upgrade?

    It might prevent you from reinstalling the Munin plugin. Generally, the better approach is to have your system administrator revert the Percona installation and use a supported database server (e.g. MySQL or MariaDB). Thank you.
    0
  • cPanelMichael
    Hello, To update, this is actually a defect where Munin is requiring the incorrect package name for "MySQL-server". Internal case CPANEL-17756 addresses this issue in cPanel version 70 by ensuring it instead depends on the presence of mysqld. It doesn't look like we will backport this change to cPanel version 68 (it only affects unsupported database server installations such as Percona on cPanel 68). Thus, setting the Munin RPM target to "unmanaged" as mentioned earlier in this thread will act as a workaround to allow the cPanel update to proceed. Thank you.
    0
  • sbhooley
    I am not sure how to close this, but your suggestions worked perfectly. I am on version 68, and things are working more smoothly now. Thanks!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post