Return-Path: <issues-return-26992-archive-asf-public=cust-asf.ponee.io@ambari.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 8D57D200B96
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Thu,  6 Oct 2016 18:25:23 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 8BE22160ADB; Thu,  6 Oct 2016 16:25:23 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id C61A5160AC5
	for <archive-asf-public@cust-asf.ponee.io>; Thu,  6 Oct 2016 18:25:22 +0200 (CEST)
Received: (qmail 84680 invoked by uid 500); 6 Oct 2016 16:25:21 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 84559 invoked by uid 99); 6 Oct 2016 16:25:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2016 16:25:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 953F22C2A69
	for <issues@ambari.apache.org>; Thu,  6 Oct 2016 16:25:20 +0000 (UTC)
Date: Thu, 6 Oct 2016 16:25:20 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13010201.1475770560000.754478.1475771120608@Atlassian.JIRA>
In-Reply-To: <JIRA.13010201.1475770560000@Atlassian.JIRA>
References: <JIRA.13010201.1475770560000@Atlassian.JIRA> <JIRA.13010201.1475770560389@arcas>
Subject: [jira] [Updated] (AMBARI-18549) oozie server start fails post
 upgrade to Ambari 2.4.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Thu, 06 Oct 2016 16:25:23 -0000


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

Andrew Onischuk updated AMBARI-18549:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.4 and branch-2.5

> 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)