Oozie时bin/oozied.sh start或bin/oozied.sh run出现Bootstrap进程无法启动，http://bigdatamaster:11000/oozie界面也无法打开？E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.ser

　　不多说，直接上干货！

　　问题详情

[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ bin/oozied.sh start
 
Setting OOZIE_HOME:          /home/hadoop/app/oozie-4.1.-cdh5.5.4
Setting OOZIE_CONFIG:        /home/hadoop/app/oozie-4.1.-cdh5.5.4/conf
Sourcing:                    /home/hadoop/app/oozie-4.1.-cdh5.5.4/conf/oozie-env.sh
  setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m"
  setting OOZIE_CONF=${OOZIE_HOME}/conf
  setting OOZIE_DATA=${OOZIE_HOME}/data
  setting OOZIE_LOG=${OOZIE_HOME}/logs
  setting CATALINA_BASE=${OOZIE_HOME}/oozie-server
  setting CATALINA_TMPDIR=${OOZIE_HOME}/oozie-server/temp
  setting CATALINA_OUT=${OOZIE_LOG}/catalina.out
Setting OOZIE_CONFIG_FILE:   oozie-site.xml
Using   OOZIE_DATA:          /home/hadoop/app/oozie-4.1.-cdh5.5.4/data
Using   OOZIE_LOG:           /home/hadoop/app/oozie-4.1.-cdh5.5.4/logs
Setting OOZIE_LOG4J_FILE:    oozie-log4j.properties
Setting OOZIE_LOG4J_RELOAD:
Setting OOZIE_HTTP_HOSTNAME: bigdatamaster
Setting OOZIE_HTTP_PORT:
Setting OOZIE_ADMIN_PORT:
Setting OOZIE_HTTPS_PORT:
Setting OOZIE_BASE_URL:      http://bigdatamaster:11000/oozie
Using   CATALINA_BASE:       /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server
Setting OOZIE_HTTPS_KEYSTORE_FILE:     /home/hadoop/.keystore
Setting OOZIE_HTTPS_KEYSTORE_PASS:     password
Setting OOZIE_INSTANCE_ID:       bigdatamaster
Using   CATALINA_OUT:        /home/hadoop/app/oozie-4.1.-cdh5.5.4/logs/catalina.out
Setting CATALINA_PID:        /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server/temp/oozie.pid
 
Using   CATALINA_OPTS:        -Xmx1024m -Dderby.stream.error.file=/home/hadoop/app/oozie-4.1.-cdh5.5.4/logs/derby.log
Adding to CATALINA_OPTS:     -Doozie.home.dir=/home/hadoop/app/oozie-4.1.-cdh5.5.4 -Doozie.config.dir=/home/hadoop/app/oozie-4.1.-cdh5.5.4/conf -Doozie.log.dir=/home/hadoop/app/oozie-4.1.-cdh5.5.4/logs -Doozie.data.dir=/home/hadoop/app/oozie-4.1.-cdh5.5.4/data -Doozie.instance.id=bigdatamaster -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload= -Doozie.http.hostname=bigdatamaster -Doozie.admin.port= -Doozie.http.port= -Doozie.https.port= -Doozie.base.url=http://bigdatamaster:11000/oozie -Doozie.https
.keystore.file=/home/hadoop/.keystore -Doozie.https.keystore.pass=password -Djava.library.path=
 
Using CATALINA_BASE:   /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server
Using CATALINA_HOME:   /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server
Using CATALINA_TMPDIR: /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server/temp
Using JRE_HOME:        /home/hadoop/app/jdk
Using CLASSPATH:       /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server/bin/bootstrap.jar
Using CATALINA_PID:    /home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server/temp/oozie.pid
Existing PID file found during start.
Removing/clearing stale PID file.
[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ 

　　查看日志

-- ::,  INFO XLogService: - SERVER[bigdatamaster] Log4j configuration file [oozie-log4j.properties]
-- ::,  INFO XLogService: - SERVER[bigdatamaster] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.-cdh5.5.4/conf]
-- ::,  INFO XLogService: - SERVER[bigdatamaster] Log4j reload interval [ sec]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Oozie home dir  [/home/hadoop/app/oozie-4.1.-cdh5.5.4]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Oozie conf dir  [/home/hadoop/app/oozie-4.1.-cdh5.5.4/conf]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Oozie conf file [oozie-site.xml]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Configuration change via System Property, [oozie.base.url]=[http://bigdatamaster:11000/oozie]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Configuration change via System Property, [oozie.http.hostname]=[bigdatamaster]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Configuration change via System Property, [oozie.http.port]=[]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Configuration change via System Property, [oozie.instance.id]=[bigdatamaster]
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] System property [oozie.https.keystore.pass] no defined in Oozie configuration, ignored
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] System property [oozie.admin.port] no defined in Oozie configuration, ignored
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] System property [oozie.https.port] no defined in Oozie configuration, ignored
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] System property [oozie.https.keystore.file] no defined in Oozie configuration, ignored
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.hostname], Value [bigdatamaster]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.instance.id], Value [bigdatamaster]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.port], Value []
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.hosts]
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.groups]
-- ::,  WARN Services: - SERVER[bigdatamaster] System ID [oozie-hado] exceeds maximum length [], trimming
-- ::,  INFO Services: - SERVER[bigdatamaster] Exiting null Entering NORMAL
-- ::,  INFO Services: - SERVER[bigdatamaster] Initialized runtime directory [/home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server/temp/oozie-hado4767423416871899036.dir]
-- ::, FATAL Services: - SERVER[bigdatamaster] Runtime Exception during Services Load. Check your list of 'oozie.services' or 'oozie.services.ext'
-- ::, FATAL Services: - SERVER[bigdatamaster] E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
org.apache.oozie.service.ServiceException: E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
    at org.apache.oozie.service.Services.loadServices(Services.java:)
    at org.apache.oozie.service.Services.init(Services.java:)
    at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:)
    at org.apache.catalina.core.StandardService.start(StandardService.java:)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:)
    at java.lang.reflect.Method.invoke(Method.java:)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:)
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
    at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:)
    at org.apache.oozie.service.ConfigurationService$LogChangesConfiguration.getClasses(ConfigurationService.java:)
    at org.apache.oozie.service.ConfigurationService.getClasses(ConfigurationService.java:)
    at org.apache.oozie.service.Services.loadServices(Services.java:)
    ...  more
