• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Resolved Unable to upgrade to 17.8.10 (testing)

Sergio Manzi

Regular Pleskian
So, I decided to give 17.8.10 a try but have stumbled on an issue I don't have the first idea how to solve:

To prepare for the upgrade I "nuked" my /root/parallels directory (I think this is OK, isn't it?), then I issued the "plesk installer upgrade plesk testing" command from my ssh console.

The upgrade started in an apparently uneventful way, but then I got this:
Code:
...
http://autoinstall.plesk.com/PSA_17.8.10/extras-rpm-CentOS-7-x86_64/repodata/f0281ac0f12b41fd911138d317ebc0497ba54c2aad645b86afed5580e90d24dd-filelists.sqlite.bz2: [Errno 14] HTTP Error 504 - Gateway Timeout
Trying other mirror.
NoMoreMirrorsRepoError: failure: repodata/f0281ac0f12b41fd911138d317ebc0497ba54c2aad645b86afed5580e90d24dd-filelists.sqlite.bz2 from PLESK_17_8_10-extras: [Errno 256] No more mirrors to try.
http://autoinstall.plesk.com/PSA_17.8.10/extras-rpm-CentOS-7-x86_64/repodata/f0281ac0f12b41fd911138d317ebc0497ba54c2aad645b86afed5580e90d24dd-filelists.sqlite.bz2: [Errno 14] HTTP Error 504 - Gateway Timeout

ERROR: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please contact product technical support.
exit status 1

If I'm getting the above right, it is a problem downloading from autoinstall.plesk.com, isn't it?

Notwithstanding the the warning message about the software possibly being possibly inoperable everything seemed to be OK, but to not risk some hidden issue I restored my VPS from the snapshot I took just before trying the upgrade.

Everything seems to work now (SNAFU as they say...), but before giving it a second shot I'd like to hear from someone "in-the-know"...

CentOS is 7.4.1708, Kernel 3.10.0-693
Current Plesk is 17.5.3#40

TIA,

Sergio
 
Yes, there were some problems with CDN, we are working on it. Thank you.
 
Back
Top