Dmytro Shkvyra created AMBARI-4844:
--------------------------------------
Summary: Oozie server restart fails on stack 1.3.3 with message
"ERROR: Stop Oozie first"
Key: AMBARI-4844
URL: https://issues.apache.org/jira/browse/AMBARI-4844
Project: Ambari
Issue Type: Bug
Components: controller
Affects Versions: 1.5.0
Environment: CentOS 6.4, stack 1.3.3
ambari-server --version
1.5.0.42
ambari-server --hash
65249796f42e45216ce5463b4d7bb0024a7a5bcd
Reporter: Dmytro Shkvyra
Fix For: 1.5.0
*STR:*
1. Install, setup and start Ambari server by default.
2. Deploy Hadoop with all services.
3. Apply action "Restart" to Oozie Server.
4. Check host for Oozie process existing.
5. Start Oozie Server.
*Actual results:*
1. Operation "Restart Oozie Servers" fails with output:
{noformat}
stderr: /var/lib/ambari-agent/data/errors-105.txt
setting CATALINA_BASE=${CATALINA_BASE:-/var/lib/oozie/oozie-server}
setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
setting CATALINA_PID=${CATALINA_PID:-/var/run/oozie/oozie.pid}
setting JAVA_HOME=/usr/jdk64/jdk1.7.0_45
setting OOZIE_LOG=/grid/0/log/oozie
setting CATALINA_PID=/var/run/oozie/oozie.pid
setting OOZIE_DATA=/hadoop/oozie/data
setting JAVA_LIBRARY_PATH=/usr/lib/hadoop/lib/native/Linux-amd64-64
ERROR: Stop Oozie first
stdout: /var/lib/ambari-agent/data/output-105.txt
setting CATALINA_BASE=${CATALINA_BASE:-/var/lib/oozie/oozie-server}
setting CATALINA_TMPDIR=${CATALINA_TMPDIR:-/var/tmp/oozie}
setting CATALINA_PID=${CATALINA_PID:-/var/run/oozie/oozie.pid}
setting JAVA_HOME=/usr/jdk64/jdk1.7.0_45
setting OOZIE_LOG=/grid/0/log/oozie
setting CATALINA_PID=/var/run/oozie/oozie.pid
setting OOZIE_DATA=/hadoop/oozie/data
setting JAVA_LIBRARY_PATH=/usr/lib/hadoop/lib/native/Linux-amd64-64
ERROR: Stop Oozie first
{noformat}
2. On step 4 commands execution result:
{noformat}
[root@c6402 ~]# cat /var/run/oozie/oozie.pid
25056
[root@c6402 ~]# ps aux | grep 25056
root 26783 0.0 0.0 103260 904 pts/0 S+ 11:57 0:00 grep 25056
{noformat}
3. "Start Oozie Server" fails with similar error message.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)