Error trying to start Migration Manager

[damon]

On two servers with 9.21 I try to start PMM using the same credentials I use to ssh in to the old box with Putty. Instead of starting it tries for a long time, then fails with error.

Error: Host example.com is not accessible

I've tried using the old server hostname and also the IP. The same login info works with Putty and WinSCP for SSH.

What could be stopping Migration Manager?

 

[damon]

More info on this:

I've discovered that I can't ping from new server to old (or back). I get one ping then it times out.

I tried to do a tracert from one to the other and that gets two hops then times out.

These are both 1and1 servers with IP's starting with 74.208.xxx.xxx

Does 1and1 stop traffic between servers in their data centers? If so that would kill Migration Manager.

 

[Total]

More info on this:

I've discovered that I can't ping from new server to old (or back). I get one ping then it times out.

I tried to do a tracert from one to the other and that gets two hops then times out.

These are both 1and1 servers with IP's starting with 74.208.xxx.xxx

Does 1and1 stop traffic between servers in their data centers? If so that would kill Migration Manager.

are both ssh's set to ports 22 ??

 

[damon]

are both ssh's set to ports 22 ??

yes, I can use putty on port 22 to ssh into both servers.

I tried to use command line ssh to connect from each macine to the other. When I do new to old I just get a timeout eventually. When I try to connect to the new machine from the old, I get a "No route to host" error.

 

[Total]

Did you try to accomplish this thru the migration manager ?

 

[damon]

Yes, I got migration manager working. The problem I had turned out to be that two servers in the same 1and1 datacenter needed to have the subnet mask set to 255.255.255.255 for each IP on each server. Mine were all 255.255.0.0

After that was fixed and networking restarted, MM started transfering sites, it appears to be working well now.

 

[Total]

That is great news , but just walk away , and leave it be ... Please let us know how it goes . Mine went 100 % .. Good luck

 

[Yeolegood]

Hello,

Looks like I am late wit the the answer, but this issue is handled in one of our knowledge base articles:

http://kb.odin.com/en/807

 

[Markus_Eyrich]

Transfer Domains between Plesk 9.2.1 Servers

Hi There,

I got a other problem with the migration manager. I get the same message (Host xxx is not accessible) BUT i checked everything else already. I can ping the server i want to get data from, even tracert is no problem. I can transfer files with scp from source to destination server, there's no firewall, standard ssh port 22, protocol version 2 allowed and so on. Everything that is in the kb is checked and working. The only difference here is that i try to get data from a Plesk 9.2.1 Server which uses Ubuntu 8.04 LTS, but the destination machine is Centos 5.3. Since we have many installations around i tried different server (all CentOS 5.3) and i always get the same error. I even see that the connection with the given user and password is accepted (in the auth.log on the ubuntu machine). If i try vice versa, so the ubuntu machine as destination of the migration, all works fine. Trying 3 different CentOS Machines as destination for the migration always fails.

Any ideas?

 

[Markus_Eyrich]

Again, for what is this forum for? No answer from a Plesk representative for days now.....

 

[Markus_Eyrich]

Since we opened a Ticket for this issue here's the fix. The Problem was that the source server has set it's system locale to "de_DE.UTF-8" and somehow the plesk migration agents couldn't read out the available disk space then. The destination system connects to the source system via ssh and then fails. Just set the locale to your language without "UTF-8" Encoding and everything works as expected.