• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Update to 18.0.27 failed

moswak

Regular Pleskian
I received the message from 3 centos 6 servers tonight that the upgrade to 18.0.27 failed.

with other centos6 servers the update went through without problems

error was:
Error: Cannot open file /var/cache/yum/x86_64/6/base/packages/perl-Error-0.17015-4.el6.noarch.rpm: [Errno 2] No such file or directory: '/ var / cache / yum / x86_64 / 6 / base / packages / perl-Error-0.17015-4.el6.noarch.rpm '
TypeError: an integer is required
error: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x57952d8 >> failed, aborting!

I installed the perl error package and completed the unfinished removal of the older plesk packages with yum-complete-transaction.

Plesk is now displayed as 18.0.27 but without installationdate and everything seems to be working but the upgrade to 18.0.27 is still proposed. If i open the web installer, 18.0.27 is also displayed.

should I do anything else or can I upgrade to 18.0.27 again?
 
Hi IgorG,

first you wrote "try to fix with # plesk repair installation"
your post to support.plesk.com is not my problem. when i run"package-cleanup --dupes" there are no duplicates

i run plesk repair installation
**** Product repair completed successfully.

I will wait 24 hours and then see if "An update to Plesk Obsidian 18.0.27 is available." is still displayed after the login in plesk.
 
Hi IgorG,

# plesk repair installation
or
# plesk installer update --repatch

doesnt solve the issue
"An update to Plesk Obsidian 18.0.27 is available." is still displayed after the login in plesk

since everything seems to be running normally, maybe just wait until the next update?
 
You can also try to fix it with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
 
# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

Result: "You already have the latest version of product(s) and all the selected components installed. Installation will not continue."

nothing has changed in the display

screen.jpg

I just wait until the next update is due and will see what happens next
 
I'm having the exact same problem but with upgrading to 18.0.28 that auto-installed overnight.
Same file:
Error: Cannot open file /var/cache/yum/x86_64/7/base/packages/perl-Error-0.17020-2.el7.noarch.rpm:

@IgorG you might want to look into a solution so others don't have this issue that has been around for a while. Might it flare up again with 18.0.29?

The install had to repair itself after it failed and looks ok now, but the panel is saying the update to 18.0.28 is still available...
 
Back
Top