Caused by: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
    at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:)
    at org.apache.oozie.util.XConfiguration.getClassByName(XConfiguration.java:)
    at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:)
    ...  more
[hadoop@bigdatamaster logs]$ 

解决办法

http://community.cloudera.com/t5/Cloudera-Manager-Installation/Oozie-startup-failure-ERROR-XSDB6/td-p/11584

　　查看

[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ ps aux | grep oozie
hadoop      0.0  0.0     pts/    S+   :   : grep oozie
[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ 

[hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$ ps aux | grep oozie|grep -v grep
[hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$

　　说明oozie没进程启动 

 

 

　　然后

Its likely that another instance of Oozie may be running on the machine already thats causing this. You can first check for such an instance via a "ps aux | grep oozie" command perhaps, and kill it if one is indeed running.

If there's no other instance, then its likely that the OOME caused crash/kill has left the DB lock under the derby directory, causing the further startups to fail as it now thinks the DB is in use (Derby DB supports only 1 max. current user, which is why we strongly discourage its use in your clusters - consider moving off of Derby when you get a chance).

To resolve that, run: rm /var/lib/oozie/data/*.lck

After this, start up the Oozie server again, and it should come up now.

Once again: Consider changing the default DB of Oozie to MySQL/etc. instead of Derby. You'll avoid a lot of other pains that will come later if you continue to use it.

Backline Customer Operations Enginee

 

 

 

 

　　如果上述的步骤，还是没解决的话，则

　　1、进入cd $OOZIE_HOME

　　2、将Oozie停止运行./bin/oozie-stop.sh

     3、重新进行打包war包 ./bin/oozie-setup.sh prepare-war

     4、 重新打开Oozie：./bin/oozie-start.sh

 

 

 

 

 

 

　　最后

[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ jps
 Bootstrap
 NameNode
 SecondaryNameNode
 Jps
 QuorumPeerMain
 ResourceManager
[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ 

 

-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] System property [oozie.https.keystore.file] no defined in Oozie configuration, ignored
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.hostname], Value [bigdatamaster]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.instance.id], Value [bigdatamaster]
-- ::,  INFO ConfigurationService: - SERVER[bigdatamaster] Overriding configuration with system property. Key [oozie.http.port], Value []
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] Invalid configuration defined, [oozie.use.system.libpath]
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.hosts]
-- ::,  WARN ConfigurationService: - SERVER[bigdatamaster] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hadoop.groups]
-- ::,  WARN Services: - SERVER[bigdatamaster] System ID [oozie-hado] exceeds maximum length [], trimming
-- ::,  INFO Services: - SERVER[bigdatamaster] Exiting null Entering NORMAL
-- ::,  INFO Services: - SERVER[bigdatamaster] Initialized runtime directory [/home/hadoop/app/oozie-4.1.-cdh5.5.4/oozie-server/temp/oozie-hado2668923471340073361.dir]
-- ::, FATAL Services: - SERVER[bigdatamaster] Runtime Exception during Services Load. Check your list of 'oozie.services' or 'oozie.services.ext'
-- ::, FATAL Services: - SERVER[bigdatamaster] E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
org.apache.oozie.service.ServiceException: E0103: Could not load service classes, java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
    at org.apache.oozie.service.Services.loadServices(Services.java:)
    at org.apache.oozie.service.Services.init(Services.java:)
    at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:)
 
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:)
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
    at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:)
    at org.apache.oozie.service.ConfigurationService$LogChangesConfiguration.getClasses(ConfigurationService.java:)
    at org.apache.oozie.service.ConfigurationService.getClasses(ConfigurationService.java:)
    at org.apache.oozie.service.Services.loadServices(Services.java:)
    ...  more
Caused by: java.lang.ClassNotFoundException: Class org.apache.oozie.service.CoordinatorStoreService not found
    at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:)
    at org.apache.oozie.util.XConfiguration.getClassByName(XConfiguration.java:)
    at org.apache.hadoop.conf.Configuration.getClasses(Configuration.java:)
    ...  more
[hadoop@bigdatamaster logs]$ 

 

 

 　　后来，我又在网上查了下，说，试试，是否oozie在启动的时候，没有权限对oozie-server进行读写。

[hadoop@bigdatamaster oozie-4.1.-cdh5.5.4]$ chmod  oozie-server

　　然后，我又执行这条命令。

　　

 

　　同时，还看到网上说，在$OOZIE_HOME/libext目录下，解压ext-2.2.zip。

　　[hadoop@bigdatamaster libext]$ unzip ext-2.2.zip

     [hadoop@bigdatamaster libext]$ chmod -R 777 ext-2.2

 

 

 

 

 

 

 

 

 

 

 

 

然后呢，大家也许还会出现如下问题：

Oozie安装时放置Mysql驱动包的总结（网上最全）

Oozie时出现org.apache.oozie.service.ServiceException: E0103: Could not load service classes, Cannot load JDBC driver class 'com.mysql.jdbc.Driver'

Oozie时bin/oozied.sh start或bin/oozied.sh run出现Bootstrap进程无法启动，http://bigdatamaster:11000/oozie界面也无法打开？E0103: Could not load service classes,

java.lang.ClassNotFoundException: Class org.apache.oozie.ser

Oozie时bin/oozied.sh start或bin/oozied.sh run出现Bootstrap进程无法启动，http://bigdatamaster:11000/oozie界面也无法打开？

Oozie时出现Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure？

Oozie时出现Exception in thread "main" java.lang.UnsupportedClassVersionError: com/mysql/jdbc/Driver : Unsupported major.minor version 52.0？

CDH版本的oozie安装执行bin/oozie-setup.sh prepare-war，没生成oozie.war?