• 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 Manager Problems

S

SeanV

Guest
Still getting this error "Error: No migration agents found. Data migration is not available."

So I know there are several threads regarding this issue but I still can't figure out whats wrong! I've made sure the remote server has the Firewall disabled and set the root logon to yes. It seems to be connecting fine. So frustrating as this Migration manager would make my life so much easier! Please Help!

I am going from Plesk 9.3 to Plesk 9.54 on two different Linux machines.
The logs on the new server I am migrating to are showing that its connecting here:
/usr/local/psa/PMM/msessions/

Note: Had to remove a "p" from each line because this form thought it was a picture...
[root@web2 20120306120117312]# vi migration.log
[12:01:17|INFO: 6966:.log] Launchpad started : /usr/local/psa/admin/bin/launchpad --send-scout --host=208.109.171.70 --login=f1admin --session-path=/usr/local/psa/PMM/msessions/20120306120117312
[12:01:17|DEBG: 6966:.libssh2pp.Socket] Socket created
[12:01:17|DEBG: 6966:.libssh2pp.Socket] Connecting to xxx.xxx.xxx.xxx:22
[12:01:17|DEBG: 6966:.libssh2pp.Socket] Resolving xxx.xxx.xxx.xxx
[12:01:17|DEBG: 6966:.libssh2pp.Socket] xxx.xxx.xxx.xxx was resolved to xxx.xxx.xxx.xxx
[12:01:17|DEBG: 6966:.libssh2pp.Socket] Connected
[12:01:17|DEBG: 6966:.libssh2pp.Session] Trying to start SSH session
[12:01:18|DEBG: 6966:.libssh2pp.Session] Selected aes256-cbc encryption method
[12:01:18|DEBG: 6966:.libssh2pp.Session] SSH session started successfully
[12:01:18|DEBG: 6966:.libssh2pp.Session] Requested authorization for user f1admin
[12:01:18|DEBG: 6966:.libssh2pp.Session] Getting userauth methods for user 'f1admin'
[12:01:18|DEBG: 6966:.libssh2pp.Session] Got the following allowed userauth methods: publickey,gssapi-with-mic,password
[12:01:18|DEBG: 6966:.libssh2pp.Session] Trying 'password' authentication
[12:01:18|DEBG: 6966:.libssh2pp.Session] Authenticated succesfully
[12:01:18|DEBG: 6966:.Ssh] Executing sh -c cd\ \;\ perl on the remote host
[12:01:18|DEBG: 6966:.libssh2pp.Session] Opening SSH channel for command 'sh -c cd\ \;\ perl'
[12:01:18|DEBG: 6966:.Ssh] remote stdout -> <?xml version="1.0"?><scout-result>
[12:01:18|DEBG: 6966:.Ssh] remote stdout -> <os-info os="Linux" loadavg="0.40 0.16 0.14"/>
[12:01:18|DEBG: 6966p.Ssh] remote stdout -> <remote-fs><fs mountpoint="/" device="/dev/sda3" mode="rw" size="155308982272" free="43006750720" type="ext3"/><fs mountpoint="/boot" device="/dev/sda1" mode="rw" size="103512064" free="81504256" type="ext3"/></remote-fs></scout-result>
[12:01:18|DEBG: 6966:.Ssh] Execution finished with return code 0
[12:01:18|DEBG: 6966:.libssh2pp.Channel] Closed
[12:01:18|DEBG: 6966:.libssh2pp.Session] SSH session finished
[12:01:18|DEBG: 6966:.libssh2pp.Socket] Connection closed
[12:01:18|INFO: 6966:.log] Launchpad finished. Exit code: 0
 
Fixed my Issue

Felt kinda stupid once I figured it out but it was pretty simple. I was using the wrong user account. Make sure you use the "root" account as this is the only account that will work. Also I had changed the "allow root access" to yes previous to figuring out the user problem which I think would have also been necessary to make this work correctly.
 
Back
Top