Grokbase › Groups › Hadoop › scm-users › April 2014
FAQ
How does one deal this? All nodes are deamed not healthy. From
http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/cdh4ig_topic_11_1.html

I mean..I set my /etc/hosts and /etc/hostname they way cloudera likes yet I
get the below

  uname -a
Linux manager-107170235192-sf-development.cloudera 3.8.0-29-generic
#42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64
GNU/Linux

hostname
manager-107170235192-sf-development.cloudera

hostname --fqdn
manager-107170235192-sf-development.cloudera.test.com

nano /etc/sysconfig/network
EMPTY FILE

  host -v -t A `hostname`
Trying "manager-107170235192-sf-development.cloudera"
Received 137 bytes from 8.8.4.4#53 in 102 ms
Trying "manager-107170235192-sf-development.cloudera"
Host manager-107170235192-sf-development.cloudera not found: 3(NXDOMAIN)
Received 137 bytes from 8.8.4.4#53 in 2 ms


/sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 04:01:17:96:5d:01
           inet addr:107.170.235.192 Bcast:107.170.235.255
Mask:255.255.255.0
           inet6 addr: fe80::601:17ff:fe96:5d01/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
           RX packets:943909 errors:0 dropped:0 overruns:0 frame:0
           TX packets:782040 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1504778185 (1.5 GB) TX bytes:3453248322 (3.4 GB)

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

