1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Host is not accessible

Discussion in 'Plesk 10.x for Linux Issues, Fixes, How-To' started by caballero, Aug 22, 2011.

  1. caballero

    caballero New Pleskian

    12
    60%
    Joined:
    Aug 22, 2011
    Messages:
    2
    Likes Received:
    0
    I have 2 dedicated servers both running CentOS 5.3 and Plesk 10.0.0.

    I'm trying to migrate stuff from one to the other but it's not happening, just after I fill out "Migration settings" and press "Next" I get "Host xx.xx.xx.xx is not accessible"

    What I've done so far that didn't have any effect whatsoever:

    stopped the firewall on the source server
    enabled "PermitRootLogin yes" in /etc/ssh/sshd_config
    and restarted the service

    Any ideas?

    UPDATE: I was able to initiate the migration from the new server (which is blank) to an old one (I need vice versa), so there's definitely something relating settings.

    I pulled out a log file, and this is the place where everything fails:



    23117: 2011-08-22 16:34:22,949 INFO Executing <subprocess[23118] '/usr/local/psa/admin/bin/launchpad --send-scout --host=XX.XXX.XXX.XXX --login=root --session-path=/usr/local/psa/PMM/msessions/2011082216342281'>
    23117: 2011-08-22 16:34:32,983 INFO Subprocess raised ExecuteException: Subprocess <subprocess[23118] '/usr/local/psa/admin/bin/launchpad --send-scout --host=XX.XXX.XXX.XXX --login=root --session-path=/usr/local/psa/PMM/msessions/2011082216342281'> was finished with exit code 10
    == STDOUT ====================

    == STDERR ====================
    Cannot send scout to the remote host
    23117: 2011-08-22 16:34:32,983 ERROR Subprocess <subprocess[23118] '/usr/local/psa/admin/bin/launchpad --send-scout --host=XX.XXX.XXX.XXX --login=root --session-path=/usr/local/psa/PMM/msessions/2011082216342281'> was finished with exit code 10
    == STDOUT ====================

    == STDERR ====================
    Cannot send scout to the remote host
    23117: 2011-08-22 16:34:32,983 INFO Outgoing packet:
    <?xml version="1.0" encoding="UTF-8"?>
    <response>
    <errcode>130</errcode>
    <errmsg>Host XX.XXX.XXX.XXX is not accessible</errmsg>
    </response>
     
    Last edited: Aug 22, 2011
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,547
    Likes Received:
    1,241
    Location:
    Novosibirsk, Russia
    These errors means that migration manager failed upload agent to the remote server or the connection with the remote server was lost. Migration Manager uses SSH protocol for uploading of migration agents to source server and dump files retrieving. Make sure that:

    - SSH server is running and SSH (22) port is opened on the source server (you are performing the migration from),
    - SSH server on the source server allows connecting it with SSH version 2 protocol,
    - you are able to login from destination server to the source one via SSH under the user you specified during the migration. Also check that you can transfer a file from the source server to the destination Plesk server with scp command.
     
Loading...