• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Run upgrade with option --repair

Zappu

New Pleskian
I had some issues with one of my servers :
OS: CentOS Linux 7.9.2009 (Core)
Product: Plesk Obsidian - Version 18.0.41, last updated on Jan 27, 2022 04:04 AM
so, I run the plesk repair process for everything and at the last stage for the installation itself.
But I got some errors and the log tells me to run the upgrade with the option --repair to rerun failed steps
I have no idea which command to use to run this upgrade. Please see the log below

regards
Thomas

... Applying migrations from: /usr/local/psa/bootstrapper/pp18.0.41-bootstrapper/migrations/ ===> Plesk database scheme upgrade has been completed. ERROR: Upgrade step 2018-03-01-11-34-09_UpdateDnsZones.php failed with code 1 and output: [2022-02-07 10:26:18.027] 446:6200e5ba06810 ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/dnsmng' '--update' 'swinger-reisen24.com' '--without-reverse'] with exit code [127] [2022-02-07 10:26:18.187] 446:6200e5ba06810 ERR [panel] dnsmng failed: sh: /usr/local/psa/admin/bin/dnsmng: No such file or directory: 0: /usr/local/psa/admin/plib/Upgrade/upgrade.php:44 ERROR: Plesk\Upgrade\Exception: dnsmng failed: sh: /usr/local/psa/admin/bin/dnsmng: No such file or directory (upgrade.php:44) 0: /usr/local/psa/admin/plib/Upgrade/upgrade.php:44 SUCCESS: Upgrade step 2019-02-18-14-09-55_InstallEssentialExtensions.php was successfully done. SUCCESS: Upgrade step 2019-04-25-14-46-58_ReportUsage.php was successfully done. SUCCESS: Upgrade step 2020-03-19-17-13-39_UpgradeExtensions.php was successfully done. Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
 
Looks like bind component is not installed. Try to fix it with

# plesk installer add --components bind
 
Ok, that's true, because I do not need it (DNS is handled via Rout53). But thanks, than I know I can ignore this error.
 
You can install bind but not start it. It will eliminate this error at least.
 
Back
Top