FAQ
Hi All,

Can anyone tell me how to disable ipv6 for Cloudera Manager 4?

I am getting this error each time a cloudera-scm-agent tries to send a
heart beat to cloudera-scm-server.

[24/Jul/2012 16:23:33 +0000] 30594 MonitorDaemon throttling_logger ERROR
File '/proc/net/tcp6' couldn't be opened
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/src/cmf/monitor/host/tcp_metrics_utils.py",
line 52, in add_tcp_metrics
proc_tcp_file = open(proc_file_name)
IOError: [Errno 2] No such file or directory: '/proc/net/tcp6'
[24/Jul/2012 16:23:33 +0000] 30594 MainThread agent ERROR Caught
unexpected exception in main loop.
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 310, in start
timed_heartbeat_response = self.send_heartbeat(heartbeat)
File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 581, in send_heartbeat
self.log_heartbeat_exception("Heartbeating to %s:%s failed." %
(self.master_host, self.master_port))
AttributeError: 'Agent' object has no attribute 'master_port'


Thanks
Sambit.

Search Discussions

  • Philip Zeyliger at Jul 24, 2012 at 3:50 pm
    Hi Sambit,

    The ipv6 error is not the root cause: that's some monitoring code that
    spams the logs a bit. We've fixed that in house for future releases, but
    it's not your underlying problem.

    What's your configuration (/etc/cloudera-scm-agent/config.ini) say? It
    looks like the master host/port aren't configured.

    -- Philip
    On Tue, Jul 24, 2012 at 4:04 AM, Sambit Tripathy wrote:

    Hi All,

    Can anyone tell me how to disable ipv6 for Cloudera Manager 4?

    I am getting this error each time a cloudera-scm-agent tries to send a
    heart beat to cloudera-scm-server.

    [24/Jul/2012 16:23:33 +0000] 30594 MonitorDaemon throttling_logger ERROR
    File '/proc/net/tcp6' couldn't be opened
    Traceback (most recent call last):
    File "/usr/lib64/cmf/agent/src/cmf/monitor/host/tcp_metrics_utils.py",
    line 52, in add_tcp_metrics
    proc_tcp_file = open(proc_file_name)
    IOError: [Errno 2] No such file or directory: '/proc/net/tcp6'
    [24/Jul/2012 16:23:33 +0000] 30594 MainThread agent ERROR Caught
    unexpected exception in main loop.
    Traceback (most recent call last):
    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 310, in start
    timed_heartbeat_response = self.send_heartbeat(heartbeat)
    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 581, in send_heartbeat
    self.log_heartbeat_exception("Heartbeating to %s:%s failed." %
    (self.master_host, self.master_port))
    AttributeError: 'Agent' object has no attribute 'master_port'


    Thanks
    Sambit.
  • Sambit Tripathy at Jul 25, 2012 at 6:52 pm
    Finally managed to fix it for my cluster.

    I was doing this installation using a local yum repo and have downloaded
    the rpms manually and put inside the repo, it was the older versions of the
    rpms which I downloaded was behind this issue which had this ipv6 issue.

    Upgraded the following rpms in my repo :

    from

    cloudera-manager-agent-4.0.2-1.cm402.p0.26.x86_64.rpm
    cloudera-manager-daemons-4.0.2-1.cm402.p0.26.x86_64.rpm
    cloudera-manager-server-4.0.2-1.cm402.p0.26.x86_64.rpm
    enterprise-debuginfo-4.0.2-1.cm402.p0.26.x86_64.rpm

    to

    cloudera-manager-agent-4.0.3-1.cm403.p0.50.x86_64.rpm
    cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm
    cloudera-manager-server-4.0.3-1.cm403.p0.50.x86_64.rpm
    cloudera-manager-server-db-4.0.3-1.cm403.p0.50.x86_64.rpm
    enterprise-debuginfo-4.0.3-1.cm403.p0.50.x86_64.rpm


    The error message "File '/proc/net/tcp6' couldn't be opened" still comes in
    the log, nothing to worry about that but all the hosts are displayed
    correctly under managed hosts panel.

    Thanks
    Sambit.

    On Tue, Jul 24, 2012 at 9:20 PM, Philip Zeyliger wrote:

    Hi Sambit,

    The ipv6 error is not the root cause: that's some monitoring code that
    spams the logs a bit. We've fixed that in house for future releases, but
    it's not your underlying problem.

    What's your configuration (/etc/cloudera-scm-agent/config.ini) say? It
    looks like the master host/port aren't configured.

    -- Philip
    On Tue, Jul 24, 2012 at 4:04 AM, Sambit Tripathy wrote:

    Hi All,

    Can anyone tell me how to disable ipv6 for Cloudera Manager 4?

    I am getting this error each time a cloudera-scm-agent tries to send a
    heart beat to cloudera-scm-server.

    [24/Jul/2012 16:23:33 +0000] 30594 MonitorDaemon throttling_logger ERROR
    File '/proc/net/tcp6' couldn't be opened
    Traceback (most recent call last):
    File "/usr/lib64/cmf/agent/src/cmf/monitor/host/tcp_metrics_utils.py",
    line 52, in add_tcp_metrics
    proc_tcp_file = open(proc_file_name)
    IOError: [Errno 2] No such file or directory: '/proc/net/tcp6'
    [24/Jul/2012 16:23:33 +0000] 30594 MainThread agent ERROR
    Caught unexpected exception in main loop.
    Traceback (most recent call last):
    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 310, in start
    timed_heartbeat_response = self.send_heartbeat(heartbeat)
    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 581, in
    send_heartbeat
    self.log_heartbeat_exception("Heartbeating to %s:%s failed." %
    (self.master_host, self.master_port))
    AttributeError: 'Agent' object has no attribute 'master_port'


    Thanks
    Sambit.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJul 24, '12 at 11:04a
activeJul 25, '12 at 6:52p
posts3
users2
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase