You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "SHOBAN (JIRA)" <ji...@apache.org> on 2013/08/27 09:05:53 UTC

[jira] [Updated] (OOZIE-1512) Webconsole

     [ https://issues.apache.org/jira/browse/OOZIE-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SHOBAN updated OOZIE-1512:
--------------------------

    Description: 
Hi,
oozie is started and stop is correctly but while running the link it is
showing the error.(As a fresher I want try to learn about Oozie and i
want to execute the sample program)

 bin/oozie-setup.sh

INFO: Oozie webconsole disabled, ExtJS library not specified
INFO: Doing default installation
INFO: Oozie is ready to be started

bin/oozie-start.sh

Setting OOZIE_HOME:          /usr/local/oozie
Setting OOZIE_CONFIG:        /usr/local/oozie/conf
Sourcing:                    /usr/local/oozie/conf/oozie-env.sh
Setting OOZIE_CONFIG_FILE:   oozie-site.xml
Setting OOZIE_DATA:          /usr/local/oozie/data
Setting OOZIE_LOG:           /usr/local/oozie/logs
Setting OOZIE_LOG4J_FILE:    oozie-log4j.properties
Setting OOZIE_LOG4J_RELOAD:  10
Setting OOZIE_HTTP_HOSTNAME: computer10-MS-7211
Setting OOZIE_HTTP_PORT:     11000
Setting OOZIE_BASE_URL:      http://computer10-MS-7211:11000/oozie
Setting CATALINA_BASE:       /usr/local/oozie/oozie-server
Setting CATALINA_OUT:        /usr/local/oozie/logs/catalina.out
Setting CATALINA_PID:        /usr/local/oozie/oozie-server/temp/oozie.pid

Using   CATALINA_OPTS:
-Dderby.stream.error.file=/usr/local/oozie/logs/derby.log
Adding to CATALINA_OPTS:     -Doozie.home.dir=/usr/local/oozie
-Doozie.config.dir=/usr/local/oozie/conf
-Doozie.log.dir=/usr/local/oozie/logs
-Doozie.data.dir=/usr/local/oozie/data
-Doozie.config.file=oozie-site.xml
-Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10
-Doozie.http.hostname=computer10-MS-7211 -Doozie.http.port=11000
-Doozie.base.url=http://computer10-MS-7211:11000/oozie

Using CATALINA_BASE:   /usr/local/oozie/oozie-server
Using CATALINA_HOME:   /usr/local/apache-tomcat-7.0.42
Using CATALINA_TMPDIR: /usr/local/oozie/oozie-server/temp
Using JRE_HOME:        /usr/lib/jvm/jdk1.6.0_26
Using CLASSPATH:
/usr/local/oozie/oozie-server/bin/tomcat-juli.jar:/usr/local/apache-tomcat-7.0.42/bin/bootstrap.jar
Using CATALINA_PID:    /usr/local/oozie/oozie-server/temp/oozie.pid

Oozie started




bin/oozie-stop.sh

Setting OOZIE_HOME:          /usr/local/oozie
Setting OOZIE_CONFIG:        /usr/local/oozie/conf
Sourcing:                    /usr/local/oozie/conf/oozie-env.sh
Setting OOZIE_CONFIG_FILE:   oozie-site.xml
Setting OOZIE_DATA:          /usr/local/oozie/data
Setting OOZIE_LOG:           /usr/local/oozie/logs
Setting OOZIE_LOG4J_FILE:    oozie-log4j.properties
Setting OOZIE_LOG4J_RELOAD:  10
Setting OOZIE_HTTP_HOSTNAME: computer10-MS-7211
Setting OOZIE_HTTP_PORT:     11000
Setting OOZIE_BASE_URL:      http://computer10-MS-7211:11000/oozie
Setting CATALINA_BASE:       /usr/local/oozie/oozie-server
Setting CATALINA_OUT:        /usr/local/oozie/logs/catalina.out
Setting CATALINA_PID:        /usr/local/oozie/oozie-server/temp/oozie.pid

Using CATALINA_BASE:   /usr/local/oozie/oozie-server
Using CATALINA_HOME:   /usr/local/apache-tomcat-7.0.42
Using CATALINA_TMPDIR: /usr/local/oozie/oozie-server/temp
Using JRE_HOME:        /usr/lib/jvm/jdk1.6.0_26
Using CLASSPATH:
/usr/local/oozie/oozie-server/bin/tomcat-juli.jar:/usr/local/apache-tomcat-7.0.42/bin/bootstrap.jar
Using CATALINA_PID:    /usr/local/oozie/oozie-server/temp/oozie.pid

Oozie stopped

while starting   oozie
webconsole is : http://localhost:11000/oozie/

HTTP Status 404 -

type Status report

message

description The requested resource () is not available.
Apache Tomcat/6.0.32

  was:
Hi,
oozie is started and stop is correctly but while running the link it is
showing the error.(As a fresher I want try to learn about Oozie and i
want to execute the sample program)

While try to enter the oozie-setup,sh file it is showing
Oozie : webconsole is enable and extjs path is not specified
Oozie : oozie is started
Oozie : XXXXXXXXXXXXX

How can i get the solution please help me someone


    
> Webconsole
> ----------
>
>                 Key: OOZIE-1512
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1512
>             Project: Oozie
>          Issue Type: Bug
>          Components: client, examples, workflow
>    Affects Versions: 3.1.3
>         Environment: oozie-3.0.2-distro.tar
>            Reporter: SHOBAN
>            Priority: Minor
>              Labels: test
>             Fix For: trunk
>
>
> Hi,
> oozie is started and stop is correctly but while running the link it is
> showing the error.(As a fresher I want try to learn about Oozie and i
> want to execute the sample program)
>  bin/oozie-setup.sh
> INFO: Oozie webconsole disabled, ExtJS library not specified
> INFO: Doing default installation
> INFO: Oozie is ready to be started
> bin/oozie-start.sh
> Setting OOZIE_HOME:          /usr/local/oozie
> Setting OOZIE_CONFIG:        /usr/local/oozie/conf
> Sourcing:                    /usr/local/oozie/conf/oozie-env.sh
> Setting OOZIE_CONFIG_FILE:   oozie-site.xml
> Setting OOZIE_DATA:          /usr/local/oozie/data
> Setting OOZIE_LOG:           /usr/local/oozie/logs
> Setting OOZIE_LOG4J_FILE:    oozie-log4j.properties
> Setting OOZIE_LOG4J_RELOAD:  10
> Setting OOZIE_HTTP_HOSTNAME: computer10-MS-7211
> Setting OOZIE_HTTP_PORT:     11000
> Setting OOZIE_BASE_URL:      http://computer10-MS-7211:11000/oozie
> Setting CATALINA_BASE:       /usr/local/oozie/oozie-server
> Setting CATALINA_OUT:        /usr/local/oozie/logs/catalina.out
> Setting CATALINA_PID:        /usr/local/oozie/oozie-server/temp/oozie.pid
> Using   CATALINA_OPTS:
> -Dderby.stream.error.file=/usr/local/oozie/logs/derby.log
> Adding to CATALINA_OPTS:     -Doozie.home.dir=/usr/local/oozie
> -Doozie.config.dir=/usr/local/oozie/conf
> -Doozie.log.dir=/usr/local/oozie/logs
> -Doozie.data.dir=/usr/local/oozie/data
> -Doozie.config.file=oozie-site.xml
> -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10
> -Doozie.http.hostname=computer10-MS-7211 -Doozie.http.port=11000
> -Doozie.base.url=http://computer10-MS-7211:11000/oozie
> Using CATALINA_BASE:   /usr/local/oozie/oozie-server
> Using CATALINA_HOME:   /usr/local/apache-tomcat-7.0.42
> Using CATALINA_TMPDIR: /usr/local/oozie/oozie-server/temp
> Using JRE_HOME:        /usr/lib/jvm/jdk1.6.0_26
> Using CLASSPATH:
> /usr/local/oozie/oozie-server/bin/tomcat-juli.jar:/usr/local/apache-tomcat-7.0.42/bin/bootstrap.jar
> Using CATALINA_PID:    /usr/local/oozie/oozie-server/temp/oozie.pid
> Oozie started
> bin/oozie-stop.sh
> Setting OOZIE_HOME:          /usr/local/oozie
> Setting OOZIE_CONFIG:        /usr/local/oozie/conf
> Sourcing:                    /usr/local/oozie/conf/oozie-env.sh
> Setting OOZIE_CONFIG_FILE:   oozie-site.xml
> Setting OOZIE_DATA:          /usr/local/oozie/data
> Setting OOZIE_LOG:           /usr/local/oozie/logs
> Setting OOZIE_LOG4J_FILE:    oozie-log4j.properties
> Setting OOZIE_LOG4J_RELOAD:  10
> Setting OOZIE_HTTP_HOSTNAME: computer10-MS-7211
> Setting OOZIE_HTTP_PORT:     11000
> Setting OOZIE_BASE_URL:      http://computer10-MS-7211:11000/oozie
> Setting CATALINA_BASE:       /usr/local/oozie/oozie-server
> Setting CATALINA_OUT:        /usr/local/oozie/logs/catalina.out
> Setting CATALINA_PID:        /usr/local/oozie/oozie-server/temp/oozie.pid
> Using CATALINA_BASE:   /usr/local/oozie/oozie-server
> Using CATALINA_HOME:   /usr/local/apache-tomcat-7.0.42
> Using CATALINA_TMPDIR: /usr/local/oozie/oozie-server/temp
> Using JRE_HOME:        /usr/lib/jvm/jdk1.6.0_26
> Using CLASSPATH:
> /usr/local/oozie/oozie-server/bin/tomcat-juli.jar:/usr/local/apache-tomcat-7.0.42/bin/bootstrap.jar
> Using CATALINA_PID:    /usr/local/oozie/oozie-server/temp/oozie.pid
> Oozie stopped
> while starting   oozie
> webconsole is : http://localhost:11000/oozie/
> HTTP Status 404 -
> type Status report
> message
> description The requested resource () is not available.
> Apache Tomcat/6.0.32

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira