Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Cloudera manager admin console Issues

Cloudera manager admin console Issues

Expert Contributor

Hello ,
I followed the  steps given in https://groups.google.com/a/cloudera.org/forum/#!topic/scm-users/xr0Yr5_Hilc for getting rid of "The hostname and canonical name for this host are not consistent when checked from a Java process."  which was showing after installing Cloudera Manager 5. The Cluster and the Management service were in red so i followed the steps .

                                                   It seems to work for a while but suddenly my admin console crashed and didnt open with my <ipaddress>:7180 . Instead  it opened with 127.0.0.1:7180. How to change this back :( :( .. Please help

hostname : INCHCMPCCHE01
hostname -f : ip00958.mycomp.ad

etc/hosts :
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
172.18.42.119   ip00958.mycomp.ad INCHCMPCCHE01

etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=INCHCMPCCHE01

1. I need the console to open with my ip address ie 172.18.42.119:7180
2. And also to get rid of "The hostname and canonical name for this host are not consistent when checked from a Java process." .

Please help me out ..

Thanks
Bala

Thanks
Bala
19 REPLIES 19
Highlighted

Re: Cloudera manager admin console Issues

Cloudera Employee

What are the contents of /etc/resolv.conf?

 

Thanks,

Adam

Re: Cloudera manager admin console Issues

Expert Contributor

Hi Mark ,

 

Contents of /etc/resolv.conf :

 

domain mycomp.ad
search mycomp.ad
nameserver 172.18.18.210
nameserver 172.18.129.210
nameserver 172.19.129.210
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 172.19.57.210

 

Thanks

Bala

Thanks
Bala

Re: Cloudera manager admin console Issues

Cloudera Employee

To the particular 2 issues:
1) Cloudera Manager does not come up on IP address but only on localhost (127.0.0.1)
Cloudera Manager will bind to wildcard address by default, so any route that gets you to the host should get you there. That is why localhost will get you there. The bigger thing is that the IP address stopped working - this to me indicates that you IP address may have changed!

 

To validate:

Check that CM is listening, and on wildcard:

netstat -a -t --numeric-ports -p | grep 7180

 

List your IP address:

ifconfig

 

 


2) Your forward and reverse DNS lookup do not appear to agree on what your hostname is.
To validate:

 

See what the DNS server thinks the IP address is:

dig @172.18.18.210 INCHCMPCCHE01

dig @172.18.129.210 INCHCMPCCHE01

 

Then take that IP address - for the next command

 

Reverse DNS lookup for the IPs:

host <ipaddress>

 

 

 

Please provide the output of all of these commands

 

 

Re: Cloudera manager admin console Issues

Expert Contributor

Hi Adam ,

 

Results of the commands :

 

1. netstat -a -t --numeric-ports -p | grep 7180 :

 

tcp        0      0 *:7180                      *:*                         LISTEN      2705/java          
tcp        0      0 localhost:7180              localhost:45005             ESTABLISHED 2705/java          
tcp        0      0 ip00958.mycomp:48430 ip00958.mycompany:7180 ESTABLISHED 8375/java          
tcp        0      0 localhost:7180              localhost:45004             ESTABLISHED 2705/java          
tcp        0      0 localhost:7180              localhost:45007             ESTABLISHED 2705/java
tcp        0      0 ip00958.mycomp:48423 ip00958.mycompany:7180 ESTABLISHED 8441/java
tcp        0      0 ip00958.mycomp:48407 ip00958.mycompany:7180 ESTABLISHED 8397/java
tcp        0      0 localhost:45007             localhost:7180              ESTABLISHED 6221/firefox
tcp        0      0 ip00958.mycomp:48431 ip00958.mycompany:7180 ESTABLISHED 8419/java
tcp        0      0 localhost:7180              localhost:50430             ESTABLISHED 2705/java
tcp        0      0 localhost:45004             localhost:7180              ESTABLISHED 6221/firefox
tcp        0      0 localhost:50430             localhost:7180              ESTABLISHED 6221/firefox
tcp        0      0 ip00958.mycompany:7180 ip00958.mycomp:48407 ESTABLISHED 2705/java
tcp        0      0 localhost:45005             localhost:7180              ESTABLISHED 6221/firefox
tcp        0      0 ip00958.mycompany:7180 ip00958.mycomp:48431 ESTABLISHED 2705/java
tcp        0      0 ip00958.mycompany:7180 ip00958.mycomp:48430 ESTABLISHED 2705/java
tcp        0      0 ip00958.mycompany:7180 ip00958.mycomp:48423 ESTABLISHED 2705/java

