• 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

Migration Error: Host not accessible.

D

Dan C

Guest
Migrating from server with 9.2.3 (windows 2003) to 9.2.3 (windows 2008). I am receiving error message:
"Error: Host xxx.xxx.xxx.xxx is not accessible"

Steps taken:
- Migration agent running on source server (tried changing port and channel type, updated config on destination server to reflect)
- Client for MS Networks and File and Print Sharing installed on both servers (able to access \\localhost\c$ on both)
- Restarted both servers
- Turned off Windows Firewall on both servers
- Can ping source server from destination server

Any ideas?
 
Do you have $ symbol in the password? Just remove it as possible workaround. Also make sure that password has not more that 14 symbols.
 
Migration Error

Ok - the password issue fixed the "Host not accessible" error. Can I make a suggestion on making that error more clear? The session log file shows that it is indeed an authentication error, but "host not accessible" is not very helpful in troubleshooting.

I am now receiving a different error however:

Error: The version of Plesk Migration Agent running on the remote host is older than the version of Plesk Migration Manager being currently used. Please install Plesk Migration Manager components of the same version.

Troubleshooting steps:
- Both servers have 9.2.3 installed.
- I have installed the Plesk Migration Agent from the "Synchronize" link under Migration Manager
- I have also tried using the 9.2.3 Migration Agent manually from: http://www.parallels.com/download/plesk/utilities/
- Session logs didn't tell me anything more specific (version numbers mismatched, etc) that I could find.

Is there a newer version somewhere that I am not aware of?
 
Strange. Reason of such behaviour is not clear for me and I have not found nothing useful in our internal resources. Seems migration logs from PMM\msession folder should be investigated. I think that you should contact support team if you not find any useful in logs.
 
From the logs:

1356: Info 11/01/2010 01:21:33.937 : CrossSysAgent::CheckVersion. remoteVersion (9.203.3544.19131), localVersion (9.300.3643.12193)

9.3? That is really odd as the plesk version installed is 9.2.3. Is there a 9.3 migration agent I can install? Or should I upgrade both servers to 9.3?
 
Additionally, I have tried removing Migration Manager through control panel add/remove programs > setup on the destination machine and adding it again. It still tells me 9.300.3643.12193 is the local version.
 
I have upgraded both servers to 9.3. However, neither of the 9.3 migration agent download links you provided work.
 
Ok - migration agent installed on both. When I run a migration, I see a message that says:

"Notice: Undefined variable: scouts in C:\Program Files (x86)\Parallels\Plesk\admin\plib\backup\MigrationAgentForm.php on line 64"

Then a message that says:

"Error: No migration agents found. Data migration is not available."

From the logs, it appears that it is not correctly identifying the version of Plesk installed. Confirming that 9.3.0 is installed on both servers.

-------------


4968: Info 13/01/2010 01:33:20.218 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.218 : PleskXMigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.234 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.234 : Plesk84MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.234 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.234 : Plesk811MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.234 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.234 : Plesk83MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.250 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.250 : Plesk75MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.250 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.250 : Plesk82MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.250 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.250 : Plesk80MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.265 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.265 : Plesk76MigrationPlatform::platformDetected: (False)
4968: Info 13/01/2010 01:33:20.265 : >>>Detected Plesk version (9.3.0)<<<
4968: Debug 13/01/2010 01:33:20.265 : Plesk86MigrationPlatform::platformDetected: (False)
4968: Debug 12/01/2010 23:33:25.625 : /\/\/\/\/\/\/\/\ End SyncLog /\/\/\/\/\/\/\/\
4968: Debug 12/01/2010 23:33:25.640 : PsaMigrMng90::GetHostInfo successfully finished
4968: Debug 12/01/2010 23:33:25.640 : Output info:
4968: Debug 12/01/2010 23:33:25.640 : <?xml version="1.0" encoding="UTF-8"?><scout-result><os-info os="Microsoft Windows NT 5.2.3790 Service Pack 2" loadavg="31.25" /><remote-fs /></scout-result>
4968: Debug 12/01/2010 23:33:25.640 : Saving result...
4968: Debug 12/01/2010 23:33:25.640 : migrmng exits with code 0
 
I have submitted request to developers regarding this problem. I will update this thread with results as soon as I receive it from developers.
 
With the 9.3 migration agent still installed, I reinstalled 9.2.3 on both servers and ran the migration successfully!
 
I used the patch and the error went away, now I can get to select the domains to migrate and start migrating. The migration then fails with no log message. Where are the logs located?
 
I used the patch and the error went away, now I can get to select the domains to migrate and start migrating. The migration then fails with no log message. Where are the logs located?

Plesk\PMM\logs\
 
More interesting stuff. I was able to migrate a few domains, now it seems to stall at 50% no matter what I do.

From the log for the session:

<execution-result status="warnings">
<object name="backup" type="backupowner">
<message code="ArgumentException" severity="error">Version string portion was too short or too long.</message>
</object>
</execution-result>
 
Back
Top