Support Questions
Find answers, ask questions, and share your expertise

Troubleshooting a host with concerning status

Troubleshooting a host with concerning status

New Contributor

Hi everybody!

We installed CDH using Cloudera Manager on two Virtual Machines. The first one is running ok with all services, but the second shows a "Concerning Health" status and we can't even assign Data Node role to it.

Host's status page on Cloudera Manager displays the following warnings:
"
This host is in contact with Cloudera Manager. The host's Cloudera Manager Agent's software version can not be determined.
6 unknown.
Details Not enough data to test: Test of whether a host is swapping memory.
Details Not enough data to test: Test of whether a host has network frame errors
Details Not enough data to test: Test of whether the host has network interfaces that appear to be operating at less than full speed.
Details Not enough data to test: Test of whether the hostname and canonical name for this host are consistent when checked from a Java process.
Details Not enough data to test: Test of whether a host resolves DNS names in a timely manner.
Details The status of the host's NTP service could not be determined.
"

Firstly, we thought that it was a network or security problem, but we already did these tests:
- They are on same LAN;
- Ping is ok between them;
- They share same root login acess;
- Command "/etc/init.d/cloudera-scm-agent status" displays ok

Do you have any idea what could cause this problem or how could we troubleshoot it?

Thanks a lot!

 

1 REPLY 1

Re: Troubleshooting a host with concerning status

Hi,

 

You should check with Telecom team or evaluate the switch port connected to this server network interface configuration, if the jumbo frame is enabled (MTU = 9000).

 

The same configuration must be verified in the network interface settings for the server.

 

A great way to check if the configuration is missing at one of the points is checking if there are dropped packages with the command 'ifconfig -a', executed in server SO console:

 

[root@<hostname> ~]# ifconfig -a
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 9000
inet Ip.Ad.re.ss netmask net.m.as.k broadcast bro.d.ca.st
ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet)
RX packets 522849928 bytes 80049415915 (74.5 GiB)
RX errors 274721 dropped 276064 overruns 0 frame 274721
TX packets 520714273 bytes 72697966414 (67.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

 

In this case, jumbo frame is configured only in server network interface.

 

Regards,

Caseiro.