FAQ
Praveen,



The problem is that your DNS server is set to a public DNS server (8.8.8.8)
which will not be able to resolve your internal names/IPs.



nslookup does not use your /etc/hosts file. Its purpose is to query DNS.
Please point your hosts to an internal DNS server that can resolve the
servers.



*Brian Burton*

*Customer Operations Engineer, Cloudera*



*From:* Aaron T. Myers
*Sent:* Monday, January 21, 2013 1:53 PM
*To:* scm-users; praveensripati@gmail.com
*Subject:* Re: Problem setting up a Cloudera Cluster



+scm-users@

bcc: cdh-user@



Hi Praveen, moving this message over to scm-users@cloudera.org, which
should be able to help you out with this issue.




--

Aaron T. Myers

Software Engineer, Cloudera



On Mon, Jan 21, 2013 at 8:53 AM, Praveen Sripati wrote:

Hi,

I am using Cloudera Manager 4.1 to setup a small cluster. At some point
during the cluster installation I get the below message

--
Inspect hosts for correctness
Inspector ran on all 0 hosts.
The inspector failed to run on all hosts.
--

Not exactly sure why. But, the documentation says that both forward and
reverse DNS should work. So, I tried nslookup followed by the IP address of
a different machine to get the below error message

training@guest1:/etc/network$ nslookup 192.168.1.101
Server: 8.8.8.8
Address: 8.8.8.8#53
server can't find 101.1.168.192.in-addr.arpa.: NXDOMAIN

An entry has been added to the /etc/hosts for the ip and I am able to ping
the machine by name. But, still the nslookup doesn't work.

How to get around this problem? BTW, I am using Ubuntu 12.04 Server.

Thanks,
Praveen

--

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 5 | next ›
Discussion Overview
groupscm-users @
categorieshadoop
postedJan 21, '13 at 7:04p
activeJan 23, '13 at 3:40p
posts5
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase