Home Forums HDP on Linux – Installation Ambari heath check – Ambari agent with connection time out

Tagged: ,

This topic contains 5 replies, has 3 voices, and was last updated by  Son Hai Ha 5 months ago.

  • Creator
    Topic
  • #54129

    Son Hai Ha
    Participant

    I install Hadoop and its services onto a cluster of VMs on Open Stack and use Ambari of HortonWork to monitor the services. I opened all the necessary ports for the services to run already. But there is still one problem/port that I cannot figure out. I used all the default setting.

    In particular,

    For ambari-server: port 8440 and 8080
    For ambari-agent: port 8441

    The agent could not access to some services that I don’t know. I hope the issue due to a blocked port. I try to find the port to open but don’t have an answer. I also looked at the log file of the agent but cannot find out the issues. Anyone have the experiences with Ambari?

    Here are some images of the problem.

    http://i.stack.imgur.com/s1FZl.png

    All the services look good. Mapreduce can run service check successfully

    http://i.stack.imgur.com/evpKD.png

    But every host that run the agent got a problem and I cannot see the health of those remote host with Ganglia, even though Ganglia reported healthy

    http://i.stack.imgur.com/Th632.png

    A closer look on the issues at every hosts

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Ambari heath check – Ambari agent with connection time out’ is closed to new replies.

  • Author
    Replies
  • #54255

    Son Hai Ha
    Participant

    Hi,
    This problem is also fixed now. A lot of ports have to be opened for Ganglia, both UDP and TCP types. I think the manual should contains these information, otherwise for beginner like me, it took a week to figure out the problem.
    Thank you guys for helping!

    Collapse
    #54253

    Son Hai Ha
    Participant

    Hi,
    I still have one more problem.
    The host metrics tab doesn’t have any data. Ganglia run fully well and there no issue reported by Ambari.

    Collapse
    #54252

    Son Hai Ha
    Participant

    Thanks Jeff.
    The port 8670 was blocked by my switch. The problem is solved now. Thanks a lot!!!

    Collapse
    #54236

    Jeff Sposetti
    Moderator

    Nagios checks the health of the Agent itself, which listens on a ping-port.

    The port between the Nagios server and the agents machines needs to be open.

    Check /etc/ambari-agent/conf/ambari-agent.ini and the ping_port property. Confirm that port is accessible from the host running the Nagios server.

    Collapse
    #54152

    Dave
    Moderator

    Hi Son,

    The ambari agent needs to connect to the server on port 8441. Can you telnet from the agent machine to the ambari server on 8441 and 8440 ?

    Thanks

    Dave

    Collapse
Viewing 5 replies - 1 through 5 (of 5 total)