Oozie 2.3 is very old and doesn't have ooziedb.sh. I think that was added from either 3.2 or 3.3 Can you post contents from derby.log? Also, I see that 2.3 didn't have JPAService but is using StoreService. Asking Alejandro and Mohammad if they have seen this before.
Thanks, Virag On 6/26/13 10:52 PM, "Robert Kanter" <[email protected]> wrote: >It should be in the bin folder: >$ ls -l bin/ >total 104 >-rwxr-xr-x 1 rkanter staff 9723 Jun 26 22:49 addtowar.sh >-rwxr-xr-x 1 rkanter staff 1607 Jun 26 22:49 oozie >-rwxr-xr-x 1 rkanter staff 1221 Jun 26 22:49 oozie-run.sh >-rwxr-xr-x 1 rkanter staff 7242 Jun 26 22:49 oozie-setup.sh >-rwxr-xr-x 1 rkanter staff 1224 Jun 26 22:49 oozie-start.sh >-rwxr-xr-x 1 rkanter staff 1221 Jun 26 22:49 oozie-stop.sh >-rwxr-xr-x 1 rkanter staff 7066 Jun 26 22:49 oozie-sys.sh >-rwxr-xr-x 1 rkanter staff 3440 Jun 26 22:49 oozied.sh >*-rwxr-xr-x 1 rkanter staff 1932 Jun 26 22:49 ooziedb.sh* > >- Robert > > >On Wed, Jun 26, 2013 at 10:41 PM, Shalish VJ <[email protected]> wrote: > >> Hi, >> >> I am using oozie : 2.3.0 >> >> I couldnt find ooziedb.sh script in it. >> >> Can u please guide me. >> ------------------------------ >> *From:* Robert Kanter <[email protected]> >> *To:* "[email protected]" <[email protected]>; Shalish VJ < >> [email protected]> >> *Sent:* Wednesday, June 26, 2013 10:09 PM >> *Subject:* Re: Error while using OOZIE : Failed to start database >> >> Hi Shalish, >> >> Did you create the database? Before starting Oozie for the first time, >> you should run the ooziedb.sh script. >> >> - Robert >> >> >> On Wed, Jun 26, 2013 at 12:02 AM, Shalish VJ <[email protected]> >>wrote: >> >> Hi >> >> I have an oozie installation >> >> Oozie has been installed 2.3.0 through deb package. >> >> Hadoop Version : 0.20 >> >> Command to start oozie : sudo -u oozie >> /usr/lib/oozieinst/oozie-2.3.2-cdh3u5/bin/oozie-start.sh >> >> When I check the status or run a workflow using the following commands, >> >> /usr/lib/oozieinst/oozie-2.3.2-cdh3u5/bin/oozie admin -oozie >> http://localhost:11009/oozie -status >> >> sudo -u oozie oozie job -oozie http://localhost:11009/oozie -config >> job.properties -run >> >> I am getting an error >> >> Error: HTTP error code: 404 : Not Found >> >> >> I had already made the configuration changes, restarted hadoop and oozie >> to rectify the error - but they are not working. >> >> Configuration:- >> ------------------ >> >> Core-site.xml >> >> <property> >> <name>hadoop.proxyuser.oozie.hosts</name> >> <value>*</value> >> </property> >> <property> >> <name>hadoop.proxyuser.oozie.groups</name> >> <value>*</value> >> </property> >> >> >> Oozie-site.xml :- >> >> <property > >> <name >oozie.services.ext</name > >> <value > >> org.apache.oozie.service.HadoopAccessorService >> </value > >> <description > >> To add/replace services defined in 'oozie.services' with custom >> implementations.Class names must be separated by commas. >> </description > >> </property > >> >> >> <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.HadoopAccessorService, >> org.apache.oozie.service.MemoryLocksService, >> org.apache.oozie.service.DagXLogInfoService, >> org.apache.oozie.service.SchemaService, >> org.apache.oozie.service.LiteWorkflowAppService, >> 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.DagEngineService, >> org.apache.oozie.service.CoordJobMatLookupTriggerService >> >> </value> >> <description> >> All services to be created and managed by Oozie Services >> singleton. >> Class names must be separated by commas. >> </description> >> </property> >> >> >> >> >> Error Logs:- >> >> localhost.2013-06-25.log >> -------------------------- >> >> 25 Jun, 2013 5:17:48 PM org.apache.catalina.core.StandardContext >> listenerStart >> SEVERE: Exception sending context initialized event to listener instance >> of class org.apache.oozie.servlet.ServicesLoader >> <openjpa-1.2.1-r752877:753278 fatal general error> >> org.apache.openjpa.persistence.PersistenceException: Cannot create >> >> PoolableConnectionFactory (Failed to start database >> '/usr/lib/oozieinst/oozie-2.3.2-cdh3u5/data/oozie-db' with class loader >> >> WebappClassLoader >> context: /oozie >> delegate: false >> repositories: >> /WEB-INF/classes/ >> ----------> Parent Classloader: >> org.apache.catalina.loader.StandardClassLoader@c4aad3 >> , see the next exception for details.) >> at >> >>org.apache.openjpa.jdbc.sql.DBDictionaryFactory.newDBDictionary(DBDiction >>aryFactory.java:101) >> at >> >>org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstanc >>e(JDBCConfigurationImpl.java:562) >> at >> >>org.apache.openjpa.jdbc.meta.MappingRepository.endConfiguration(MappingRe >>pository.java:1265) >> at >> >>org.apache.openjpa.lib.conf.Configurations.configureInstance(Configuratio >>ns.java:505) >> at >> >>org.apache.openjpa.lib.conf.Configurations.configureInstance(Configuratio >>ns.java:430) >> at >> >>org.apache.openjpa.lib.conf.PluginValue.instantiate(PluginValue.java:103) >> at >> >>org.apache.openjpa.conf.MetaDataRepositoryValue.instantiate(MetaDataRepos >>itoryValue.java:68) >> at >>org.apache.openjpa.lib.conf.ObjectValue.instantiate(ObjectValue.java:83) >> at >> >>org.apache.openjpa.conf.OpenJPAConfigurationImpl.newMetaDataRepositoryIns >>tance(OpenJPAConfigurationImpl.java:863) >> at >> >>org.apache.openjpa.conf.OpenJPAConfigurationImpl.getMetaDataRepositoryIns >>tance(OpenJPAConfigurationImpl.java:854) >> at >> >>org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrok >>erFactory.java:638) >> at >> >>org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerF >>actory.java:183) >> at >> >>org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBro >>kerFactory.java:142) >> at >> >>org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManag >>er(EntityManagerFactoryImpl.java:192) >> at >> >>org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManag >>er(EntityManagerFactoryImpl.java:145) >> at >> >>org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManag >>er(EntityManagerFactoryImpl.java:56) >> at >> >>org.apache.oozie.service.StoreService.getEntityManager(StoreService.java: >>204) >> at org.apache.oozie.service.StoreService.init(StoreService.java:170) >> at >>org.apache.oozie.service.Services.setServiceInternal(Services.java:307) >> at org.apache.oozie.service.Services.setService(Services.java:293) >> at org.apache.oozie.service.Services.init(Services.java:203) >> at >> >>org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader >>.java:37) >> at >> >>org.apache.catalina.core.StandardContext.listenerStart(StandardContext.ja >>va:4205) >> at >> >>org.apache.catalina.core.StandardContext.start(StandardContext.java:4704) >> at >> >>org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.jav >>a: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.deployDescriptor(HostConfig.java:6 >>75) >> at >> >>org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java: >>601) >> at >>org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) >> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315) >> at >> >>org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324 >>) >> at >> >>org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSup >>port.java:142) >> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) >> at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) >> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) >> 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 >>:39) >> at >> >>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI >>mpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) >> Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create >> PoolableConnectionFactory (Failed to start database >> >> '/usr/lib/oozieinst/oozie-2.3.2-cdh3u5/data/oozie-db' with class loader >> WebappClassLoader >> context: /oozie >> delegate: false >> repositories: >> /WEB-INF/classes/ >> ----------> Parent Classloader: >> org.apache.catalina.loader.StandardClassLoader@c4aad3 >> , see the next exception for details.) >> at >> >>org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(B >>asicDataSource.java:1549) >> at >> >>org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource. >>java:1388) >> ............................. >> ............................. >> >>org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService >>(Unknown >> Source) >> at >> >>org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unk >>nown >> Source) >> ... 61 more >> >> >> It seems like some issue with derby I guess. >> Please advice how to resolve the issue. >> >> >> >> >>
