Hi Lian Jiang,

you could set TRACE level logging
<https://oozie.apache.org/docs/4.3.1/AG_OozieLogging.html> for package
org.apache.oozie.service
<https://github.com/apache/oozie/blob/release-4.3.1/core/src/main/java/org/apache/oozie/service/Services.java>
for better log information.

Can you please also post stderr content? Should be somewhere around
catalina.log.

Regards,

Andras

On Tue, Aug 21, 2018 at 7:02 PM Lian Jiang <jiangok2...@gmail.com> wrote:

> Thanks Andras.
>
> /usr/hdp/current/oozie-server/oozie-sharelib.tar.gz missing does not 100%
> repro. I will cut the log when I repro it again.
>
> In my new repro, /usr/hdp/current/oozie-server/oozie-sharelib.tar.gz
> presents. However, oozie server cannot be started and the logs are not
> obvious:
>
>
>
> *******************************************************************************
>
>
>   STARTUP MSG: Oozie BUILD_VERSION [4.3.1.3.0.0.0-1634] compiled by
> [jenkins] on [${build.time}]
>
>   STARTUP MSG:       revision [${vc.revision}]@[${vc.url}]
>
>
> *******************************************************************************
>
> 2018-08-21 05:59:46,794  INFO XLogService:520 - SERVER[] Log4j
> configuration file [oozie-log4j.properties]
>
> 2018-08-21 05:59:46,795  INFO XLogService:520 - SERVER[] Log4j
> configuration file loaded from [/usr/hdp/current/oozie-server/conf]
>
> 2018-08-21 05:59:46,795  INFO XLogService:520 - SERVER[] Log4j reload
> interval [10 sec]
>
> 2018-08-21 05:59:46,796  INFO ConfigurationService:520 - SERVER[] Oozie
> home dir  [/usr/hdp/3.0.0.0-1634/oozie]
>
> 2018-08-21 05:59:46,796  INFO ConfigurationService:520 - SERVER[] Oozie
> conf dir  [/usr/hdp/current/oozie-server/conf]
>
> 2018-08-21 05:59:46,797  INFO ConfigurationService:520 - SERVER[] Oozie
> conf file [oozie-site.xml]
>
> 2018-08-21 05:59:46,810  WARN ConfigurationService:523 - SERVER[] Invalid
> configuration defined, [use.system.libpath.for.mapreduce.and.pig.jobs]
>
> 2018-08-21 05:59:46,811  WARN ConfigurationService:523 - SERVER[] Invalid
> configuration defined, [oozie.email.smtp.password]
>
> 2018-08-21 05:59:46,811  WARN ConfigurationService:523 - SERVER[] Invalid
> configuration defined, [oozie.email.smtp.username]
>
> 2018-08-21 05:59:46,812  WARN ConfigurationService:523 - SERVER[] Invalid
> configuration defined,
> [oozie.service.AuthorizationService.security.enabled]
>
>
> 2018-08-21 05:59:46,813  WARN ConfigurationService:523 - SERVER[] Invalid
> configuration defined, [oozie.authentication.jwt.cookie]
>
> 2018-08-21 05:59:46,813  INFO Services:520 - SERVER[] Exiting null Entering
> NORMAL
>
> 2018-08-21 05:59:46,814  INFO Services:520 - SERVER[] Initialized runtime
> directory [/tmp/oozie-root151166298688308409.dir]
>
> 2018-08-21 05:59:46,815  INFO ConfigurationService:520 - SERVER[]
> Programmatic configuration change,
> property[oozie.services]=[org.apache.oozie.service.HadoopAccessorService]
>
> 2018-08-21 05:59:46,815  INFO ConfigurationService:520 - SERVER[]
> Programmatic configuration change, property[oozie.services.ext]=[]
>
> 2018-08-21 05:59:46,816  INFO HadoopAccessorService:520 - SERVER[]
> JOB_TRACKER_WHITELIST :[], Total entries :0
>
> 2018-08-21 05:59:46,816  INFO HadoopAccessorService:520 - SERVER[]
> NAME_NODE_WHITELIST :[], Total entries :0
>
> 2018-08-21 05:59:46,816  INFO HadoopAccessorService:520 - SERVER[] Oozie
> Kerberos Authentication [disabled]
>
> 2018-08-21 05:59:46,841  INFO Services:520 - SERVER[] Initialized
>
> 2018-08-21 05:59:46,841  INFO Services:520 - SERVER[] Running with JARs for
> Hadoop version [3.1.0.3.0.0.0-1634]
>
> 2018-08-21 05:59:46,841  INFO Services:520 - SERVER[] Oozie System ID
> [oozie-root] started!
>
> 2018-08-21 05:59:46,842  INFO Services:520 - SERVER[] Shutdown
>
>
>
> As you can see, oozie server started and shutdown, causing port 11000
> cannot be connected. The warnings should be benign because it worked in
> HDP2.6.
>
>
> Again, I *sometimes *can start oozie server successfully and port 11000
> works fine. However, oozie installation is extremely unreliable due to
> multiple issues (e.g. missing oozie-sharelib.tar.gz, oozie server
> shutdown).
>
>
> Any idea why oozie server shutdown? How to debug? Thanks a lot.
>
>
>
> On Tue, Aug 21, 2018 at 1:10 AM Andras Piros <and...@apache.org> wrote:
>
> > Hi Lian Jiang,
> >
> > as I'm not familiar w/ HDP, can you please post exception logs? I believe
> > HDP 3.0 is based on Oozie 4.3.1.
> >
> > For a general introduction how Oozie sharelib works, please see relevant
> > parts of the Apache Oozie documentation
> > <https://oozie.apache.org/docs/4.3.1/AG_Install.html#Oozie_Share_Lib>
> and
> > this
> > blog entry
> > <
> >
> https://blog.cloudera.com/blog/2014/05/how-to-use-the-sharelib-in-apache-oozie-cdh-5/
> > >
> > .
> >
> > Regards,
> >
> > Andras
> >
> > On Tue, Aug 21, 2018 at 12:01 AM Lian Jiang <jiangok2...@gmail.com>
> wrote:
> >
> > > Hi,
> > >
> > > I am using HDP3.0 and ambari 2.7 blueprint to install a cluster.
> > Everything
> > > but oozie worked. The oozie failed to start due to the fact that
> > > /usr/hdp/current/oozie-server/oozie-sharelib.tar.gz is not generated.
> > >
> > > oozie-sharelib.tar.gz is 1.6G and Our production environment has very
> > small
> > > /tmp partition (1G). I guess this is the reason why
> oozie-sharelib.tar.gz
> > > is not generated using ambari cluster installation. I hacked
> > oozie-setup.sh
> > > to use /u01/tmp (a bigger partition) instead of /tmp and assumed
> > > "oozie-setup.sh prepare-war" will generate oozie-sharelib.tar.gz.
> > However,
> > > I still did not get oozie-sharelib.tar.gz.
> > >
> > > Any idea how to install oozie in this case? Thanks.
> > >
> >
>

Reply via email to