Skip to content
October 2, 2013 / binidas

Running cloudera centOS and list of issues encountered

I downloaded full blown standard edition of Cloudera to install on 64-bit server CentOS 6.4. Installation of components was pretty straight forward than the vanilla Hadoop ecosystem thanks to cloudera manager that makes so easy to install each component.

However i must say it wasnt a one click installation of cloudera cluster,  had to tweak few configurations to get it working. Below are the issues i encountered so far and resolved.

1. Open ports as given below, else installation will error out.

[root@localhost ~]# vi /etc/sysconfig/iptables
-A INPUT -m state –state NEW -m tcp -p tcp –dport 7180 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 7182 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 7183 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 7184 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 7432 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 9000 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 9001 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 8888 -j ACCEPT


[root@localhost ~]# /etc/init.d/iptables restart

iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: [ OK ]
iptables: Loading additional modules: nf_conntrack_ftp [ OK ]
2. WARNING hostname localhost.localdomain differs from the canonical name localhost

Verify host name it resolves to “host -v -t A `hostname`”

Edit hostname mapping in /etc/sysconfig/network. Change localhost.localdomain to localhost or your domain name.

/etc/init.d/network restart
Hue currently requires that the machines within your cluster can connect to each other freely over TCP. The machines outside your cluster must be able to open TCP port 8888 on the Hue Server (or the configured Hue web HTTP port) to interact with the system.

3. Monitoring service donot work, errors out: Could not find a HOST_MONITORING nozzle from SCM
Sol: Re-run cloudera manager upgrade wizard as given in

4. Oozie monitoring webui not working – http://masternode:11000/oozie/
As per instruction ext-2.2 must be extracted /var/lib/oozie/libext (

But it did not work, its because symbolic on the deployed oozie-server pointed to different path /var/lib/oozie/ext-2.2, so make sure to unzip ext-2.2 files to this location.

/opt/cloudera/parcels/CDH-4.4.0-1.cdh4.4.0.p0.39/lib/oozie/oozie-server/webapps/oozie/ext-2.2 -> /var/lib/oozie/ext-2.2


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: