Wondering how to resolve Upgrade to Plesk Obsidian fails? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team help a customer  deal with this Plesk error.

How to resolve Upgrade to Plesk Obsidian fails?

The following error appear at the log when Upgrading to Plesk Obsidian:

Error: Cannot open file /var/cache/yum/x86_64/6/PLESK_17_PHP70/packages/plesk-php70-sodium-2.0.13-0centos.6.181207.1259.x86_64.rpm: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/6/PLESK_17_PHP70/packages/plesk-php70-sodium-2.0.13-0centos.6.181207.1259.x86_64.rpm'
...
TypeError: an integer is required
error: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x6324e18>> failed, aborting!
processTransaction event: 10 (Downloading Packages)
processTransaction event: 11 (unknown)

Issue usually occurs due to missing files at the Yum Cache folder located at /var/cache/yum/x86_64.

Today, let us see the steps followed by our Support Techs to resolve it.

1. Firstly, connect to the server via SSH
2. Then, check for duplicate packages with the command below:

   package-cleanup --dupes

   Note: package-cleanup utility is provided by yum-utils package. If the package is not installed use yum install yum-utilsto install it.

3. Next, make sure that important packages will not be removed and then remove duplicates using the following method:

• package-cleanup --cleandupes

  4. Then, re-check duplicates:

  package-cleanup --dupes

  5. If any package still reported, remove it manually

  rpm -e --nodeps --noscripts <package_name>

  6. Finally, complete the upgrade:

plesk installer update

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw steps followed by our Support Engineers to resolve Obsidian upgrade failure in Plesk.