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 15BD9200B8F for ; Fri, 30 Sep 2016 14:07:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 14535160AD9; Fri, 30 Sep 2016 12:07:22 +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 5A920160AC4 for ; Fri, 30 Sep 2016 14:07:21 +0200 (CEST) Received: (qmail 58632 invoked by uid 500); 30 Sep 2016 12:07:20 -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 58621 invoked by uid 99); 30 Sep 2016 12:07:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2016 12:07:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 6F7D02C0057 for ; Fri, 30 Sep 2016 12:07:20 +0000 (UTC) Date: Fri, 30 Sep 2016 12:07:20 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-18501) If ambari-server fails to start, appropriate error message should be displayed. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 30 Sep 2016 12:07:22 -0000 [ https://issues.apache.org/jira/browse/AMBARI-18501?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15= 535815#comment-15535815 ]=20 Hadoop QA commented on AMBARI-18501: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest= attachment=20 http://issues.apache.org/jira/secure/attachment/12831094/AMBARI-18501.pat= ch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author= tags. {color:green}+1 tests included{color}. The patch appears to include 1 = new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not incre= ase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in amba= ri-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8776//t= estReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8776/= /console This message is automatically generated. > If ambari-server fails to start, appropriate error message should be disp= layed. > -------------------------------------------------------------------------= ------ > > Key: AMBARI-18501 > URL: https://issues.apache.org/jira/browse/AMBARI-18501 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.5.0 > Reporter: Vitaly Brodetskyi > Assignee: Vitaly Brodetskyi > Fix For: 3.0.0 > > Attachments: AMBARI-18501.patch > > > If due to some error, ambari-server JAR exits with -1, we still display = =E2=80=9CAmbari Server =E2=80=98start=E2=80=99 completed successfully=E2=80= =9D > In AmbariServer.java::main(), if an exception occurs, the program exits w= ith -1. Howerver, the caller ambari-server.py::main() displays the status m= essage as "Ambari Server 'start' completed successfully". -- This message was sent by Atlassian JIRA (v6.3.4#6332)