FAQ
The agent is having trouble figuring out its own hostname. Can you post the
output of hostname -f and your /etc/hosts file?

-Joey
On Tuesday, December 4, 2012, James Chang wrote:

Dear Joey,

Following is the log you want, thanks for your kindly help.

===================================================================================================
[root@HadoopCDH4 cloudera-scm-agent]# cat cloudera-scm-agent.out
/usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha
module is deprecated; use the hashlib module instead
import sha
/usr/lib64/cmf/agent/src/cmf/monitor/host/network_interfaces.py:11:
DeprecationWarning: the sets module is deprecated
from sets import Set
[03/Dec/2012 17:52:48 +0000] 10992 MainThread agent ERROR Could
not determine hostname or ip address; proceeding.
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1204, in
parse_arguments
ip_address = socket.gethostbyname(fqdn)
gaierror: [Errno -2] Name or service not known
usage: agent.py [-h] [--agent_dir AGENT_DIR]
[--agent_httpd_port AGENT_HTTPD_PORT] --package_dir
PACKAGE_DIR [--supervisord_path SUPERVISORD_PATH]
[--supervisord_httpd_port SUPERVISORD_HTTPD_PORT]
[--standalone STANDALONE] [--master MASTER]
[--environment ENVIRONMENT] [--host_id HOST_ID]
[--disable_supervisord_events] [--disable_eager_heartbeats]
--hostname HOSTNAME --ip_address IP_ADDRESS [--use_tls]
[--client_key_file CLIENT_KEY_FILE]
[--client_cert_file CLIENT_CERT_FILE]
[--verify_cert_file VERIFY_CERT_FILE]
[--client_keypw_file CLIENT_KEYPW_FILE] [--logfile LOGFILE]
[--optional_token] [--clear_agent_dir]
agent.py: error: argument --hostname is required
[03/Dec/2012 17:52:48 +0000] 10992 Dummy-1 agent INFO Stopping
agent...

===================================================================================================

Cheers,
James Chang

2012/12/4 Joey Echeverria <joey@cloudera.com>

+scm-users@

Moving this to scm-users@cloudera.org which is the right list for
Cloudera Manager issues.

Can you send a link to your agent log file (it should be in
/var/log/cloudera-scm-agent). That will give us a better idea why the agent
couldn't start.

-Joey


On Mon, Dec 3, 2012 at 5:37 AM, James Chang wrote:

Hi,

I try to use Cloudera Manager 4.1 Free Edition to install CDH
as pseudo-distribution mode but it failed!

Following are the error log and my environment, could anyone give me a
hand?

1.OS:CentOS 6.3 X64 Version
2.JDK:Oracle JDK 1.6.0_37 X64 Version
3.Cloudera Manager 4.1 Free Edition
[root@HadoopCDH4 work]# rpm -qa|grep cloudera
cloudera-manager-repository-4.0-1.noarch
cloudera-manager-server-db-4.1.1-1.cm411.p0.388.x86_64
cloudera-manager-daemons-4.1.1-1.cm411.p0.388.x86_64
cloudera-manager-server-4.1.1-1.cm411.p0.388.x86_64
4.Full Log:
=============================


Failed to start Cloudera Manager Agent. (Failed Step)
Uninstalled. (Current Step) Last Refreshed: Dec 3, 2012 6:30:29 PM CST
/tmp/scm_prepare_node.R0VmeIQN
using SSH_CLIENT to get the SCM hostname: 10.1.112.131 49478 22
opening logging file descriptor
Starting installation script... Acquiring installation lock...
*BEGIN flock 4 *
*END (0) *
Detecting root privileges...
effective UID is 0
Detecting distribution...
*BEGIN grep Tikanga /etc/redhat-release *
*END (1) *
*BEGIN grep 'CentOS release 5' /etc/redhat-release *
*END (1) *
*BEGIN grep Santiago /etc/redhat-release *
*END (1) *
*BEGIN grep 'CentOS Linux release 6' /etc/redhat-release *
*END (1) *
*BEGIN grep 'CentOS release 6' /etc/redhat-release *
CentOS release 6.3 (Final)
*END (0) *
/etc/redhat-release ==> CentOS 6
Detecting Cloudera Manager Server...
*BEGIN host -t PTR 10.1.112.131 *
Host 131.112.1.10.in-addr.arpa. not found: 3(NXDOMAIN)
*END (1) *
*BEGIN ping -c 1 10.1.112.131 *
PING 10.1.112.131 (10.1.112.131) 56(84) bytes of data.
64 bytes from 10.1.1 <http://10.1.112.131>
--
Joey Echeverria
Principal Solutions Architect
Cloudera, Inc.

