• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Plesk migration = headaches!

H

HHawk

Regular Pleskian
Been trying to migrate several servers now, only one worked so far, the other one is a pain in the ....
I already spend hours on this and the boss is getting annoyed with Plesk at the moment. And he is even considering to make a permanent move to something else.


The debug.log is in the next post because of the stupid forum limit. Sigh.


The error message in the Plesk migration tool is also not very useful:

Failed to convert clients and subscriptions
Cause: not well-formed (invalid token): line 92, column 33
That is a critical error, migration was stopped.
Click to expand...

I was fed up with that message, so I just deleted all user accounts with wrong passwords. Ofcourse it didn't help at all.

When I click the details text (on migration page) it's swamped with the following message:

Failed to check license limits on target Plesk server
Exception: 'NoneType' object has no attribute 'iter_all_subscriptions'
Click to expand...

After several hours, I am pretty much fed up with everything.

Sidenote: nowadays it seems more and more issues with Plesk. For example my own server, which runs Onyx (I regret upgrading) doesn't work correctly anymore after a reboot and only runs when running Plesk repair utility.... Sigh. Anyways, that's just my personal server (also considering moving to a different CP for that matter). Also recent updates makes our customer angry because the self-signed certificates don't work anymore with Outlook, iPhone, MacOS, etc... We already lost a few customers because of that.

Anyways, I hope someone can help with the above, but I doubt it. The message isn't very useful to do anything. Maybe just migrate everything over to a different CP may be a good solution as this isn't getting me anywhere at all, only frustrated and wasting my precious time for hours now...

And yes, I ran plesk repair command several times, no issues.....


[Update: added information]

Both servers are running Plesk 12.5.3 latest versions.
One Plesk server is running on CentOS 5.11 (old server) with all the latest updates.
The other Plesk server is running on CentOS 6.8 (new server) also with all the latest updates.
 
Last edited:
Code: 
+|2017-03-02_18:17:59,964|D|MT|hosting_check.utils.http_client|||Unable to import NSS. We will use OpenSSL
+|2017-03-02_18:17:59,986|I|MT|core.migrator|||Initialize Plesk Migrator
+|2017-03-02_18:17:59,987|D|MT|core.utils.panel_detector.source|||Source panel (specified in configuration file): plesk
+|2017-03-02_18:17:59,988|D|MT|core.runners.base|||Execute command on the local server: plesk db "SELECT name FROM Modules WHERE name = 'plesk-multi-server'"
+|2017-03-02_18:17:59,996|D|MT|core.runners.base|||Command execution results:
=|2017-03-02_18:17:59,996|D|MT|core.runners.base|||stdout:
=|2017-03-02_18:17:59,996|D|MT|core.runners.base|||stderr:
=|2017-03-02_18:17:59,996|D|MT|core.runners.base|||exit code: 0
+|2017-03-02_18:17:59,996|D|MT|core.utils.panel_detector.target|||Target panel (automatically detected): plesk
+|2017-03-02_18:18:00,009|I|MT|plesk.connections.target_connections|||Target Plesk host: YY.YY.YY.YY
+|2017-03-02_18:18:00,010|I|MT|plesk.source.plesk.connections.source_connections|||Source Plesk 'source' host: XX.XX.XX.XX
+|2017-03-02_18:18:00,010|I|MT|plesk.connections.target_connections|||Target Plesk host: YY.YY.YY.YY
+|2017-03-02_18:18:03,307|D|MT|hosting_check.utils.http_client|||Unable to import NSS. We will use OpenSSL
+|2017-03-02_18:18:03,329|I|MT|core.migrator|||Initialize Plesk Migrator
+|2017-03-02_18:18:03,330|D|MT|core.utils.panel_detector.source|||Source panel (specified in configuration file): plesk
+|2017-03-02_18:18:03,331|D|MT|core.runners.base|||Execute command on the local server: plesk db "SELECT name FROM Modules WHERE name = 'plesk-multi-server'"
+|2017-03-02_18:18:03,340|D|MT|core.runners.base|||Command execution results:
=|2017-03-02_18:18:03,340|D|MT|core.runners.base|||stdout:
=|2017-03-02_18:18:03,340|D|MT|core.runners.base|||stderr:
=|2017-03-02_18:18:03,340|D|MT|core.runners.base|||exit code: 0
+|2017-03-02_18:18:03,340|D|MT|core.utils.panel_detector.target|||Target panel (automatically detected): plesk
+|2017-03-02_18:18:03,352|I|MT|plesk.connections.target_connections|||Target Plesk host: YY.YY.YY.YY
+|2017-03-02_18:18:03,353|I|MT|plesk.source.plesk.connections.source_connections|||Source Plesk 'source' host: XX.XX.XX.XX
+|2017-03-02_18:18:03,353|I|MT|plesk.connections.target_connections|||Target Plesk host: YY.YY.YY.YY
+|2017-03-02_18:18:11,770|D|MT|hosting_check.utils.http_client|||Unable to import NSS. We will use OpenSSL
+|2017-03-02_18:18:11,792|I|MT|core.migrator|||Initialize Plesk Migrator
+|2017-03-02_18:18:11,793|D|MT|core.utils.panel_detector.source|||Source panel (specified in configuration file): plesk
+|2017-03-02_18:18:11,793|D|MT|core.runners.base|||Execute command on the local server: plesk db "SELECT name FROM Modules WHERE name = 'plesk-multi-server'"
+|2017-03-02_18:18:11,802|D|MT|core.runners.base|||Command execution results:
=|2017-03-02_18:18:11,802|D|MT|core.runners.base|||stdout:
=|2017-03-02_18:18:11,802|D|MT|core.runners.base|||stderr:
=|2017-03-02_18:18:11,802|D|MT|core.runners.base|||exit code: 0
+|2017-03-02_18:18:11,802|D|MT|core.utils.panel_detector.target|||Target panel (automatically detected): plesk
+|2017-03-02_18:18:11,814|I|MT|plesk.connections.target_connections|||Target Plesk host: YY.YY.YY.YY
+|2017-03-02_18:18:11,815|I|MT|plesk.source.plesk.connections.source_connections|||Source Plesk 'source' host: XX.XX.XX.XX
+|2017-03-02_18:18:11,816|I|MT|plesk.connections.target_connections|||Target Plesk host: YY.YY.YY.YY
+|2017-03-02_18:19:12,312|D|MT|hosting_check.utils.http_client|||Unable to import NSS. We will use OpenSSL
+|2017-03-02_18:19:12,334|I|MT|core.migrator|||Initialize Plesk Migrator
+|2017-03-02_18:19:12,335|D|MT|core.utils.panel_detector.source|||Source panel (specified in configuration file): plesk
+|2017-03-02_18:19:12,335|D|MT|core.runners.base|||Execute command on the local server: plesk db "SELECT name FROM Modules WHERE name = 'plesk-multi-server'"
+|2017-03-02_18:19:12,344|D|MT|core.runners.base|||Command execution results:
=|2017-03-02_18:19:12,344|D|MT|core.runners.base|||stdout:
=|2017-03-02_18:19:12,344|D|MT|core.runners.base|||stderr:
=|2017-03-02_18:19:12,344|D|MT|core.runners.base|||exit code: 0
+|2017-03-02_18:19:12,345|D|MT|core.utils.panel_detector.target|||Target panel (automatically detected): plesk