Search Discussions

  • David Montgomery at Apr 29, 2014 at 12:41 am ⇧
    PS..here is my /etc/resolv.conf
      on ubujtu 12.04


    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
    resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 8.8.4.4
    nameserver 8.8.8.8
    nameserver 209.244.0.3



    Advice

    This is a host health test that checks that the host's hostname and
    canonical name are consistent when checked from a Java process.

    A failure of this health test may indicate that the host's DNS
    configuration is not correct. Check the Cloudera Manager Agent log for the
    names that were detected by this test.

    The hostname and canonical name are considered to be consistent if the
    hostname or the hostname plus a domain name is the same as the canonical
    name. This health test uses domain names from the domain and search lines
    in /etc/resolv.conf. This health test does not consult /etc/nsswitch.conf
    and may give incorrect results if /etc/resolv.conf is not used by the host.
    There may be a delay of up to 5 minutes before this health test picks up
    changes to /etc/resolv.conf.

    This test can be configured using the Hostname and Canonical Name Health
    Check host configuration setting.



    On Tue, Apr 29, 2014 at 6:01 AM, David Montgomery wrote:

    How does one deal this? All nodes are deamed not healthy. From
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/cdh4ig_topic_11_1.html

    I mean..I set my /etc/hosts and /etc/hostname they way cloudera likes yet
    I get the below

    uname -a
    Linux manager-107170235192-sf-development.cloudera 3.8.0-29-generic
    #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64
    GNU/Linux

    hostname
    manager-107170235192-sf-development.cloudera

    hostname --fqdn
    manager-107170235192-sf-development.cloudera.test.com

    nano /etc/sysconfig/network
    EMPTY FILE

    host -v -t A `hostname`
    Trying "manager-107170235192-sf-development.cloudera"
    Received 137 bytes from 8.8.4.4#53 in 102 ms
    Trying "manager-107170235192-sf-development.cloudera"
    Host manager-107170235192-sf-development.cloudera not found: 3(NXDOMAIN)
    Received 137 bytes from 8.8.4.4#53 in 2 ms


    /sbin/ifconfig
    eth0 Link encap:Ethernet HWaddr 04:01:17:96:5d:01
    inet addr:107.170.235.192 Bcast:107.170.235.255
    Mask:255.255.255.0
    inet6 addr: fe80::601:17ff:fe96:5d01/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:943909 errors:0 dropped:0 overruns:0 frame:0
    TX packets:782040 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1504778185 (1.5 GB) TX bytes:3453248322 (3.4 GB)








    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • David Montgomery at Apr 29, 2014 at 12:51 am ⇧
    PPS

    I did the below. I un selected tge healt check and restart the agent. I
    have a green light now. Question..was that wise to have DNS Resolution
    Disabled?

    Thanks


    Monitoring Hostname and Canonical Name Health Check

    Reset to the default value: true

    Whether the hostname and canonical names for this host are consistent when
    checked from a Java process.

    On Tue, Apr 29, 2014 at 8:41 AM, David Montgomery wrote:

    PS..here is my /etc/resolv.conf
    on ubujtu 12.04


    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
    resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 8.8.4.4
    nameserver 8.8.8.8
    nameserver 209.244.0.3



    Advice

    This is a host health test that checks that the host's hostname and
    canonical name are consistent when checked from a Java process.

    A failure of this health test may indicate that the host's DNS
    configuration is not correct. Check the Cloudera Manager Agent log for the
    names that were detected by this test.

    The hostname and canonical name are considered to be consistent if the
    hostname or the hostname plus a domain name is the same as the canonical
    name. This health test uses domain names from the domain and search lines
    in /etc/resolv.conf. This health test does not consult /etc/nsswitch.conf
    and may give incorrect results if /etc/resolv.conf is not used by the host.
    There may be a delay of up to 5 minutes before this health test picks up
    changes to /etc/resolv.conf.

    This test can be configured using the Hostname and Canonical Name Health
    Check host configuration setting.




    On Tue, Apr 29, 2014 at 6:01 AM, David Montgomery <
    [email protected]> wrote:
    How does one deal this? All nodes are deamed not healthy. From
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/cdh4ig_topic_11_1.html

    I mean..I set my /etc/hosts and /etc/hostname they way cloudera likes yet
    I get the below

    uname -a
    Linux manager-107170235192-sf-development.cloudera 3.8.0-29-generic
    #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64
    GNU/Linux

    hostname
    manager-107170235192-sf-development.cloudera

    hostname --fqdn
    manager-107170235192-sf-development.cloudera.test.com

    nano /etc/sysconfig/network
    EMPTY FILE

    host -v -t A `hostname`
    Trying "manager-107170235192-sf-development.cloudera"
    Received 137 bytes from 8.8.4.4#53 in 102 ms
    Trying "manager-107170235192-sf-development.cloudera"
    Host manager-107170235192-sf-development.cloudera not found: 3(NXDOMAIN)
    Received 137 bytes from 8.8.4.4#53 in 2 ms


    /sbin/ifconfig
    eth0 Link encap:Ethernet HWaddr 04:01:17:96:5d:01
    inet addr:107.170.235.192 Bcast:107.170.235.255
    Mask:255.255.255.0
    inet6 addr: fe80::601:17ff:fe96:5d01/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:943909 errors:0 dropped:0 overruns:0 frame:0
    TX packets:782040 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1504778185 (1.5 GB) TX bytes:3453248322 (3.4 GB)








    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Philip Langdale at Apr 29, 2014 at 6:42 pm ⇧
    Your /etc/hostname should provide the fqdn - that's the problem, i believe.
    As you see, DNS is failing to resolve the partial name.

    --phil

    On 28 April 2014 17:51, David Montgomery wrote:

    PPS

    I did the below. I un selected tge healt check and restart the agent. I
    have a green light now. Question..was that wise to have DNS Resolution
    Disabled?

    Thanks


    Monitoring Hostname and Canonical Name Health Check

    Reset to the default value: true

    Whether the hostname and canonical names for this host are consistent when
    checked from a Java process.


    On Tue, Apr 29, 2014 at 8:41 AM, David Montgomery <
    [email protected]> wrote:
    PS..here is my /etc/resolv.conf
    on ubujtu 12.04


    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
    resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 8.8.4.4
    nameserver 8.8.8.8
    nameserver 209.244.0.3



    Advice

    This is a host health test that checks that the host's hostname and
    canonical name are consistent when checked from a Java process.

    A failure of this health test may indicate that the host's DNS
    configuration is not correct. Check the Cloudera Manager Agent log for the
    names that were detected by this test.

    The hostname and canonical name are considered to be consistent if the
    hostname or the hostname plus a domain name is the same as the canonical
    name. This health test uses domain names from the domain and search lines
    in /etc/resolv.conf. This health test does not consult /etc/nsswitch.conf
    and may give incorrect results if /etc/resolv.conf is not used by the host.
    There may be a delay of up to 5 minutes before this health test picks up
    changes to /etc/resolv.conf.

    This test can be configured using the Hostname and Canonical Name Health
    Check host configuration setting.




    On Tue, Apr 29, 2014 at 6:01 AM, David Montgomery <
    [email protected]> wrote:
    How does one deal this? All nodes are deamed not healthy. From
    http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/cdh4ig_topic_11_1.html

    I mean..I set my /etc/hosts and /etc/hostname they way cloudera likes
    yet I get the below

    uname -a
    Linux manager-107170235192-sf-development.cloudera 3.8.0-29-generic
    #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64
    GNU/Linux

    hostname
    manager-107170235192-sf-development.cloudera

    hostname --fqdn
    manager-107170235192-sf-development.cloudera.test.com

    nano /etc/sysconfig/network
    EMPTY FILE

    host -v -t A `hostname`
    Trying "manager-107170235192-sf-development.cloudera"
    Received 137 bytes from 8.8.4.4#53 in 102 ms
    Trying "manager-107170235192-sf-development.cloudera"
    Host manager-107170235192-sf-development.cloudera not found: 3(NXDOMAIN)
    Received 137 bytes from 8.8.4.4#53 in 2 ms


    /sbin/ifconfig
    eth0 Link encap:Ethernet HWaddr 04:01:17:96:5d:01
    inet addr:107.170.235.192 Bcast:107.170.235.255
    Mask:255.255.255.0
    inet6 addr: fe80::601:17ff:fe96:5d01/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:943909 errors:0 dropped:0 overruns:0 frame:0
    TX packets:782040 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1504778185 (1.5 GB) TX bytes:3453248322 (3.4 GB)








    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedApr 28, '14 at 10:01p
activeApr 29, '14 at 6:42p
posts4
users2
websitecloudera.com
irc#hadoop

2 users in discussion

David Montgomery: 3 posts Philip Langdale: 1 post

Content

People

Support

Translate

site design / logo © 2023 Grokbase