Oozie时bin/oozied.sh start或bin/oozied.sh run出现Bootstrap进程无法启动,http://bigdatamaster:11000/oozie界面也无法打开?
不多说,直接上干货!
问题详情
按照官网
http://archive.cloudera.com/cdh5/cdh/5/oozie-4.1.0-cdh5.5.4/DG_QuickStart.html
Start Oozie as a daemon process run:
$ bin/oozied.sh start
To start Oozie as a foreground process run:
$ bin/oozied.sh run
Check the Oozie log file logs/oozie.log to ensure Oozie started properly.
Using the Oozie command line tool check the status of Oozie:
$ bin/oozie admin -oozie http://localhost:11000/oozie -status
Using a browser go to the Oozie web console , Oozie status should be NORMAL .
Refer to the Running the Examples document for details on running the examples.
[hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$ bin/oozied.sh start Setting OOZIE_HOME: /home/hadoop/app/oozie-4.1.0-cdh5.5.4 Setting OOZIE_CONFIG: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf Sourcing: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf/oozie-env.sh setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m" Setting OOZIE_CONFIG_FILE: oozie-site.xml Setting OOZIE_DATA: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/data Setting OOZIE_LOG: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs Setting OOZIE_LOG4J_FILE: oozie-log4j.properties Setting OOZIE_LOG4J_RELOAD: 10 Setting OOZIE_HTTP_HOSTNAME: bigdatamaster Setting OOZIE_HTTP_PORT: 11000 Setting OOZIE_ADMIN_PORT: 11001 Setting OOZIE_HTTPS_PORT: 11443 Setting OOZIE_BASE_URL: http://bigdatamaster:11000/oozie Using CATALINA_BASE: /home/hadoop/app/sqoop/server Setting OOZIE_HTTPS_KEYSTORE_FILE: /home/hadoop/.keystore Setting OOZIE_HTTPS_KEYSTORE_PASS: password Setting OOZIE_INSTANCE_ID: bigdatamaster Setting CATALINA_OUT: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs/catalina.out Setting CATALINA_PID: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie.pid Using CATALINA_OPTS: -Xmx1024m -Dderby.stream.error.file=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs/derby.log Adding to CATALINA_OPTS: -Doozie.home.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4 -Doozie.config.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf -Doozie.log.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs -Doozie.data.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/data -Doozie.instance.id=bigdatamaster -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10 -Doozie.http.hostname=bigdatamaster -Doozie.admin.port=11001 -Doozie.http.port=11000 -Doozie.https.port=11443 -Doozie.base.url=http://bigdatamaster:11000/oozie -Doozie.https.keystore.file=/home/hadoop/.keystore -Doozie.https.keystore.pass=password -Djava.library.path= WARN: Oozie WAR has not been set up at ''/home/hadoop/app/sqoop/server/webapps'', doing default set up setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m" no arguments given Usage : oozie-setup.sh <Command and OPTIONS> prepare-war [-d directory] [-secure] (-d identifies an alternative directory for processing jars -secure will configure the war file to use HTTPS (SSL)) sharelib create -fs FS_URI [-locallib SHARED_LIBRARY] (create sharelib for oozie, FS_URI is the fs.default.name for hdfs uri; SHARED_LIBRARY, path to the Oozie sharelib to install, it can be a tarball or an expanded version of it. If ommited, the Oozie sharelib tarball from the Oozie installation directory will be used) (action failes if sharelib is already installed in HDFS) sharelib upgrade -fs FS_URI [-locallib SHARED_LIBRARY] (upgrade existing sharelib, fails if there is no existing sharelib installed in HDFS) db create|upgrade|postupgrade -run [-sqlfile <FILE>] (create, upgrade or postupgrade oozie db with an optional sql File) (without options prints this usage information) EXTJS can be downloaded from http://www.extjs.com/learn/Ext_Version_Archives [hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$ jps 3543 ThriftServer 3101 QuorumPeerMain 3281 HMaster 8257 ResourceManager 14271 Jps 7918 NameNode 8075 SecondaryNameNode [hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$
[hadoop@bigdatamaster temp]$ cd /home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs [hadoop@bigdatamaster logs]$ ls oozie-audit.log oozie-instrumentation.log oozie-jpa.log oozie.log oozie-ops.log [hadoop@bigdatamaster logs]$ cat oozie.log 2017-05-08 19:29:39,215 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 19:29:39,228 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 19:29:39,229 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 19:29:39,230 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 19:29:39,645 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 19:29:39,646 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 19:29:39,647 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 19:29:40,737 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 19:29:40,738 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 19:29:40,817 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 19:29:40,828 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 19:29:40,830 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado485610280680465189.dir] 2017-05-08 19:29:40,830 INFO ConfigurationService:520 - SERVER[] Programmatic configuration change, property[oozie.services]=[org.apache.oozie.service.LiteWorkflowAppService, org.apache.oozie.service.HadoopAccessorService] 2017-05-08 19:29:40,838 INFO ConfigurationService:520 - SERVER[] Programmatic configuration change, property[oozie.services.ext]=[] 2017-05-08 19:29:40,938 INFO HadoopAccessorService:520 - SERVER[] JOB_TRACKER_WHITELIST :[], Total entries :0 2017-05-08 19:29:40,938 INFO HadoopAccessorService:520 - SERVER[] NAME_NODE_WHITELIST :[], Total entries :0 2017-05-08 19:29:40,939 INFO HadoopAccessorService:520 - SERVER[] Oozie Kerberos Authentication [disabled] 2017-05-08 19:29:43,237 WARN NativeCodeLoader:62 - SERVER[] Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 2017-05-08 19:29:44,909 INFO Services:520 - SERVER[] Initialized 2017-05-08 19:29:44,926 INFO Services:520 - SERVER[] Running with JARs for Hadoop version [2.6.0-cdh5.5.4] 2017-05-08 19:29:44,927 INFO Services:520 - SERVER[] Oozie System ID [oozie-hado] started! 2017-05-08 19:33:06,241 INFO Services:520 - SERVER[] Shutdown 2017-05-08 20:02:19,137 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:02:19,149 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:02:19,154 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:02:19,156 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:02:19,341 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:02:19,343 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:02:19,343 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:02:21,454 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:02:21,455 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:02:21,494 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:02:21,496 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:02:21,768 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado4006649374121962698.dir] 2017-05-08 20:09:55,897 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:09:55,912 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:09:55,912 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:09:55,913 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:09:56,017 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:09:56,020 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:09:56,021 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:09:57,188 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:09:57,189 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:09:57,201 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:09:57,203 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:09:57,230 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado7535278402080082342.dir] 2017-05-08 20:13:36,773 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:13:36,815 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:13:36,817 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:13:36,817 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:13:36,955 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:13:36,956 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:13:36,957 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:13:38,312 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:13:38,313 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:13:38,327 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:13:38,330 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:13:38,373 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado1884519945558517209.dir] 2017-05-08 20:14:04,322 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:14:04,331 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:14:04,331 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:14:04,332 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:14:04,452 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:14:04,454 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:14:04,454 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:14:05,669 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:14:05,671 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:14:05,690 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:14:05,694 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:14:05,730 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado6246788071058315044.dir] 2017-05-08 20:17:06,664 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:17:06,672 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:17:06,673 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:17:06,673 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:17:06,827 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:17:06,827 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:17:06,828 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:17:08,243 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:17:08,244 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:17:08,263 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:17:08,266 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:17:08,337 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado6985333808007161805.dir] 2017-05-08 20:17:38,275 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:17:38,284 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:17:38,285 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:17:38,285 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:17:38,373 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:17:38,374 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:17:38,374 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:17:41,143 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:17:41,146 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:17:41,180 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:17:41,189 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:17:41,436 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado8108581817801567279.dir] 2017-05-08 20:19:50,146 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:19:50,154 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:19:50,155 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:19:50,155 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:19:50,276 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:19:50,280 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:19:50,280 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:19:51,426 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:19:51,427 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:19:51,441 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:19:51,447 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:19:51,481 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado3493176773230629433.dir] 2017-05-08 20:20:39,080 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:20:39,094 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:20:39,094 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:20:39,095 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:20:39,235 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] 2017-05-08 20:20:39,235 INFO ConfigurationService:520 - SERVER[] Oozie conf dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:20:39,236 INFO ConfigurationService:520 - SERVER[] Oozie conf file [oozie-site.xml] 2017-05-08 20:20:40,482 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.hosts] 2017-05-08 20:20:40,483 WARN ConfigurationService:523 - SERVER[] Invalid configuration defined, [oozie.service.ProxyUserService.proxyuser.hue.groups] 2017-05-08 20:20:40,493 WARN Services:523 - SERVER[] System ID [oozie-hado] exceeds maximum length [10], trimming 2017-05-08 20:20:40,495 INFO Services:520 - SERVER[] Exiting null Entering NORMAL 2017-05-08 20:20:40,524 INFO Services:520 - SERVER[] Initialized runtime directory [/tmp/oozie-hado4464733353977573624.dir] 2017-05-08 20:37:51,989 INFO XLogService:520 - SERVER[] ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [4.1.0-cdh5.5.4] compiled by [jenkins] on [2016.04.25-18:14:19GMT] STARTUP MSG: revision [unavailable]@[unavailable] ******************************************************************************* 2017-05-08 20:37:52,001 INFO XLogService:520 - SERVER[] Log4j configuration file [oozie-log4j.properties] 2017-05-08 20:37:52,005 INFO XLogService:520 - SERVER[] Log4j configuration file loaded from [/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf] 2017-05-08 20:37:52,006 INFO XLogService:520 - SERVER[] Log4j reload interval [10 sec] 2017-05-08 20:37:52,132 INFO ConfigurationService:520 - SERVER[] Oozie home dir [/home/hadoop/app/oozie-4.1.0-cdh5.5.4] .....
[hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$ bin/oozie admin -oozie http://bigdatamaster:11000/oozie -status Connection exception has occurred [ java.net.ConnectException Connection refused ]. Trying after 1 sec. Retry count = 1 Connection exception has occurred [ java.net.ConnectException Connection refused ]. Trying after 2 sec. Retry count = 2 Connection exception has occurred [ java.net.ConnectException Connection refused ]. Trying after 4 sec. Retry count = 3 Connection exception has occurred [ java.net.ConnectException Connection refused ]. Trying after 8 sec. Retry count = 4 Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of retries = 4. Exception = Connection refused [hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$
解决办法
http://stackoverflow.com/questions/35171957/error-running-spark-action-in-oozie-user-root-is-not-allowed-to-impersonate-ro
修改为
在core-site.xml里修改为
<property> <name>oozie.services</name> <value> org.apache.oozie.service.SchedulerService, org.apache.oozie.service.InstrumentationService, org.apache.oozie.service.CallableQueueService, org.apache.oozie.service.UUIDService, org.apache.oozie.service.ELService, org.apache.oozie.service.AuthorizationService, org.apache.oozie.service.MemoryLocksService, org.apache.oozie.service.DagXLogInfoService, org.apache.oozie.service.SchemaService, org.apache.oozie.service.LiteWorkflowAppService, org.apache.oozie.service.JPAService, org.apache.oozie.service.StoreService, org.apache.oozie.service.CoordinatorStoreService, org.apache.oozie.service.SLAStoreService, org.apache.oozie.service.DBLiteWorkflowStoreService, org.apache.oozie.service.CallbackService, org.apache.oozie.service.ActionService, org.apache.oozie.service.ActionCheckerService, org.apache.oozie.service.RecoveryService, org.apache.oozie.service.PurgeService, org.apache.oozie.service.CoordinatorEngineService, org.apache.oozie.service.BundleEngineService, org.apache.oozie.service.DagEngineService, org.apache.oozie.service.CoordMaterializeTriggerService, org.apache.oozie.service.StatusTransitService, org.apache.oozie.service.PauseTransitService, org.apache.oozie.service.HadoopAccessorService </value> <description> All services to be created and managed by Oozie Services singleton. Class names must be separated by commas. </description> </property> <property> <name>oozie.service.ProxyUserService.proxyuser.hadoop.hosts</name> <value>*</value> <description> List of hosts the '#USER#' user is allowed to perform 'doAs' operations. The '#USER#' must be replaced with the username o the user who is allowed to perform 'doAs' operations. The value can be the '*' wildcard or a list of hostnames. For multiple users copy this property and replace the user name in the property name. </description> </property> <property> <name>oozie.service.ProxyUserService.proxyuser.hadoop.groups</name> <value>*</value> <description> List of groups the '#USER#' user is allowed to impersonate users from to perform 'doAs' operations. The '#USER#' must be replaced with the username o the user who is allowed to perform 'doAs' operations. The value can be the '*' wildcard or a list of groups. For multiple users copy this property and replace the user name in the property name. </description> </property>
在core-site.xml里
<!-- OOZIE --> <property> <name>hadoop.proxyuser.hadoop.hosts</name> <value>bigdatamaster</value> </property> <property> <name>hadoop.proxyuser.hadoop.groups</name> <value>hadoop</value> </property>
在oozie-env.sh里追加
export OOZIE_CONF=${OOZIE_HOME}/conf export OOZIE_DATA=${OOZIE_HOME}/data export OOZIE_LOG=${OOZIE_HOME}/logs export CATALINA_BASE=${OOZIE_HOME}/oozie-server export CATALINA_TMPDIR=${OOZIE_HOME}/oozie-server/temp export CATALINA_OUT=${OOZIE_LOG}/catalina.out
然后,再试试
[hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$ bin/oozied.sh start Setting OOZIE_HOME: /home/hadoop/app/oozie-4.1.0-cdh5.5.4 Setting OOZIE_CONFIG: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf Sourcing: /home/hadoop/app/oozie-4.1.0-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.0-cdh5.5.4/data Using OOZIE_LOG: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs Setting OOZIE_LOG4J_FILE: oozie-log4j.properties Setting OOZIE_LOG4J_RELOAD: 10 Setting OOZIE_HTTP_HOSTNAME: bigdatamaster Setting OOZIE_HTTP_PORT: 11000 Setting OOZIE_ADMIN_PORT: 11001 Setting OOZIE_HTTPS_PORT: 11443 Setting OOZIE_BASE_URL: http://bigdatamaster:11000/oozie Using CATALINA_BASE: /home/hadoop/app/oozie-4.1.0-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.0-cdh5.5.4/logs/catalina.out Setting CATALINA_PID: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie.pid Using CATALINA_OPTS: -Xmx1024m -Dderby.stream.error.file=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs/derby.log Adding to CATALINA_OPTS: -Doozie.home.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4 -Doozie.config.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/conf -Doozie.log.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/logs -Doozie.data.dir=/home/hadoop/app/oozie-4.1.0-cdh5.5.4/data -Doozie.instance.id=bigdatamaster -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10 -Doozie.http.hostname=bigdatamaster -Doozie.admin.port=11001 -Doozie.http.port=11000 -Doozie.https.port=11443 -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.0-cdh5.5.4/oozie-server Using CATALINA_HOME: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server Using CATALINA_TMPDIR: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp Using JRE_HOME: /home/hadoop/app/jdk Using CLASSPATH: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/bin/bootstrap.jar Using CATALINA_PID: /home/hadoop/app/oozie-4.1.0-cdh5.5.4/oozie-server/temp/oozie.pid Existing PID file found during start. Removing/clearing stale PID file. [hadoop@bigdatamaster oozie-4.1.0-cdh5.5.4]$
查看日志
2017-05-08 22:06:15,164 FATAL Services:514 - SERVER[bigdatamaster] Runtime Exception during Services Load. Check your list of 'oozie.services' or 'oozie.services.ext' 2017-05-08 22:06:15,180 FATAL Services:514 - 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:309) at org.apache.oozie.service.Services.init(Services.java:213) at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4709) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:802) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:944) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:779) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:505) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:325) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1068) at org.apache.catalina.core.StandardHost.start(StandardHost.java:822) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1060) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:759) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) 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:2178)
请见,
Oozie时出现org.apache.oozie.service.ServiceException: E0103: Could not load service classes, Cannot load JDBC driver class 'com.mysql.jdbc.Driver'
然后呢,大家也许还会出现如下问题:
Oozie安装时放置Mysql驱动包的总结(网上最全)
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?
作者:大数据和人工智能躺过的坑
出处:http://www.cnblogs.com/zlslch/
本文版权归作者和博客园共有,欢迎转载,但未经作者同意必须保留此段声明,且在文章页面明显位置给出原文链接,否则保留追究法律责任的权利。
如果您认为这篇文章还不错或者有所收获,您可以通过右边的“打赏”功能 打赏我一杯咖啡【物质支持】,也可以点击右下角的【好文要顶】按钮【精神支持】,因为这两种支持都是我继续写作,分享的最大动力!