Member since
11-06-2013
3
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
39082 | 11-06-2013 08:15 AM |
11-07-2013
06:08 AM
Hi Clint, [root@homer /]# hostname homer.larim.polymtl.ca [root@homer /]# cat /etc/sysconfig/network HOSTNAME=homer.larim.polymtl.ca NETWORKING=yes That's why I was confused with the problem because everything was resolving properly. Anyway, since I was using Centos, I installed Ubuntu in a virtual machine to see if I had the same problem. The installation completed successfully so I compared the Ubuntu /etc/hosts file with the CentOS one and noticed the difference for the localhost entries. I made the modification on all my Centos hosts and everything installed correctly...
... View more
11-06-2013
08:15 AM
1 Kudo
Ok I found the solution. I modified the hosts file for the following ( remove the FQDN for localhost 😞 127.0.0.1 localhost ::1 localhost6 132.207.67.11 homer.larim.polymtl.ca homer Edit: Removed an entry to avoid any confusion.
... View more
11-06-2013
07:09 AM
1 Kudo
Hello,
I'm doing a basic cluster installation using Cloudera Standard 4 on CentOS 6.3 64 and it does not work... Here is what I'm doing:
1. I run ./cloudera-manager-installer.bin and go to http://132.207.67.11:7180/ to continue the installation.
2. Then I follow the wizard and add the host 132.207.67.11 to the cluster installation.
3. The cluster installation on this host is successful but I find it strange that the IP is changed to 127.0.0.1.
4. But anyway, I continue and install the parcels.
5. And then at the hosts inspection I get this:
Cluster Installation
Inspect hosts for correctness Run Again
Validations
Inspector failed on the following hosts...
homer.larim.polymtl.ca: IOException thrown while collecting data from host: Connection refused
Inspector ran on 0 hosts.
The inspector failed to run on all hosts.
0 hosts are running CDH3 and 1 hosts are running CDH4.
All checked hosts are running the same version of components.
All managed hosts have consistent versions of Java.
All checked Cloudera Management Daemons versions are consistent with the server.
All checked Cloudera Management Agents versions are consistent with the server.
And from the log file cloudera-scm-agent.out
:
[06/Nov/2013 09:45:45 +0000] 21416 MainThread agent INFO SCM Agent Version: 4.7.3
[06/Nov/2013 09:45:45 +0000] 21416 MainThread agent INFO Using directory: /var/run/cloudera-scm-agent
[06/Nov/2013 09:45:45 +0000] 21416 MainThread agent INFO Using supervisor binary path: /usr/lib64/cmf/agent/src/cmf/../../build/env/bin/supervisord
[06/Nov/2013 09:45:45 +0000] 21416 MainThread agent WARNING Agent is running on 127.0.0.1 (localhost). This is a misconfiguration for multi-machine clusters. Check your hostname settings.
[06/Nov/2013 09:45:45 +0000] 21416 MainThread agent INFO Adding env vars that start with CMF_AGENT_
[06/Nov/2013 09:45:45 +0000] 21416 MainThread agent INFO Logging to /var/log/cloudera-scm-agent/cloudera-scm-agent.log
Why is it using 127.0.0.1. I'm always using FQDN name and the name resolution is made by DNS. Just the be sure, here is the content of my hosts file:
127.0.0.1 localhost.localdomain localhost
::1 homer.larim.polymtl.ca homer localhost6.localdomain6 localhost6
132.207.67.11 homer.larim.polymtl.ca homer
Anyway, I'm a bit baffled by the problem since I'm doing a vanilla installation with all the default value. Can anybody help me?
Thanks a lot...
... View more
Labels:
- Labels:
-
Cloudera Manager