- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
The hostname and canonical name for this host are not consistent
Created 09-29-2014 12:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
When I added a new node in cloudera cluster, The node went to bad health and shows error message like "The hostname and canonical name for this host are not consistent when checked from a Java process" Can any one help us to fix this issue.
Thanks,
Sathishkumar M
Sathish (Satz)
Created 09-29-2014 12:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
has the HOSTNAME field with the FQDN, not just the host name.
HOSTNAME=server1.example.com (good)
HOSTNAME=server1 (bad)
Edit this and reboot the host. Just restarting network services might not
work. Then let us know if the error still continues to be logged.
Gautam Gopalakrishnan
Created 09-29-2014 01:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
don't get complaints and on the host you just fixed. Do they look similar?
# python -c "import socket; print socket.getfqdn(); print
socket.gethostbyname(socket.getfqdn())"
Gautam Gopalakrishnan
Created 09-29-2014 12:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
has the HOSTNAME field with the FQDN, not just the host name.
HOSTNAME=server1.example.com (good)
HOSTNAME=server1 (bad)
Edit this and reboot the host. Just restarting network services might not
work. Then let us know if the error still continues to be logged.
Gautam Gopalakrishnan
Created 09-29-2014 01:14 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Gautam, It is working.
But, Other nodes in the same cluster dont have this FQDN in that path /etc/sysconfig/network and those are working fine.Is there any specific reason?
Sathish (Satz)
Created 09-29-2014 01:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
don't get complaints and on the host you just fixed. Do they look similar?
# python -c "import socket; print socket.getfqdn(); print
socket.gethostbyname(socket.getfqdn())"
Gautam Gopalakrishnan
Created 09-29-2014 02:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes,The onliner diplaying the FQDN in both the nodes. But we tried after removing that FQDN in /etc/sysconfig/network file also and we got the same output.
Sathish (Satz)
Created 09-29-2014 02:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
take effect.
Gautam Gopalakrishnan
Created 09-29-2014 04:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Gautam for your reply. We checked only after the reboot.
Sathish (Satz)
Created 09-29-2014 07:50 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you able to provide the python script output from both types of hosts? What OS are these hosts running?
Gautam Gopalakrishnan
Created 09-29-2014 10:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Network file for that node which is in bad health before change
cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=node10
Output of Python code
python -c "import socket; print socket.getfqdn(); print
socket.gethostbyname(socket.getfqdn())"
node10.cluster1.com
Network file for that node which is already in good health
cat /etc/sysconfig/network
python -c "import socket; print socket.getfqdn(); print
socket.gethostbyname(socket.getfqdn())"
node6.cluster1.com
Thanks
Sathishkumar M
Sathish (Satz)
Created 10-01-2014 04:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You were getting warnings for node10 earlier but don't any more. Does node6 have "HOSTNAME=node6" and still doesn't generate warnings?
Gautam Gopalakrishnan
