oozie启动问题：Could not initialize service [org.apache.oozie.service.HadoopAccessorService]
来源：互联网 发布：lgd官方淘宝店 编辑：程序博客网 时间：2024/06/14 00:45
FATAL Services:533 - USER[-] GROUP[-] E0100: Could not initialize service [org.apache.oozie.service.HadoopAccessorService], org.xml.sax.SAXParseException; Premature end of file.
oozie-site.xml文件如下：
<?xml version="1.0"?><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.--><configuration> <!-- Refer to the oozie-default.xml file for the complete list of Oozie configuration properties and their default values. --> <property> <name>oozie.service.ActionService.executor.ext.classes</name> <value> org.apache.oozie.action.email.EmailActionExecutor, org.apache.oozie.action.hadoop.HiveActionExecutor, org.apache.oozie.action.hadoop.ShellActionExecutor, org.apache.oozie.action.hadoop.SqoopActionExecutor, org.apache.oozie.action.hadoop.DistcpActionExecutor </value> </property> <property> <name>oozie.service.SchemaService.wf.ext.schemas</name> <value>shell-action-0.1.xsd,shell-action-0.2.xsd,email-action-0.1.xsd,hive-action-0.2.xsd,hive-action-0.3.xsd,sqoop-action-0.2.xsd,sqoop-action-0.3.xsd,ssh-action-0.1.xsd,distcp-action-0.1.xsd</value> </property> <property> <name>oozie.system.id</name> <value>oozie-${user.name}</value> <description> The Oozie system ID. </description> </property> <property> <name>oozie.systemmode</name> <value>NORMAL</value> <description> System mode for Oozie at startup. </description> </property> <property> <name>oozie.service.AuthorizationService.security.enabled</name> <value>false</value> <description> Specifies whether security (user name/admin role) is enabled or not. If disabled any user can manage Oozie system and manage any job. </description> </property> <property> <name>oozie.service.AuthorizationService.authorization.enabled</name> <value>false</value> <description> Specifies whether security (user name/admin role) is enabled or not. If disabled any user can manage Oozie system and manage any job. </description> </property> <property> <name>oozie.service.PurgeService.older.than</name> <value>30</value> <description> Jobs older than this value, in days, will be purged by the PurgeService. </description> </property> <property> <name>oozie.service.PurgeService.purge.interval</name> <value>3600</value> <description> Interval at which the purge service will run, in seconds. </description> </property> <property> <name>oozie.service.CallableQueueService.queue.size</name> <value>10000</value> <description>Max callable queue size</description> </property> <property> <name>oozie.service.CallableQueueService.threads</name> <value>10</value> <description>Number of threads used for executing callables</description> </property> <property> <name>oozie.service.CallableQueueService.callable.concurrency</name> <value>3</value> <description> Maximum concurrency for a given callable type. Each command is a callable type (submit, start, run, signal, job, jobs, suspend,resume, etc). Each action type is a callable type (Map-Reduce, Pig, SSH, FS, sub-workflow, etc). All commands that use action executors (action-start, action-end, action-kill and action-check) use the action type as the callable type. </description> </property> <property><name>oozie.service.coord.normal.default.timeout</name><value>120</value><description>Default timeout for a coordinator action input check (in minutes) for normal job. -1 means infinite timeout</description></property> <property> <name>oozie.db.schema.name</name> <value>oozie</value> <description> Oozie DataBase Name </description> </property> <property> <name>oozie.service.JPAService.create.db.schema</name> <value>true</value> <description> Creates Oozie DB. If set to true, it creates the DB schema if it does not exist. If the DB schema exists is a NOP. If set to false, it does not create the DB schema. If the DB schema does not exist it fails start up. </description> </property> <property> <name>oozie.service.JPAService.jdbc.driver</name> <value>com.mysql.jdbc.Driver</value> <description> JDBC driver class. </description> </property> <property> <name>oozie.service.JPAService.jdbc.url</name> <value>jdbc:mysql://localhost:3306/oozie</value> <description> JDBC URL. </description> </property> <property> <name>oozie.service.JPAService.jdbc.username</name> <value>oozie</value> <description> DB user name. </description> </property> <property> <name>oozie.service.JPAService.jdbc.password</name> <value>oozie</value> <description> DB user password. IMPORTANT: if password is emtpy leave a 1 space string, the service trims the value, if empty Configuration assumes it is NULL. </description> </property> <property> <name>oozie.service.JPAService.pool.max.active.conn</name> <value>10</value> <description> Max number of connections. </description> </property> <property> <name>oozie.service.HadoopAccessorService.kerberos.enabled</name> <value>false</value> <description> Indicates if Oozie is configured to use Kerberos. </description> </property> <property> <name>local.realm</name> <value>LOCALHOST</value> <description> Kerberos Realm used by Oozie and Hadoop. Using 'local.realm' to be aligned with Hadoop configuration </description> </property> <property> <name>oozie.service.HadoopAccessorService.keytab.file</name> <value>${user.home}/oozie.keytab</value> <description> Location of the Oozie user keytab file. </description> </property> <property> <name>oozie.service.HadoopAccessorService.kerberos.principal</name> <value>${user.name}/localhost@${local.realm}</value> <description> Kerberos principal for Oozie service. </description> </property> <property> <name>oozie.service.HadoopAccessorService.jobTracker.whitelist</name> <value> </value> <description> Whitelisted job tracker for Oozie service. </description> </property> <property> <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name> <value> </value> <description> Whitelisted job tracker for Oozie service. </description> </property> <property> <name>oozie.service.HadoopAccessorService.hadoop.configurations</name> <value>*=/etc/hadoop/conf</value> <description> Comma separated AUTHORITY=HADOOP_CONF_DIR, where AUTHORITY is the HOST:PORT of the Hadoop service (JobTracker, HDFS). The wildcard '*' configuration is used when there is no exact match for an authority. The HADOOP_CONF_DIR contains the relevant Hadoop *-site.xml files. If the path is relative is looked within the Oozie configuration directory; though the path can be absolute (i.e. to point to Hadoop client conf/ directories in the local filesystem. </description> </property> <property> <name>oozie.service.WorkflowAppService.system.libpath</name> <value>/user/${user.name}/share/lib</value> <description> System library path to use for workflow applications. This path is added to workflow application if their job properties sets the property 'oozie.use.system.libpath' to true. </description> </property> <property> <name>use.system.libpath.for.mapreduce.and.pig.jobs</name> <value>false</value> <description> If set to true, submissions of MapReduce and Pig jobs will include automatically the system library path, thus not requiring users to specify where the Pig JAR files are. Instead, the ones from the system library path are used. </description> </property> <property> <name>oozie.authentication.type</name> <value>simple</value> <description> Defines authentication used for Oozie HTTP endpoint. Supported values are: simple | kerberos | #AUTHENTICATION_HANDLER_CLASSNAME# </description> </property> <property> <name>oozie.authentication.token.validity</name> <value>36000</value> <description> Indicates how long (in seconds) an authentication token is valid before it has to be renewed. </description> </property> <property> <name>oozie.authentication.signature.secret</name> <value>oozie</value> <description> The signature secret for signing the authentication tokens. If not set a random secret is generated at startup time. In order to authentiation to work correctly across multiple hosts the secret must be the same across al the hosts. </description> </property> <property> <name>oozie.authentication.cookie.domain</name> <value></value> <description> The domain to use for the HTTP cookie that stores the authentication token. In order to authentiation to work correctly across multiple hosts the domain must be correctly set. </description> </property> <property> <name>oozie.authentication.simple.anonymous.allowed</name> <value>true</value> <description> Indicates if anonymous requests are allowed. This setting is meaningful only when using 'simple' authentication. </description> </property> <property> <name>oozie.authentication.kerberos.principal</name> <value>HTTP/localhost@${local.realm}</value> <description> Indicates the Kerberos principal to be used for HTTP endpoint. The principal MUST start with 'HTTP/' as per Kerberos HTTP SPNEGO specification. </description> </property> <property> <name>oozie.authentication.kerberos.keytab</name> <value>${oozie.service.HadoopAccessorService.keytab.file}</value> <description> Location of the keytab file with the credentials for the principal. Referring to the same keytab file Oozie uses for its Kerberos credentials for Hadoop. </description> </property> <property> <name>oozie.authentication.kerberos.name.rules</name> <value>DEFAULT</value> <description> The kerberos names rules is to resolve kerberos principal names, refer to Hadoop's KerberosName for more details. </description> </property> <!-- Proxyuser Configuration --> <!-- <property> <name>oozie.service.ProxyUserService.proxyuser.#USER#.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.#USER#.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> --> <!-- Default proxyuser configuration for Hue --> <property> <name>oozie.service.ProxyUserService.proxyuser.hue.hosts</name> <value>*</value> </property> <property> <name>oozie.service.ProxyUserService.proxyuser.hue.groups</name> <value>*</value> </property> <property> <name>oozie.action.mapreduce.uber.jar.enable</name> <value>true</value> </property> <property> <name>oozie.service.HadoopAccessorService.supported.filesystems</name> <value>hdfs,viewfs</value> </property></configuration>[root@localhost conf]# service oozie startSetting OOZIE_HOME: /usr/lib/oozieSourcing: /usr/lib/oozie/bin/oozie-env.sh setting OOZIE_CONFIG=/etc/oozie/conf setting OOZIE_DATA=/var/lib/oozie setting OOZIE_LOG=/var/log/oozie setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat setting CATALINA_TMPDIR=/var/lib/oozie setting CATALINA_PID=/var/run/oozie/oozie.pid setting CATALINA_BASE=/usr/lib/oozie/oozie-server-0.20 setting CATALINA_OPTS=-Xmx1024m setting OOZIE_HTTPS_PORT=11443 setting OOZIE_HTTPS_KEYSTORE_PASS=password setting CATALINA_OPTS="$CATALINA_OPTS -Doozie.https.port=${OOZIE_HTTPS_PORT}" setting CATALINA_OPTS="$CATALINA_OPTS -Doozie.https.keystore.pass=${OOZIE_HTTPS_KEYSTORE_PASS}"Using OOZIE_CONFIG: /etc/oozie/confSourcing: /etc/oozie/conf/oozie-env.sh setting OOZIE_CONFIG=/etc/oozie/conf setting OOZIE_DATA=/var/lib/oozie setting OOZIE_LOG=/var/log/oozie setting OOZIE_CATALINA_HOME=/usr/lib/bigtop-tomcat setting CATALINA_TMPDIR=/var/lib/oozie setting CATALINA_PID=/var/run/oozie/oozie.pid setting CATALINA_BASE=/usr/lib/oozie/oozie-server-0.20 setting CATALINA_OPTS=-Xmx1024m setting OOZIE_HTTPS_PORT=11443 setting OOZIE_HTTPS_KEYSTORE_PASS=password setting CATALINA_OPTS="$CATALINA_OPTS -Doozie.https.port=${OOZIE_HTTPS_PORT}" setting CATALINA_OPTS="$CATALINA_OPTS -Doozie.https.keystore.pass=${OOZIE_HTTPS_KEYSTORE_PASS}"Setting OOZIE_CONFIG_FILE: oozie-site.xmlUsing OOZIE_DATA: /var/lib/oozieUsing OOZIE_LOG: /var/log/oozieSetting OOZIE_LOG4J_FILE: oozie-log4j.propertiesSetting OOZIE_LOG4J_RELOAD: 10Setting OOZIE_HTTP_HOSTNAME: localhostSetting OOZIE_HTTP_PORT: 11000Setting OOZIE_ADMIN_PORT: 11001Setting OOZIE_BASE_URL: http://localhost:11000/oozieUsing CATALINA_BASE: /usr/lib/oozie/oozie-server-0.20Setting CATALINA_OUT: /var/log/oozie/catalina.outUsing CATALINA_PID: /var/run/oozie/oozie.pidUsing CATALINA_OPTS: -Xmx1024m -Doozie.https.port=11443 -Doozie.https.keystore.pass=password -Dderby.stream.error.file=/var/log/oozie/derby.logAdding to CATALINA_OPTS: -Doozie.home.dir=/usr/lib/oozie -Doozie.config.dir=/etc/oozie/conf -Doozie.log.dir=/var/log/oozie -Doozie.data.dir=/var/lib/oozie -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10 -Doozie.http.hostname=localhost -Doozie.admin.port=11001 -Doozie.http.port=11000 -Doozie.base.url=http://localhost:11000/oozieUsing CATALINA_BASE: /usr/lib/oozie/oozie-server-0.20Using CATALINA_HOME: /usr/lib/bigtop-tomcatUsing CATALINA_TMPDIR: /var/lib/oozieUsing JRE_HOME: /usr/java/jdk1.7.0_25/jreUsing CLASSPATH: /usr/lib/bigtop-tomcat/bin/bootstrap.jarUsing CATALINA_PID: /var/run/oozie/oozie.pid[root@localhost conf]# oozie admin -oozie http://localhost:11000/oozie -statusError: IO_ERROR : java.net.ConnectException: Connection refused
[root@localhost oozie]# cat oozie.log2014-03-18 04:22:27,072 INFO XLogService:539 - ******************************************************************************* STARTUP MSG: Oozie BUILD_VERSION [3.3.0-cdh4.2.1] compiled by [jenkins] on [2013.04.22-19:38:39GMT] STARTUP MSG: revision [unavailable]@[unavailable]*******************************************************************************2014-03-18 04:22:27,076 INFO XLogService:539 - Log4j configuration file [oozie-log4j.properties]2014-03-18 04:22:27,076 INFO XLogService:539 - Log4j configuration file loaded from [/etc/oozie/conf]2014-03-18 04:22:27,077 INFO XLogService:539 - Log4j reload interval [10 sec]2014-03-18 04:22:27,093 INFO ConfigurationService:539 - USER[-] GROUP[-] Oozie home dir [/usr/lib/oozie]2014-03-18 04:22:27,094 INFO ConfigurationService:539 - USER[-] GROUP[-] Oozie conf dir [/etc/oozie/conf]2014-03-18 04:22:27,094 INFO ConfigurationService:539 - USER[-] GROUP[-] Oozie conf file [oozie-site.xml]2014-03-18 04:22:27,243 INFO ConfigurationService:539 - USER[-] GROUP[-] Configuration change via System Property, [oozie.base.url]=[http://localhost:11000/oozie]2014-03-18 04:22:27,246 WARN ConfigurationService:542 - USER[-] GROUP[-] System property [oozie.https.keystore.pass] no defined in Oozie configuration, ignored2014-03-18 04:22:27,247 WARN ConfigurationService:542 - USER[-] GROUP[-] System property [oozie.admin.port] no defined in Oozie configuration, ignored2014-03-18 04:22:27,247 WARN ConfigurationService:542 - USER[-] GROUP[-] System property [oozie.https.port] no defined in Oozie configuration, ignored2014-03-18 04:22:27,253 WARN Services:542 - USER[-] GROUP[-] System ID [oozie-oozi] exceeds maximum length [10], trimming2014-03-18 04:22:27,258 INFO Services:539 - USER[-] GROUP[-] Exiting null Entering NORMAL2014-03-18 04:22:27,260 INFO Services:539 - USER[-] GROUP[-] Initialized runtime directory [/var/lib/oozie/oozie-oozi2413457807675791802.dir]2014-03-18 04:22:27,322 WARN ConfigurationService:542 - USER[-] GROUP[-] Configuration property [oozie.service.ELService.ext.constants.job-submit] not found, using default []2014-03-18 04:22:27,323 WARN ConfigurationService:542 - USER[-] GROUP[-] Configuration property [oozie.service.ELService.ext.functions.job-submit] not found, using default []2014-03-18 04:22:27,434 WARN ConfigUtils:542 - USER[-] GROUP[-] Using a deprecated configuration property [oozie.service.AuthorizationService.security.enabled], should use [oozie.service.AuthorizationService.authorization.enabled]. Please delete the deprecated property in order for the new property to take effect.2014-03-18 04:22:27,434 WARN AuthorizationService:542 - USER[-] GROUP[-] Oozie running with authorization disabled2014-03-18 04:22:27,435 INFO HadoopAccessorService:539 - USER[-] GROUP[-] JOB_TRACKER_WHITELIST :[ ], Total entries :02014-03-18 04:22:27,436 INFO HadoopAccessorService:539 - USER[-] GROUP[-] NAME_NODE_WHITELIST :[ ], Total entries :02014-03-18 04:22:27,436 INFO HadoopAccessorService:539 - USER[-] GROUP[-] Oozie Kerberos Authentication [disabled]2014-03-18 04:22:27,758 WARN NativeCodeLoader:62 - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable2014-03-18 04:22:27,892 WARN Configuration:824 - fs.default.name is deprecated. Instead, use fs.defaultFS2014-03-18 04:22:27,910 FATAL Services:533 - USER[-] GROUP[-] E0100: Could not initialize service [org.apache.oozie.service.HadoopAccessorService], org.xml.sax.SAXParseException; Premature end of file.org.apache.oozie.service.ServiceException: E0100: Could not initialize service [org.apache.oozie.service.HadoopAccessorService], org.xml.sax.SAXParseException; Premature end of file. at org.apache.oozie.service.HadoopAccessorService.loadHadoopConfigs(HadoopAccessorService.java:231) at org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:124) at org.apache.oozie.service.HadoopAccessorService.init(HadoopAccessorService.java:85) at org.apache.oozie.service.Services.setServiceInternal(Services.java:368) at org.apache.oozie.service.Services.setService(Services.java:354) at org.apache.oozie.service.Services.loadServices(Services.java:287) at org.apache.oozie.service.Services.init(Services.java:208) at org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:39) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) 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:754) 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.io.IOException: org.xml.sax.SAXParseException; Premature end of file. at org.apache.oozie.util.XConfiguration.parse(XConfiguration.java:251) at org.apache.oozie.util.XConfiguration.<init>(XConfiguration.java:63) at org.apache.oozie.service.HadoopAccessorService.loadHadoopConf(HadoopAccessorService.java:181) at org.apache.oozie.service.HadoopAccessorService.loadHadoopConfigs(HadoopAccessorService.java:224) ... 31 moreCaused by: org.xml.sax.SAXParseException; Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.apache.oozie.util.XConfiguration.parse(XConfiguration.java:246) ... 34 more
0 0
- oozie启动问题：Could not initialize service [org.apache.oozie.service.HadoopAccessorService]
- webservice: Could not initialize Service NoSuchMethodException getPortClassMap()
- webservice: Could not initialize Service NoSuchMethodException getPortClassMap()
- oozie.action.ActionExecutorException: Could not locate Oozie sharelib
- error：org.apache.oozie.action.ActionExecutorException:Permissiondenied
- 关于在java6中使用XFire时碰到的一个问题Could not initialize Service
- Oozie
- Oozie
- OOZIE
- oozie
- oozie
- oozie
- oozie
- Oozie
- Could not initialize class org.apache.struts2.json.JSONResult
- org.apache.cxf.binding.soap.SoapFault: Could not initialize class
- Could not initialize class org.apache.xpath.compiler.FunctionTable
- Could not initialize class org.apache.log4j.Log4jLoggerFactory
- 手把手教你把Vim改装成一个IDE编程环境(图文)
- oracle中utl_file包的使用
- 关于c#中判断dataset中填充的表数据是否为空的总结
- bochs安装
- HDU2112HDU Today单源最短路
- oozie启动问题：Could not initialize service [org.apache.oozie.service.HadoopAccessorService]
- 冒泡排序的三种实现
- iOS安全系列汇总
- 聚集表（clustered table）data page中的数据行可以无序
- HTML5中使用JSON对象存取数据
- OGNL(对象图导航语言)基础了解
- 新华网：房价涨幅放缓成趋势 楼市风向正在改变
- 我在路上最爱你
- java环境变量详解
