• 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

Plesk MU #39 failed auto-install

meech

New Pleskian
Hello,

Logged in to Plesk control panel today and have notification that latest MU #39 failed. It appears it failed to resolve some Plesk dependencies? Never had this issue before and haven't made any changes to OS (Ubuntu 14.04). The log file that the notification provided a link to is attached to this post.

Any suggestions on how to proceed would be much appreciated. Thanks!
 

Attachments

  • Plesk - Update Execution failed.txt
    8.4 KB · Views: 1
Hi meech,

such errors/warnings/issues:
Code:
Reading package lists...
Warning: not connected 'multiverse' repository section
Detecting installed product components.
Gathering information about installed license key...
Launching component checkers...
File downloading PSA_12.0.18/examiners/panel_preupgrade_checker.php: 20%..32%..44%..55%..60%..72%..83%..95%..100% was finished.
File downloading PSA_12.0.18/examiners/php_launcher.sh: 100% was finished.
Checking whether the package dependencies are resolved.
E: Version '12.0.18-ubuntu14.04.build1200151014.14' for 'pp12.0.18-bootstrapper' was not found
E: Version '4.5.0.2-ubuntu14.04.build1200151014.14' for 'psa-phpmyadmin' was not found
E: Version '12.0.18-ubuntu14.04.build1200151013.13' for 'psa-updates' was not found
... are mostly only temporary failures, which could as well depend on temporary missing mirrors, or temporary high loads. Please repeat the update procedure after a short coffee break and you will normally see, that the issue is gone. :)

Manual command:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base


If you still experience the same issue another day, an Odin - Team - Member will investigate the issue on their servers/mirrors immediately and will solve the inaccessibility of the files.
 
@UFHH01, Thank you for the quick response! That's good to know. And running the manual command worked like a charm.
Thanks again! :)
 
Back
Top