• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

migration from cpanel to plesk failure

shall

Regular Pleskian
Trying to migrate a half dozen domains from a cPanel server to my Plesk 8.1.1 server.

Plesk Migration Manager is reporting:

=============================================
ERROR: PleskFatalException

Unable execute MigrationWait::make(): Unable to create bar: assigned values not like "minimal value <= current value <= maximal value (!= 0)

0: /usr/local/psa/admin/plib/common_func.php3:151
psaerror(string 'Unable execute MigrationWait::make(): Unable to create bar: assigned values not like "minimal value <= current value <= maximal value (!= 0)')
1: /usr/local/psa/admin/plib/PMM/MigrationWait.php:282
MigrationWait->make()
2: /usr/local/psa/admin/htdocs/server/PMM/main.php:25

=============================================

And the migration process has now run for over 76 hours on both the Plesk AND the (LIVE!) cPanel system.

How do I completely kill the process on the cPanel box and prevent it from starting up again?

Has anyone found a fix for this funky MigrationWait thing?

Thanks!
 
I dumped the PMM temp folders on both servers, then logged into mysql and emptied the psa.PMM table, and am restarting the server - hopefully this will resolve any trailing problems with the failed PMM migration.
 
Back
Top