ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1
Date Thu, 06 Oct 2016 16:16:20 GMT
Andrew Onischuk created AMBARI-18549:
----------------------------------------

             Summary: oozie server start fails post upgrade to Ambari 2.4.1
                 Key: AMBARI-18549
                 URL: https://issues.apache.org/jira/browse/AMBARI-18549
             Project: Ambari
          Issue Type: Bug
            Reporter: Andrew Onischuk
            Assignee: Andrew Onischuk
             Fix For: 2.4.2
         Attachments: AMBARI-18549.patch

====================================  
**Info**  
This cluster has gone through below upgrade.  
Ambari 2.2.2.0 - Ambari 2.4.1  
Cluster Details : <https://github.com/hortonworks/HCube#winchester-hdp-24>  
Please login with okta credential to these cluster machines  
====================================

On restarting Oozie web server from Ambari below error was thrown.

    
    
    
    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 215, in <module>
        OozieServer().execute()
      File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
        method(env)
      File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
line 100, 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 164, in oozie_service
        user = params.oozie_user)
      File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155,
in __init__
        self.env.run()
      File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line
160, in run
        self.run_action(resource, action)
      File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line
124, in run_action
        provider_action()
      File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 273, 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 71,
in inner
        result = function(command, **kwargs)
      File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 93,
in checked_call
        tries=tries, try_sleep=try_sleep)
      File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 141,
in _call_wrapper
        result = _call(command, **kwargs_copy)
      File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 294,
in _call
        raise Fail(err_msg)
    resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie && /usr/hdp/current/oozie-server/bin/oozied.sh
stop 60 -force' returned 1. -bash: line 0: cd: /var/tmp/oozie: No such file or directory
    

We had to workaround this problem by running oozie stop manual as below

    
    
    
    /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
    





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

Mime
View raw message