• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Migration Manager 'Host XXX is not accessible'

B

brendog

Guest
As stated on my last thread, I'm a newbie to all this, so please excuse my ignorance! :)

When I last upgraded my server I used Migration Manager without a problem - it was incredibly easy and worked straight away.... but not this time.

Both source and destination servers are Linux, with source using Plesk 9.2.3 and destination using 9.3. I enter all the details in the Migration Manager page on the destination server, hit 'next', but then after a few moments it just says:

Error: Host ******** is not accessible

Any suggestions? The solution found at the bottom of this thread goes way over my head - http://forum.parallels.com/showthread.php?t=89946 - I've started using putty but I'm only just getting to grips with it!
 
So, can you connect from destination server to source server as root via ssh?
 
Yes, just tried that and I can... can I migrate through SSH?
 
Do you have any errors in logs from /usr/local/psa/PMM/logs/ ? Are hostnames of both servers resolvable from one server to another and vice versa?
 
We had the same problems once and i opened a ticket for it. The problem in our case was the system locale on one of the server's... Do you use any locale settings with special character's or german umlaut's such as "äöü" and so on? If yes, set the locale to something without that. The problem was as migration manager connected to the destination server and tried to do a "df -h" on the console, the german umlaut stuff in our server couldn't be read and the above error message appeared. I also suggested that this should be somewhere in a knowledgebase article OR should be fixed, since as for example using a de-DE.UTF-8 as Locale (with german umlaut's) is quite common in germany and a lot of people use plesk.
 
Back
Top