2. ifconfig :

 

eth0      Link encap:Ethernet  HWaddr F0:92:1C:EF:87:D2
          inet addr:172.18.42.119  Bcast:172.18.43.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:478073 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41213 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:90929045 (86.7 MiB)  TX bytes:8301087 (7.9 MiB)
          Interrupt:20 Memory:f7c00000-f7c20000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5169387 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5169387 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4252024333 (3.9 GiB)  TX bytes:4252024333 (3.9 GiB)

virbr0    Link encap:Ethernet  HWaddr 52:54:00:47:30:E2
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

3. dig @172.18.18.210 INCHCMPCCHE01 :

 

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6 <<>> @172.18.18.210 INCHCMPCCHE01
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 27079
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;INCHCMPCCHE01.                 IN      A

;; Query time: 1 msec
;; SERVER: 172.18.18.210#53(172.18.18.210)
;; WHEN: Tue Jun 24 23:46:41 2014
;; MSG SIZE  rcvd: 31

4. dig @172.18.129.210 INCHCMPCCHE01 :

 

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6 <<>> @172.18.129.210 INCHCMPCCHE01
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62416
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;INCHCMPCCHE01.                 IN      A

;; Query time: 1 msec
;; SERVER: 172.18.129.210#53(172.18.129.210)
;; WHEN: Tue Jun 24 23:47:12 2014
;; MSG SIZE  rcvd: 31

 

I had run the commands . But i am not sure they have given the right result or not . So waiting for your response to proceed.

 

Thanks

Bala

 

ip00958

Thanks
Bala

Re: Cloudera manager admin console Issues

Expert Contributor
Adam , awaiting for your response ....
Thanks
Bala

Re: Cloudera manager admin console Issues

Cloudera Employee

Hi Bala,

 

It appears that CM is listening on 7180. That's good.

It also appears that 172.18.42.119 is your IP address. That's also good.

 

I'm unable to explain why CM wouldn't be responding if you browse to

http://172.18.42.119:7180

Is a firewall enabled? Are you attempting to browse to the UI from the same host on which CM is installed?

 

 

As for the hostname issue, it appears to me that your shortname (INCHCMPCCHE01) is not recognized by your DNS configuration.

Can you try the following:

dig @172.18.18.210 ip00958.mycomp.ad

 

 

Re: Cloudera manager admin console Issues

Expert Contributor

Hello Adam ,

1. My firewall is disabled and CM is installed in only one host.

2. Rightnow my hostname is INCHCMPCCHE01 and hostname -f is ip00958.mycomp.ad . Should the both be same ??

3. dig @172.18.18.210 ip00958.mycomp.ad
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6 <<>> @172.18.18.210 ip00958.mycomp.ad
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37048
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ip00958.mycomp.ad. IN    A

;; ANSWER SECTION:
ip00958.mycomp.ad. 1200 IN A    172.18.42.119

;; Query time: 1 msec
;; SERVER: 172.18.18.210#53(172.18.18.210)
;; WHEN: Fri Jun 27 00:53:19 2014
;; MSG SIZE  rcvd: 65

Wating for your response


Thanks

Bala

 

 

Thanks
Bala

Re: Cloudera manager admin console Issues

Cloudera Employee

Hi Bala,

 

I think that setting the hostname to INCHCMPCCHE01 is the problem.

Can you modify 

/etc/sysconfig/network

 

and set

HOSTNAME=ip00958.mycomp.ad

 

Since that appears to be the name that your DNS recognizes, I would suggest using that everywhere.

 

Then reboot the node, and see if the concern goes away.

 

Thanks

Adam

Re: Cloudera manager admin console Issues

Expert Contributor
Adam I am changing it . Do i need to change in etc/hosts too , right now
my etc/hosts is
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
172.18.42.119 ip00958.mycomp.ad INCHCMPCCHE01

is this ok ?
Thanks
Bala