ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-14220) Express Upgrades Fail To Stop Services Because Of Destroyed Configurations
Date Fri, 04 Dec 2015 20:35:11 GMT
Jonathan Hurley created AMBARI-14220:
----------------------------------------

             Summary: Express Upgrades Fail To Stop Services Because Of Destroyed Configurations
                 Key: AMBARI-14220
                 URL: https://issues.apache.org/jira/browse/AMBARI-14220
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Blocker
             Fix For: 2.2.0


*Steps:*
# Install Ambari 2.1.3 with HDP 2.1.15
# Modify DB tables for EU to be triggered
# Start Express Upgrade to HDP 2.3.4.0

*Result:*
EU failed while trying to stop Oozie server as part of "Stop Components for High Level Services"
step

{code}
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 195, in <module>
    OozieServer().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 217, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 85, in stop
    oozie_service(action='stop', upgrade_type=upgrade_type)
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk
    return fn(*args, **kwargs)
  File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
line 136, in oozie_service
    user = params.oozie_user)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 154, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 158,
in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 121,
in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line
238, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92, in checked_call
    tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140, in
_call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 291, in
_call
    raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie && /usr/lib/oozie/bin/oozie-stop.sh'
returned 126. WARN: Use of this script is deprecated; use 'oozied.sh stop' instead

Setting OOZIE_HOME:          /usr/lib/oozie
Using   OOZIE_CONFIG:        /etc/oozie/conf
Setting OOZIE_CONFIG_FILE:   oozie-site.xml
Setting OOZIE_DATA:          /usr/lib/oozie/data
Setting OOZIE_LOG:           /usr/lib/oozie/logs
mkdir: cannot create directory `/usr/lib/oozie/logs': Permission denied
Setting OOZIE_LOG4J_FILE:    oozie-log4j.properties
Setting OOZIE_LOG4J_RELOAD:  10
Setting OOZIE_HTTP_HOSTNAME: os-r6-ycmfcs-baikaltom20unsecr-re-3.novalocal
Setting OOZIE_HTTP_PORT:     11000
Setting OOZIE_ADMIN_PORT:     11001
Setting OOZIE_HTTPS_PORT:     11443
Setting OOZIE_BASE_URL:      http://os-r6-ycmfcs-baikaltom20unsecr-re-3.novalocal:11000/oozie
Setting CATALINA_BASE:       /usr/lib/oozie/oozie-server
Setting OOZIE_HTTPS_KEYSTORE_FILE:     /home/oozie/.keystore
Setting OOZIE_HTTPS_KEYSTORE_PASS:     password
Setting OOZIE_INSTANCE_ID:       os-r6-ycmfcs-baikaltom20unsecr-re-3.novalocal
Setting CATALINA_OUT:        /usr/lib/oozie/logs/catalina.out
Setting CATALINA_PID:        /usr/lib/oozie/oozie-server/temp/oozie.pid

Using   CATALINA_OPTS:        -Dderby.stream.error.file=/usr/lib/oozie/logs/derby.log
Adding to CATALINA_OPTS:     -Doozie.home.dir=/usr/lib/oozie -Doozie.config.dir=/etc/oozie/conf
-Doozie.log.dir=/usr/lib/oozie/logs -Doozie.data.dir=/usr/lib/oozie/data -Doozie.instance.id=os-r6-ycmfcs-baikaltom20unsecr-re-3.novalocal
-Doozie.config.file=oozie-site.xml -Doozie.log4j.file=oozie-log4j.properties -Doozie.log4j.reload=10
-Doozie.http.hostname=os-r6-ycmfcs-baikaltom20unsecr-re-3.novalocal -Doozie.admin.port=11001
-Doozie.http.port=11000 -Doozie.https.port=11443 -Doozie.base.url=http://os-r6-ycmfcs-baikaltom20unsecr-re-3.novalocal:11000/oozie
-Doozie.https.keystore.file=/home/oozie/.keystore -Doozie.https.keystore.pass=password -Djava.library.path=
/usr/lib/oozie/bin/oozied.sh: line 105: /usr/lib/oozie/oozie-server/bin/catalina.sh: No such
file or directory
/usr/lib/oozie/bin/oozied.sh: line 105: exec: /usr/lib/oozie/oozie-server/bin/catalina.sh:
cannot execute: No such file or directory
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message