Support Questions

Find answers, ask questions, and share your expertise

CDH 5.8.1 Sqoop2 Starting Problem

avatar
Explorer

Hello,

 

I'm currently installing CDH 5.8.1 on a Centos Environement with one name node and 2 data nodes.

 

The install was made using packages because the P2P ports where blocked. The install of HDFS, Zookeeper, Map Reduce, Hue, Hive went very well but I have a problem to install Sqoop2 using the Cloudera manager, we have the error below during the start of the server - log from stderr. The user cloudera-scm has the same access as root to all files.

 

How can we resolve the problem ? 

 

Thank you

+ mkdir -p /var/run/cloudera-scm-agent/process/290-sqoop-SQOOP_SERVER/temp
+ EXT_LIBS_DIR=/var/lib/sqoop2
+ cp /usr/share/java/mysql-connector-java.jar /var/lib/sqoop2
+ cp /usr/share/cmf/lib/postgresql-9.0-801.jdbc4.jar /var/lib/sqoop2
+ cp /usr/share/java/oracle-connector-java.jar /var/lib/sqoop2
+ '[' '' == upgrade -o '' == create-database ']'
+ exec /usr/lib/bigtop-tomcat/bin/catalina.sh run
aot 11, 2016 10:43:02 AM org.apache.catalina.startup.Catalina load
AVERTISSEMENT: Can't load server.xml from /var/lib/sqoop2/tomcat-deployment/conf/server.xml
aot 11, 2016 10:43:02 AM org.apache.catalina.startup.Catalina load
AVERTISSEMENT: Can't load server.xml from /var/lib/sqoop2/tomcat-deployment/conf/server.xml
aot 11, 2016 10:43:02 AM org.apache.catalina.startup.Catalina start
GRAVE: Cannot start server. Server instance is not configured.

 

1 ACCEPTED SOLUTION

avatar
Explorer

We finally found a solution for the problem, 

 1- We added the site.xml file with all the parameters under /var/lib/sqoop2/tomcat-deployment/conf/

 2- We medified Tomcat-deployment.sh so the system will not delete and recreate a new conf directory

 

This solved the problem and Sqoop2 is now up and running

View solution in original post

1 REPLY 1

avatar
Explorer

We finally found a solution for the problem, 

 1- We added the site.xml file with all the parameters under /var/lib/sqoop2/tomcat-deployment/conf/

 2- We medified Tomcat-deployment.sh so the system will not delete and recreate a new conf directory

 

This solved the problem and Sqoop2 is now up and running