Oozie server failed to start with NoClassDefFoundError

kramakrishnan — Fri, 31 Mar 2017 02:51:39 GMT

Hi Team,

I am facing this issue while adding Oozie to an existing cluster, Oozie server start is failing with NoClassDefFoundError: org/apache/oozie/cli/CLIParser. Posting the stacktrace below. Kindly let me know how can I resolve this.

setting OOZIE_CONFIG=${OOZIE_CONFIG:-/usr/hdp/current/oozie-server/conf}
  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
  setting JAVA_HOME=/usr/jdk64/jdk1.8.0_60
  setting JRE_HOME=${JAVA_HOME}
  setting CATALINA_OPTS="$CATALINA_OPTS -Xmx2048m"
  setting OOZIE_LOG=/grid/0/log/oozie
  setting CATALINA_PID=/var/run/oozie/oozie.pid
  setting OOZIE_DATA=/grid/0/hadoop/oozie/data
  setting OOZIE_HTTP_PORT=11000
  setting OOZIE_ADMIN_PORT=11001
  setting JAVA_LIBRARY_PATH=/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64
  setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS} -Doozie.connection.retry.count=5 "
  setting OOZIE_CONFIG=${OOZIE_CONFIG:-/usr/hdp/current/oozie-server/conf}
  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
  setting JAVA_HOME=/usr/jdk64/jdk1.8.0_60
  setting JRE_HOME=${JAVA_HOME}
  setting CATALINA_OPTS="$CATALINA_OPTS -Xmx2048m"
  setting OOZIE_LOG=/grid/0/log/oozie
  setting CATALINA_PID=/var/run/oozie/oozie.pid
  setting OOZIE_DATA=/grid/0/hadoop/oozie/data
  setting OOZIE_HTTP_PORT=11000
  setting OOZIE_ADMIN_PORT=11001
  setting JAVA_LIBRARY_PATH=/usr/hdp/current/hadoop-client/lib/native/Linux-amd64-64
  setting OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS} -Doozie.connection.retry.count=5 "
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/oozie/cli/CLIParser
	at org.apache.oozie.tools.OozieSharelibCLI.run(OozieSharelibCLI.java:92)
	at org.apache.oozie.tools.OozieSharelibCLI.main(OozieSharelibCLI.java:67)
Caused by: java.lang.ClassNotFoundException: org.apache.oozie.cli.CLIParser
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 2 more

Thanks,

Kishor

Re: Oozie server failed to start with NoClassDefFoundError

vrathod — Fri, 31 Mar 2017 02:56:37 GMT

When Oozie server is starting , it is unable to find oozie-client-<version>.jar.

On my cluster I found it at /<HDP folder>/oozie-client-<version>.jar

That jar may have gotten deleted on your machine for some reason.

Please let me know if this helps. Thanks

Re: Oozie server failed to start with NoClassDefFoundError

kramakrishnan — Fri, 31 Mar 2017 04:07:15 GMT

Looks like we did some mistake while doing rpm cleanup. Copied oozie client jar to /usr/hdp/<version>/oozie/lib/ and it worked fine.

Thanks!

question Oozie server failed to start with NoClassDefFoundError in Archives of Support Questions (Read Only)

Oozie server failed to start with NoClassDefFoundError

Re: Oozie server failed to start with NoClassDefFoundError

Re: Oozie server failed to start with NoClassDefFoundError