This is resolved. Possible Cause The main problem was the oozie not finding "/etc/tomcat/conf/ssl/server.xml". The oozie server has it own app-server; it should not therefore refer / conflict with the tomcat app server, which have deployed for our own purpose.
setting CATALINA_BASE=${CATALINA_BASE:-/usr/hdp/current/oozie-server/oozie-server}
setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat
It did however refer to /etc/tomcat. We had configurations settings at .bashrc, /etc/profile and /etc/init.d/tomcat re-Catalina Base and Catalina_Home. The oozie-setup.sh has references to Catalina_Base in many places. This may be the reason why it was referring to the wrong path. Solution: Code walk through on the shell files of oozie and other services, which did not start. Commented references to Catalina_Home and Catalina_Base in /etc/profile and etc/init/d/tomcat. Impact: All hadoop services have started Caution Users who may want to run Tomcat app server on the same server as Hadoop could create conflict if configurations for tomcat app server is set in the /etc/profile and etc/init.d/tomcat. The app server may either need to be run on a separate server than on the same server as oozie or enable user specific permission only through .bashrc.
... View more
