CDH installation errors highlights

 

 

CDH errors that occur during installation

1, iptables: / sbin / iptables absence

I mistakenly deleted because the / sbin / under document deleted. 
Solution: yum install iptables

2、com.mysql.jdbc.execptions.jdbc4.CommunicationsException:Communication link failure

MySQL connection driver package can not be found. 
Solution: mysql-connector-java-5.1.31 -bin.jar the package needs to be copied to the /opt/cm-5.4.3/share/cmf/lib

3, the installation fails, the detection signal is not received Agent emitted.

• Check the host name wrong, see / etc / hosts configuration and under / etc / sysconfig / network are the same
• Turn off the firewall service iptables stop
• Start Httpd service service httpd start

4, reloading HDFS error

Error: Connecting NameNode name of the directory is empty, all in empty formatted HDFS 
solution: namenode and needs to be performed on all datanode rm -rf /def

5, reloading oozie error

Error: DB schema exists java.lang.Exception: DB  schema exists
Solution: rm -rf / var / lib / oozie / *

6, reloading Hive error

Error: Connection Error Database 
Solution: - initializing the database CM 
execution /opt/cm-5.4.3/share/cmf/schema/scm_prepare_database.sh mysql cm -hcdh1 -uroot -pxxxx -scm- host cdh1 scm scm scm primary node 
Error: Hive the Create the User Directory 
Failed to the Execute the Command Hive the Create the User Directory Service ON Hive 
solution: restart YARN HDFS and after installation.

7, the database is not connected

Connect to ON to Database Unable Host 'XXXX2' from Host 'xxxx1' 
Mysql storing metadata, and therefore must be connected to the node from MySQL server configuration. 
Solution: MySQL in its command line input All privileges ON Grant  .  To 'root' @ 'XXXX2' IDENTIFIED by 'password' with the Option Grant; 
flush privileges;

8, the server build is successful, the command can not be used

-bash: hdfs: command not found 
Solution: delete the file / var / lib / alternatives under, and then restart the service,service cloudera-scm-agent

9, not connected HDFS

No FileSystem for scheme 
Solution: stop so service on the web page, and then delete HDFS and then rm -rf /dfs re-add the HDFS service.

10, Agent service failed to start

cloudera-scm-agent dead but pid  file exists
Workaround: Delete the  /var/run/cloudera-scm-agent.pidfile. 
ps -aux to see the process related to the city after killing restart the service.