AnsweredAssumed Answered

Host not reachable issue on interogating stage

Question asked by sivam on Jun 30, 2015
Latest reply on Jul 8, 2015 by Ted Dunning
while installing mapr for the 3node cluster, receiving host not reachable error on interrogation stage.

Now running on Added Control Nodes: [xx.xxx.191.xxx]

    * 19:37:44 Interrogating Node(s), Validating Prerequisites, and Starting
    Install
    fatal: [xx.xxx.191.xxx] => SSH encountered an unknown error during the
    connection. We recommend you re-run the command using -vvvv, which will
    enable SSH debugging output to help diagnose the issue
    * 19:37:44 Installing Extra Package Repositories If Needed
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Detecting Operating System
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Detecting Operating System
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Creating MapR User
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Installing and Configuring NTP Service
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Installing OpenJDK Packages If Needed
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Detecting Operating System
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Installing MapR Packages
    FATAL: no hosts matched or all hosts have already failed -- aborting
    * 19:37:44 Disabling MapR Services Until Configured
    FATAL: no hosts matched or all hosts have already failed -- aborting
    FATAL: no hosts matched or all hosts have already failed -- aborting
    Host: xx.xxx.191.xxx is unreachable
    Control Nodes have failures. Please fix the failures and re-run the
    installation. For more information refer to the installer log at
    /opt/mapr-installer/var/mapr-installer.log

Note: We are using Google Compute Engine as the Instances.(n1-standard-2 (2 vCPUs, 7.5 GB memory-Centos 6), HTTPS and HTTP traffics are enabled.

Same issue happens with AWS instances as well.

Outcomes