• 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.

RHEL i386 -> x86_64 UPDATE

S

SergAlex

Guest
Hi there,

Had installed Plesk 7.5.4 (all patches allpied) on rhel_x86_64 cuz swsoft had no x64 release prior v8.0. Now I have a trouble to upgrade from 7.5.4 to 8.0. The issue is that installed packages conflict with new x64 pkgs. :( I've evem tried to upgrade to 8.0 using --override-os-arch switch to upgrate to 8.0_i366/i686, but it didn't work for me - I got an error: "Resolve components ERROR: Can't add to black list product package psa" . Is there ANY way to upgrate to v8 ? Anyone has an expirience? I can do full RPMs uninstall_i386/install_x64, but I'm afraid to lost DB content (s well as other things). Of cource, I did FULL psa backup with psadump utility.

ANY suggestions appreciated!

Thank you, Serg
 
check /tmp/autoinstall3.log and search for backlist. There are lines that tell you what rpms couldn't be resolved. Resolve them yourself and try the updater again.
 
Back
Top