Return-Path: 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 AAB8F200D2A for ; Sat, 14 Oct 2017 05:53:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A90B8160BE5; Sat, 14 Oct 2017 03:53:10 +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 F05A01609E9 for ; Sat, 14 Oct 2017 05:53:09 +0200 (CEST) Received: (qmail 15688 invoked by uid 500); 14 Oct 2017 03:53:08 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 15679 invoked by uid 99); 14 Oct 2017 03:53:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Oct 2017 03:53:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B9247180898 for ; Sat, 14 Oct 2017 03:53:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id dbm1xPE-0osT for ; Sat, 14 Oct 2017 03:53:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 311E05F3CE for ; Sat, 14 Oct 2017 03:53:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C7FB5E04F4 for ; Sat, 14 Oct 2017 03:53:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 13EF421EE3 for ; Sat, 14 Oct 2017 03:53:00 +0000 (UTC) Date: Sat, 14 Oct 2017 03:53:00 +0000 (UTC) From: "Jayush Luniya (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-22237) Restarting Storm Supervisor from Ambari always fails while Stop and Start works fine MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 14 Oct 2017 03:53:10 -0000 [ https://issues.apache.org/jira/browse/AMBARI-22237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204462#comment-16204462 ] Jayush Luniya commented on AMBARI-22237: ---------------------------------------- +1 > Restarting Storm Supervisor from Ambari always fails while Stop and Start works fine > ------------------------------------------------------------------------------------ > > Key: AMBARI-22237 > URL: https://issues.apache.org/jira/browse/AMBARI-22237 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.5.0 > Environment: CentOS-6 (64 Bit) > Reporter: Arpit Khare > Assignee: Siddharth Wagle > Attachments: AMBARI-22237.patch, errors.txt, supervisor-start.txt, supervisor-stop.txt > > > We have Storm configured for supervision. When we restart Storm Supervisor from Ambari it always fails with the following stderr [^errors.txt]: > {code} > Traceback (most recent call last): > File "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor_prod.py", line 84, in > Supervisor().execute() > File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 314, in execute > method(env) > File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 751, in restart > self.status(env) > File "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor_prod.py", line 73, in status > supervisord_check_status("supervisor") > File "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisord_service.py", line 33, in supervisord_check_status > except Fail: > NameError: global name 'Fail' is not defined > {code} > While when we stop [^supervisor-stop.txt] and start [^supervisor-stop.txt] the supervisor we do not get any error and it works fine. Only restart is the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)