Removed several lines because of post limit....

So here is txt file as well (see attachment)
 

Attachments

  • debug.txt
    27.3 KB · Views: 1
Man that character limit is annoying.

Piece of this session debug log:
Code: 
+|2017-03-02_18:24:32,903|D|MT|parallels|||Context:
=|2017-03-02_18:24:32,903|D|MT|parallels|||Traceback (most recent call last):
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/cli/common_cli.py", line 53, in run
=|2017-03-02_18:24:32,903|D|MT|parallels|||    options.method(migration.action_runner)
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/cli/migration_cli.py", line 387, in <lambda>
=|2017-03-02_18:24:32,903|D|MT|parallels|||    lambda runner: runner.run_entry_point('transfer-accounts'),
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/base.py", line 65, in run_entry_point
=|2017-03-02_18:24:32,903|D|MT|parallels|||    self.run(entry_point, handle_stop_mark=self._context.options.is_allow_stop)
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 67, in run
=|2017-03-02_18:24:32,903|D|MT|parallels|||    self._run_common_actions_tree(actions_tree, handle_stop_mark=handle_stop_mark)
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 95, in _run_common_actions_tree
=|2017-03-02_18:24:32,903|D|MT|parallels|||    self._run_common_actions_tree(action, action_path, handle_stop_mark=handle_stop_mark)
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 103, in _run_common_actions_tree
=|2017-03-02_18:24:32,903|D|MT|parallels|||    self._run_common_action_plain(action, action_path)
=|2017-03-02_18:24:32,903|D|MT|parallels|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 146, in _run_common_action_plain
=|2017-03-02_18:24:32,903|D|MT|parallels|||    raise MigrationError(full_failure_message)
=|2017-03-02_18:24:32,903|D|MT|parallels|||MigrationError: Failed to convert clients and subscriptions
=|2017-03-02_18:24:32,903|D|MT|parallels|||Cause: not well-formed (invalid token): line 92, column 33
=|2017-03-02_18:24:32,903|D|MT|parallels|||That is a critical error, migration was stopped.
+|2017-03-02_18:24:32,903|E|MT|parallels|||Failed to convert clients and subscriptions
=|2017-03-02_18:24:32,903|E|MT|parallels|||Cause: not well-formed (invalid token): line 92, column 33
=|2017-03-02_18:24:32,903|E|MT|parallels|||That is a critical error, migration was stopped.

