ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zeng qijia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13769) Ambari Automated Install with IPv6 hosts
Date Fri, 06 Nov 2015 14:34:27 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

zeng qijia updated AMBARI-13769:
--------------------------------
    Description: 
All of the hosts are using IPv6 address with Cent OS 7, Cluster Install Wizard ->Confirm
Host section failed, log shows ambari agent can't access the ambari host, but I just confirmed
that log in from agent to server via browser, and ssh without password are successful. Everything
is okay if I assign IPv4 address to hosts instead. I assume that it is cause by some hard
codes only works for IPv4 addresses in configure scripts.

Here is the error in log:
==========================
Running setup agent script...
==========================

Command start time 2015-11-06 08:50:12
Host registration aborted. Ambari Agent host cannot reach Ambari Server 'm1.hdp2:8080'. Please
check the network connectivity between the Ambari Agent host and the Ambari Server

Connection to m2.hdp2 closed.
SSH command execution finished
host=m2.hdp2, exitcode=1
Command end time 2015-11-06 08:50:12

ERROR: Bootstrap of host m2.hdp2 fails because previous action finished with non-zero exit
code (1)
ERROR MESSAGE: Connection to m2.hdp2 closed.

STDOUT: Host registration aborted. Ambari Agent host cannot reach Ambari Server 'm1.hdp2:8080'.
Please check the network connectivity between the Ambari Agent host and the Ambari Server

Connection to m2.hdp2 closed.

  was:
All of the hosts are using IPv6 address with Cent OS 7, Ambari installation ->confirm host
section failed, log shows ambari agent can't access the ambari host, but I just confirmed
that log in from agent to server via browser, and ssh without password are successful. Everything
is okay if I assign IPv4 address to hosts instead. I assume that it is cause by some hard
codes only works for IPv4 addresses in configure scripts.

Here is the error in log:
==========================
Running setup agent script...
==========================

Command start time 2015-11-06 08:50:12
Host registration aborted. Ambari Agent host cannot reach Ambari Server 'm1.hdp2:8080'. Please
check the network connectivity between the Ambari Agent host and the Ambari Server

Connection to m2.hdp2 closed.
SSH command execution finished
host=m2.hdp2, exitcode=1
Command end time 2015-11-06 08:50:12

ERROR: Bootstrap of host m2.hdp2 fails because previous action finished with non-zero exit
code (1)
ERROR MESSAGE: Connection to m2.hdp2 closed.

STDOUT: Host registration aborted. Ambari Agent host cannot reach Ambari Server 'm1.hdp2:8080'.
Please check the network connectivity between the Ambari Agent host and the Ambari Server

Connection to m2.hdp2 closed.


> Ambari Automated Install with IPv6 hosts
> ----------------------------------------
>
>                 Key: AMBARI-13769
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13769
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.1.2
>         Environment: CentOS 7, IPv6 
>            Reporter: zeng qijia
>
> All of the hosts are using IPv6 address with Cent OS 7, Cluster Install Wizard ->Confirm
Host section failed, log shows ambari agent can't access the ambari host, but I just confirmed
that log in from agent to server via browser, and ssh without password are successful. Everything
is okay if I assign IPv4 address to hosts instead. I assume that it is cause by some hard
codes only works for IPv4 addresses in configure scripts.
> Here is the error in log:
> ==========================
> Running setup agent script...
> ==========================
> Command start time 2015-11-06 08:50:12
> Host registration aborted. Ambari Agent host cannot reach Ambari Server 'm1.hdp2:8080'.
Please check the network connectivity between the Ambari Agent host and the Ambari Server
> Connection to m2.hdp2 closed.
> SSH command execution finished
> host=m2.hdp2, exitcode=1
> Command end time 2015-11-06 08:50:12
> ERROR: Bootstrap of host m2.hdp2 fails because previous action finished with non-zero
exit code (1)
> ERROR MESSAGE: Connection to m2.hdp2 closed.
> STDOUT: Host registration aborted. Ambari Agent host cannot reach Ambari Server 'm1.hdp2:8080'.
Please check the network connectivity between the Ambari Agent host and the Ambari Server
> Connection to m2.hdp2 closed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message