Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

How to start and restart the oozie daeomon in the 5.4.x Quickstart VM?

How to start and restart the oozie daeomon in the 5.4.x Quickstart VM?

Contributor

As mentioned in my (currently unanswered) previous post about  Oozie Best practices for testing custom actions , I want to test a custom action for Oozie without using our production cluster.  Hence, I would like to add the jar I have created to the Oozie war file using the oozie-setup.sh script.

  1. Am I right that I should first stop the oozie daemon before doing this? 
  2. How can I do this?  When I try the expected command, oozied.sh,  I get the error shown below.

As per the Oozie quick start guide (see the Servier Installation section) which reads:

"IMPORTANT: all Oozie server scripts (=oozie-setup.sh=, oozied.sh , oozie-start.sh , oozie-run.sh and oozie-stop.sh ) run only under the Unix user that owns the Oozie installation directory, if necessary use sudo -u OOZIE_USER when invoking the scripts.

 

 

I check the ownership and run the command in a sudo so we see the following failure in trying to stop oozie via oozied.sh:

 

[cloudera@quickstart testdir]$ ls -la /usr/lib/oozie/bin/oozied.sh
-rwxr-xr-x 1 root root 3516 Apr 21 12:24 /usr/lib/oozie/bin/oozied.sh

sudo /usr/lib/oozie/bin/oozied.sh stop

Setting OOZIE_HOME: /usr/lib/oozie
Sourcing: /usr/lib/oozie/bin/oozie-env.sh
setting JAVA_LIBRARY_PATH="$JAVA_LIBRARY_PATH:/usr/lib/hadoop/lib/native"
setting OOZIE_DATA=/var/lib/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=/var/lib/oozie/tomcat-deployment
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 CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m"
setting OOZIE_CONFIG=/etc/oozie/conf
setting OOZIE_LOG=/var/log/oozie
Using OOZIE_CONFIG: /etc/oozie/conf
Sourcing: /etc/oozie/conf/oozie-env.sh
setting JAVA_LIBRARY_PATH="$JAVA_LIBRARY_PATH:/usr/lib/hadoop/lib/native"
setting OOZIE_DATA=/var/lib/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=/var/lib/oozie/tomcat-deployment
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 CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m"
setting OOZIE_CONFIG=/etc/oozie/conf
setting OOZIE_LOG=/var/log/oozie
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: quickstart.cloudera
Setting OOZIE_HTTP_PORT: 11000
Setting OOZIE_ADMIN_PORT: 11001
Using OOZIE_HTTPS_PORT: 11443
Setting OOZIE_BASE_URL: http://quickstart.cloudera:11000/oozie
Using CATALINA_BASE: /var/lib/oozie/tomcat-deployment
Setting OOZIE_HTTPS_KEYSTORE_FILE: /root/.keystore
Using OOZIE_HTTPS_KEYSTORE_PASS: password
Setting OOZIE_INSTANCE_ID: quickstart.cloudera
Setting CATALINA_OUT: /var/log/oozie/catalina.out
Using CATALINA_PID: /var/run/oozie/oozie.pid

Using CATALINA_OPTS: -Doozie.https.port=11443 -Doozie.https.keystore.pass=password -Xmx1024m -Doozie.https.port=11443 -Doozie.https.keystore.pass=password -Xmx1024m -Dderby.stream.error.file=/var/log/oozie/derby.log
Adding 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.instance.id=quickstart.cloudera -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10 -Doozie.http.hostname=quickstart.cloudera -Doozie.admin.port=11001 -Doozie.http.port=11000 -Doozie.https.port=11443 -Doozie.base.url=http://quickstart.cloudera:11000/oozie -Doozie.https.keystore.file=/root/.keystore -Doozie.https.keystore.pass=password -Djava.library.path=:/usr/lib/hadoop/lib/native:/usr/lib/hadoop/lib/native
Using CATALINA_BASE: /var/lib/oozie/tomcat-deployment
Using CATALINA_HOME: /usr/lib/bigtop-tomcat
Using CATALINA_TMPDIR: /var/lib/oozie
Using JRE_HOME: /usr
Using CLASSPATH: /usr/lib/bigtop-tomcat/bin/bootstrap.jar
Using CATALINA_PID: /var/run/oozie/oozie.pid
$CATALINA_PID was set but the specified file does not exist. Is Tomcat running? Stop aborted.

 

Thanks for any help on this issue or the previous questin about testing methodology.

 

1 REPLY 1
Highlighted

Re: How to start and restart the oozie daeomon in the 5.4.x Quickstart VM?

Contributor

I found out how to do this it in the cloudera Manager, in my case I did the following:

  1. Launch the Cloudera Managaer - double click on the Launch Cloud Manager icon on the VM's virtual desktop.
  2. Point the firefox browser in the VM to http://quickstart.cloudera:7180/cmf/home and using the GUI to control the service (via the drop down tabls on the rigth edge of the rows in the table for the servicces) do the following:  i) stop Hue (which depends on oozie) and ii) stop Oozie.

Restart is also done through the GUI, here the order is reviersed:

  1. Restart Ooizie
  2. Restart Hue

 

On a  side note I tried and failed with (command line tools like "sudo service oozie start|stop|status" didn't work for me, so the Cloudera 4.7.1 oozie service management documentation no longer holds.