Search Discussions

  • Philip Zeyliger at Dec 5, 2012 at 2:53 pm
    I typically use the following to diagnose such issues. This is pretty much
    what the agent does.

    $python -c 'import socket; print socket.getfqdn(),
    socket.gethostbyname(socket.getfqdn())'

    On Wed, Dec 5, 2012 at 2:04 AM, Joey Echeverria wrote:

    The agent is having trouble figuring out its own hostname. Can you post
    the output of hostname -f and your /etc/hosts file?

    -Joey
    On Tuesday, December 4, 2012, James Chang wrote:

    Dear Joey,

    Following is the log you want, thanks for your kindly help.

    ===================================================================================================
    [root@HadoopCDH4 cloudera-scm-agent]# cat cloudera-scm-agent.out
    /usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha
    module is deprecated; use the hashlib module instead
    import sha
    /usr/lib64/cmf/agent/src/cmf/monitor/host/network_interfaces.py:11:
    DeprecationWarning: the sets module is deprecated
    from sets import Set
    [03/Dec/2012 17:52:48 +0000] 10992 MainThread agent ERROR Could
    not determine hostname or ip address; proceeding.
    Traceback (most recent call last):
    File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1204, in
    parse_arguments
    ip_address = socket.gethostbyname(fqdn)
    gaierror: [Errno -2] Name or service not known
    usage: agent.py [-h] [--agent_dir AGENT_DIR]
    [--agent_httpd_port AGENT_HTTPD_PORT] --package_dir
    PACKAGE_DIR [--supervisord_path SUPERVISORD_PATH]
    [--supervisord_httpd_port SUPERVISORD_HTTPD_PORT]
    [--standalone STANDALONE] [--master MASTER]
    [--environment ENVIRONMENT] [--host_id HOST_ID]
    [--disable_supervisord_events]
    [--disable_eager_heartbeats]
    --hostname HOSTNAME --ip_address IP_ADDRESS [--use_tls]
    [--client_key_file CLIENT_KEY_FILE]
    [--client_cert_file CLIENT_CERT_FILE]
    [--verify_cert_file VERIFY_CERT_FILE]
    [--client_keypw_file CLIENT_KEYPW_FILE] [--logfile
    LOGFILE]
    [--optional_token] [--clear_agent_dir]
    agent.py: error: argument --hostname is required
    [03/Dec/2012 17:52:48 +0000] 10992 Dummy-1 agent INFO Stopping
    agent...

    ===================================================================================================

    Cheers,
    James Chang


    2012/12/4 Joey Echeverria <joey@cloudera.com>

    +scm-users@

    Moving this to scm-users@cloudera.org which is the right list for
    Cloudera Manager issues.

    Can you send a link to your agent log file (it should be in
    /var/log/cloudera-scm-agent). That will give us a better idea why the agent
    couldn't start.

    -Joey


    On Mon, Dec 3, 2012 at 5:37 AM, James Chang wrote:

    Hi,

    I try to use Cloudera Manager 4.1 Free Edition to install CDH
    as pseudo-distribution mode but it failed!

    Following are the error log and my environment, could anyone give me a
    hand?

    1.OS:CentOS 6.3 X64 Version
    2.JDK:Oracle JDK 1.6.0_37 X64 Version
    3.Cloudera Manager 4.1 Free Edition
    [root@HadoopCDH4 work]# rpm -qa|grep cloudera
    cloudera-manager-repository-4.0-1.noarch
    cloudera-manager-server-db-4.1.1-1.cm411.p0.388.x86_64
    cloudera-manager-daemons-4.1.1-1.cm411.p0.388.x86_64
    cloudera-manager-server-4.1.1-1.cm411.p0.388.x86_64
    4.Full Log:
    =============================


    Failed to start Cloudera Manager Agent. (Failed Step)
    Uninstalled. (Current Step) Last Refreshed: Dec 3, 2012 6:30:29 PM CST
    /tmp/scm_prepare_node.R0VmeIQN
    using SSH_CLIENT to get the SCM hostname: 10.1.112.131 49478 22
    opening logging file descriptor
    Starting installation script... Acquiring installation lock...
    *BEGIN flock 4 *
    *END (0) *
    Detecting root privileges...
    effective UID is 0
    Detecting distribution...
    *BEGIN grep Tikanga /etc/redhat-release *
    *END (1) *
    *BEGIN grep 'CentOS release 5' /etc/redhat-release *
    *END (1) *
    *BEGIN grep Santiago /etc/redhat-release *
    *END (1) *
    *BEGIN grep 'CentOS Linux release 6' /etc/redhat-release *
    *END (1) *
    *BEGIN grep 'CentOS release 6' /etc/redhat-release *
    CentOS release 6.3 (Final)
    *END (0) *
    /etc/redhat-release ==> CentOS 6
    Detecting Cloudera Manager Server...
    *BEGIN host -t PTR 10.1.112.131 *
    Host 131.112.1.10.in-addr.arpa. not found: 3(NXDOMAIN)
    *END (1) *
    *BEGIN ping -c 1 10.1.112.131 *
    PING 10.1.112.131 (10.1.112.131) 56(84) bytes of data.
    64 bytes from 10.1.1 <http://10.1.112.131>
    --
    Joey Echeverria
    Principal Solutions Architect
    Cloudera, Inc.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedDec 5, '12 at 10:04a
activeDec 5, '12 at 2:53p
posts2
users2
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase