ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <>
Subject [jira] [Created] (AMBARI-5111) Host confirmation failed on suse
Date Mon, 17 Mar 2014 16:37:42 GMT
Vitaly Brodetskyi created AMBARI-5111:

             Summary: Host confirmation failed on suse
                 Key: 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

1. On install options page passed 
{noformat} - failed to register
as an argument. 

On ConfirmHosts page 2 hosts were registered successfully and 1 registration failed. 

On the problematic host, agent is up and running. 
suse1102:~ # ambari-agent status
Found ambari-agent PID: 14906
ambari-agent running.
Agent PID at: /var/run/ambari-agent/
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/
start restart
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/
start restart
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

View raw message