• 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

Resolved Paramiko Missing: Error when running Migrator

linuxKurt

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.52
I am doing a 2nd dry run migration on a new server I have. The new server is running the newest version of PLESK, the old server is a running CentOS 6 Plesk 12.5 (64 Bit).

The main issue is that when I run the migration tool, it cannot authenticate to the old server. I tried using root and password and that does not work. I shifted to SSH and that initially did not work. The last successful dry run there was a PLESK ticket opened by my service provider and they did something that allowed the servers to communicate using a key created with ECDSA.

I do not have the details of that ticket or what they did to mitigate the SSH issue.

I have created a key using ssh-keygen -t ecdsa on the new Ubuntu Server. I have copied the public key manually to the "source" server. copying the key using SSH was not working.

So I have a proper ecdsa key on my Target server, and a proper public key on my Source server. When I run the Plesk Migration tool, I get the following error. Attached is a screenshot of my migration tool settings.

"[2023-05-05 15:42:23][ERROR] Internal Plesk Migrator error: 'No module named paramiko', migration is aborted. See the traceback in debug log for more information."

Plesk Migration Tool Screenshot Paramiko Error.jpg
 
That's not a login issue, that's a module issue, it's looking for a module called paramiko which you do not have. Sounds like you might have paramiko on the old server and so you would need to have it on the new server as well otherwise it will not work. So get that module installed and you should be good to go.


Shows how to install it btw.

Alternatively if you know the site on the old server that's utilizing that module and don't mind breaking it temporary you can just uninstall the module from the old server then worry about fixing it on the new server later.
 
That's not a login issue, that's a module issue, it's looking for a module called paramiko which you do not have. Sounds like you might have paramiko on the old server and so you would need to have it on the new server as well otherwise it will not work. So get that module installed and you should be good to go.


Shows how to install it btw.

Alternatively if you know the site on the old server that's utilizing that module and don't mind breaking it temporary you can just uninstall the module from the old server then worry about fixing it on the new server later.
I would like to uninstall from the old server for now, can you provide a reference for uninstalling paramiko on a CentOS 6 server?
 
I installed Paramiko on the target server and am getting the same error. It is instantaneous, there is no way it checked the other server in how fast it returned the error. There must be some cache or something. I restarted the migration from new, also restarted the server to see if that would help.

1683375787757.png
 
Back
Top