[
https://issues.apache.org/jira/browse/BIGTOP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142389#comment-13142389
]
Peter Linnell commented on BIGTOP-237:
--------------------------------------
Could you see what "oozie stop" does, too, while you're doing it? I ran into an
issue recently where "oozie stop" is quite verbose; more so than init scripts
are supposed to be. That's on u1.
[0]air:master:hadoop-conf(199978)$sudo !!
sudo /etc/init.d/oozie stop
[sudo] password for philip:
No directory, logging in with HOME=/
Setting OOZIE_HOME: /usr/lib/oozie
Sourcing: /usr/lib/oozie/bin/oozie-env.sh
setting OOZIE_CONFIG=/etc/oozie
setting OOZIE_DATA=/var/lib/oozie
setting OOZIE_LOG=/var/log/oozie
setting CATALINA_BASE=${OOZIE_DATA}/oozie-server
setting CATALINA_TMPDIR=/var/tmp/oozie
setting CATALINA_PID=/var/run/oozie/oozie.pid
Using OOZIE_CONFIG: /etc/oozie
Sourcing: /etc/oozie/oozie-env.sh
Setting OOZIE_CONFIG_FILE: oozie-site.xml
Using OOZIE_DATA: /var/lib/oozie
Using OOZIE_LOG: /var/log/oozie
Setting OOZIE_LOG4J_FILE: oozie-log4j.properties
Setting OOZIE_LOG4J_RELOAD: 10
Setting OOZIE_HTTP_HOSTNAME: air
Setting OOZIE_HTTP_PORT: 11000
Setting OOZIE_BASE_URL: http://air:11000/oozie
Using CATALINA_BASE: /var/lib/oozie/oozie-server
Setting CATALINA_OUT: /var/log/oozie/catalina.out
Using CATALINA_PID: /var/run/oozie/oozie.pid
Using CATALINA_BASE: /var/lib/oozie/oozie-server
Using CATALINA_HOME: /usr/lib/oozie/oozie-server
Using CATALINA_TMPDIR: /var/tmp/oozie
Using JRE_HOME: /usr
Using CLASSPATH: /usr/lib/oozie/oozie-server/bin/bootstrap.jar
Using CATALINA_PID: /var/run/oozie/oozie.pid
Oozie stop succeeded
> Oozie init scripts are way too verbose
> --------------------------------------
>
> Key: BIGTOP-237
> URL: https://issues.apache.org/jira/browse/BIGTOP-237
> Project: Bigtop
> Issue Type: Sub-task
> Components: General
> Affects Versions: 0.1.0
> Reporter: Peter Linnell
> Priority: Minor
> Fix For: 0.4.0
>
>
> [root@localhost init.d]# service oozie start
> Setting OOZIE_HOME: /usr/lib/oozie
> Sourcing: /usr/lib/oozie/bin/oozie-env.sh
> setting OOZIE_CONFIG=/etc/oozie
> setting OOZIE_DATA=/var/lib/oozie
> setting OOZIE_LOG=/var/log/oozie
> setting CATALINA_BASE=${OOZIE_DATA}/oozie-server
> setting CATALINA_TMPDIR=/var/tmp/oozie
> setting CATALINA_PID=/var/run/oozie/oozie.pid
> Using OOZIE_CONFIG: /etc/oozie
> Sourcing: /etc/oozie/oozie-env.sh
> Setting OOZIE_CONFIG_FILE: oozie-site.xml
> Using OOZIE_DATA: /var/lib/oozie
> Using OOZIE_LOG: /var/log/oozie
> Setting OOZIE_LOG4J_FILE: oozie-log4j.properties
> Setting OOZIE_LOG4J_RELOAD: 10
> Setting OOZIE_HTTP_HOSTNAME: localhost.localdomain
> Setting OOZIE_HTTP_PORT: 11000
> Setting OOZIE_BASE_URL: http://localhost.localdomain:11000/oozie
> Using CATALINA_BASE: /var/lib/oozie/oozie-server
> Setting CATALINA_OUT: /var/log/oozie/catalina.out
> Using CATALINA_PID: /var/run/oozie/oozie.pid
> Using CATALINA_OPTS: -Dderby.stream.error.file=/var/log/oozie/derby.log
> Adding to CATALINA_OPTS: -Doozie.home.dir=/usr/lib/oozie
> -Doozie.config.dir=/etc/oozie -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.localdomain -Doozie.http.port=11000
> -Doozie.base.url=http://localhost.localdomain:11000/oozie
> WARN: Oozie WAR has not been set up at
> ''/var/lib/oozie/oozie-server/webapps'', doing default set up
> setting OOZIE_CONFIG=/etc/oozie
> setting OOZIE_DATA=/var/lib/oozie
> setting OOZIE_LOG=/var/log/oozie
> setting CATALINA_BASE=${OOZIE_DATA}/oozie-server
> setting CATALINA_TMPDIR=/var/tmp/oozie
> setting CATALINA_PID=/var/run/oozie/oozie.pid
> INFO: Oozie webconsole disabled, ExtJS library not specified
> INFO: Doing default installation
> INFO: Oozie is ready to be started
> Using CATALINA_BASE: /var/lib/oozie/oozie-server
> Using CATALINA_HOME: /usr/lib/oozie/oozie-server
> Using CATALINA_TMPDIR: /var/tmp/oozie
> Using JRE_HOME: /usr
> Using CLASSPATH: /usr/lib/oozie/oozie-server/bin/bootstrap.jar
> Oozie started
> [root@localhost init.d]# service oozie stop
> Setting OOZIE_HOME: /usr/lib/oozie
> Sourcing: /usr/lib/oozie/bin/oozie-env.sh
> setting OOZIE_CONFIG=/etc/oozie
> setting OOZIE_DATA=/var/lib/oozie
> setting OOZIE_LOG=/var/log/oozie
> setting CATALINA_BASE=${OOZIE_DATA}/oozie-server
> setting CATALINA_TMPDIR=/var/tmp/oozie
> setting CATALINA_PID=/var/run/oozie/oozie.pid
> Using OOZIE_CONFIG: /etc/oozie
> Sourcing: /etc/oozie/oozie-env.sh
> Setting OOZIE_CONFIG_FILE: oozie-site.xml
> Using OOZIE_DATA: /var/lib/oozie
> Using OOZIE_LOG: /var/log/oozie
> Setting OOZIE_LOG4J_FILE: oozie-log4j.properties
> Setting OOZIE_LOG4J_RELOAD: 10
> Setting OOZIE_HTTP_HOSTNAME: localhost.localdomain
> Setting OOZIE_HTTP_PORT: 11000
> Setting OOZIE_BASE_URL: http://localhost.localdomain:11000/oozie
> Using CATALINA_BASE: /var/lib/oozie/oozie-server
> Setting CATALINA_OUT: /var/log/oozie/catalina.out
> Using CATALINA_PID: /var/run/oozie/oozie.pid
> Using CATALINA_BASE: /var/lib/oozie/oozie-server
> Using CATALINA_HOME: /usr/lib/oozie/oozie-server
> Using CATALINA_TMPDIR: /var/tmp/oozie
> Using JRE_HOME: /usr
> Using CLASSPATH: /usr/lib/oozie/oozie-server/bin/bootstrap.jar
> Oozie stopped
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