See the rest in the attachment.

No clue if it helps or anything....
 

Attachments

  • session.debug.txt
    16.1 KB · Views: 2
Also I already tried the "solution" provided here: https://support.plesk.com/hc/en-us/...gration-failed-not-well-formed-invalid-token-
But that didn't provide any help, let alone, solve things at all...

Running: /usr/local/psa/bin/sw-engine-pleskrun regenerate-broken-passwords.php --help
Results in:
Code: 
Usage: regenerate-broken-passwords command [options]

    Available commands:
    --run                              Regenerate passwords which cannot be
                                       encrypted (db users, mail users, ftp
                                       users)
    --show                             Show entities (db users, mail users,
                                       ftp users) with passwords which cannot
                                       be encrypted
    --help or -h                       Displays this help page.

Version: 12.5.30_build1205150826.19 os_CentOS 5


Running: /usr/local/psa/bin/sw-engine-pleskrun regenerate-broken-passwords.php --show
Results in:
Code: 
Internal error: [Account::getPassword] cannot decrypt password to be plain.

Running /usr/local/psa/bin/sw-engine-pleskrun regenerate-broken-passwords.php --run
Results in:
Code: 
Internal error: [Account::getPassword] cannot decrypt password to be plain.

So that "solution" is not very helpful either...

I also tried several other things from the Knowledgebase, but none of them had any result or even worked.... :(

Also if you look up "Plesk Internal error: [Account::getPassword] cannot decrypt password to be plain." on Google. You only get old hits, as in for Plesk version <10.x
 
Hello! Could you please give me access(ssh, root) to your source and target servers in private conversation? This is the faster way to solve problems with your migration.
 
I am not to sure about sharing server credentials over a simple forum. Nowadays a lot of forums get hacked and such.
I created a support ticket at support.plesk.com with ticket #17821.

I supplied all information in it and mentioned this thread as well. You can find both server details (source / destination) in there.

In the meantime I will start migrating other servers... Because I already lost a lot of time because of this....
 
Unfortunately the Odin employee stopped working on this issue for several hours. Now our office is closed and we cannot continue anymore as a result of this.
Very disappointing, because we wasted another day because of this crappy migration tool not working as it should.

Also we have to redo everything once more on Monday, as we don't have any employees available to do this in the evening and/or during the weekend. Really one big disappointment.
If Odin (Plesk) employees don't have the time to fix these issues or are simply not interested in helping further. Please tell us beforehand. We were waiting on this the whole day!! So another day fully wasted.

My boss is now pretty furious about this. Probably this will result in getting a cPanel license and migrate everything over.
...maybe we will do this for all our Plesk licenses (675+).

The priority support went downhill after December. No easy way to escalate tickets anymore and/or access. Maybe this is indeed the time to move on permantly.
We are already using DirectAdmin as an alternative, maybe it's also time to move from Plesk to cPanel...?

Oh well...
 
HHawk said:
Unfortunately the Odin employee stopped working on this issue for several hours. Now our office is closed and we cannot continue anymore as a result of this.
Very disappointing, because we wasted another day because of this crappy migration tool not working as it should.

Also we have to redo everything once more on Monday, as we don't have any employees available to do this in the evening and/or during the weekend. Really one big disappointment.
If Odin (Plesk) employees don't have the time to fix these issues or are simply not interested in helping further. Please tell us beforehand. We were waiting on this the whole day!! So another day fully wasted.

My boss is now pretty furious about this. Probably this will result in getting a cPanel license and migrate everything over.
...maybe we will do this for all our Plesk licenses (675+).

The priority support went downhill after December. No easy way to escalate tickets anymore and/or access. Maybe this is indeed the time to move on permantly.
We are already using DirectAdmin as an alternative, maybe it's also time to move from Plesk to cPanel...?

Oh well...
Click to expand...

Hi HHawk

Plesk Support continues working on the ticket #17821 over the weekend in order to complete migration for you by Monday, when you come back at work.

They wrote about that on the ticket itself and now they will try to contact you to ensure about the same.
 
Hello!
The problem was in passwords contain non-UTF symbols on the source server and database inconsistency. Passwords of problem users were changed.
 
You must log in or register to reply here.

Similar threads

K
Issue Plesk Migrator - Obsidian 18.0.56 - Errors / unable to migrate
Replies
4
Views
2K
salvis
S
L
Resolved Migration issue [when admin username differs from "admin"]
Replies
8
Views
831
LevelupMedia
L
B
Issue Plesk Migration Tool: Access denied for user 'admin'@'localhost' (using password: YES)")
Replies
1
Views
159
Peter Debik
P
F
Issue Plesk migrator migrating to wrong IP
Replies
0
Views
440
fliegerhermi
F
L
Issue Plesk Migrator "the antivirus usage policy on destination server does not allow per email address"
Replies
0
Views
290
Leafy
L
Back
Top