[jira] [Updated] (AMBARI-5111) Host confirmation failed on suse

["Vitaly Brodetskyi (JIRA)" <ji...@apache.org>]

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

Vitaly Brodetskyi updated AMBARI-5111:
--------------------------------------

    Attachment: AMBARI-5111.patch

> Host confirmation failed on suse
> --------------------------------
>
>                 Key: AMBARI-5111
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5111
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.5.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-5111.patch
>
>
> 1. On install options page passed 
> {noformat}
> suse1101.ambari.apache.org
> suse1102.ambari.apache.org - failed to register
> suse1103.ambari.apache.org
> {noformat}
> as an argument. 
> On ConfirmHosts page 2 hosts were registered successfully and 1 registration failed. 
> On the problematic host, agent is up and running. 
> {noformat}
> suse1102:~ # ambari-agent status
> Found ambari-agent PID: 14906
> ambari-agent running.
> Agent PID at: /var/run/ambari-agent/ambari-agent.pid
> Agent out at: /var/log/ambari-agent/ambari-agent.out
> Agent log at: /var/log/ambari-agent/ambari-agent.log
> suse1102:~ # ps aux | grep agent
> root     14890  0.0  0.4  85084 10368 ?        S    15:52   0:00 /usr/bin/python2.6 /usr/lib/python2.6/site-packages/ambari_agent/AmbariAgent.py start restart --expected-hostname=suse1102.ambari.apache.org
> root     14906  0.1  0.4 121180 11624 ?        Sl   15:52   0:03 /usr/bin/python2.6 /usr/lib/python2.6/site-packages/ambari_agent/main.py start restart --expected-hostname=suse1102.ambari.apache.org
> {noformat}
> Attached relevant cluster logs snapshot (after hadoop succesfully installed on 1-st and 3-rd hosts, 2-nd being skipped due to failed registration). 
> [~dlysnichenko] suggests, that a possible cause for this was that bootstrap failed prior to agent fully started. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)