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 9B17C200C1F for ; Fri, 3 Feb 2017 14:05:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 998B9160B48; Fri, 3 Feb 2017 13:05:00 +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 EAA80160B55 for ; Fri, 3 Feb 2017 14:04:59 +0100 (CET) Received: (qmail 93987 invoked by uid 500); 3 Feb 2017 13:04:58 -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 93978 invoked by uid 99); 3 Feb 2017 13:04:58 -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; Fri, 03 Feb 2017 13:04:58 +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 C988A18231E for ; Fri, 3 Feb 2017 13:04:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Mx_DNzs5Vu-v for ; Fri, 3 Feb 2017 13:04:54 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9CB585F3A1 for ; Fri, 3 Feb 2017 13:04:53 +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 818B7E05B1 for ; Fri, 3 Feb 2017 13:04:52 +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 BFD4825292 for ; Fri, 3 Feb 2017 13:04:51 +0000 (UTC) Date: Fri, 3 Feb 2017 13:04:51 +0000 (UTC) From: "Andrew Onischuk (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-19851) ambari-server start failed with exit code 1. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 03 Feb 2017 13:05:00 -0000 [ https://issues.apache.org/jira/browse/AMBARI-19851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19851: ------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > ambari-server start failed with exit code 1. > -------------------------------------------- > > Key: AMBARI-19851 > URL: https://issues.apache.org/jira/browse/AMBARI-19851 > Project: Ambari > Issue Type: Bug > Reporter: Andrew Onischuk > Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19851.patch > > > Found this issue in ST. > Trying to provide setup ambari-server and > > > [root@ctr-e126-1485243696039-17812-01-000004 ~]# ambari-server setup -s > Using python /usr/bin/python > Setup ambari-server > Nothing was done. Ambari Setup already performed and cannot re-run setup in silent mode. Use "ambari-server setup" command without -s option to change Ambari setup. > > Trying to start ambari-server > > > [root@ctr-e126-1485243696039-17812-01-000004 ~]# ambari-server start > Using python /usr/bin/python > Starting ambari-server > ERROR: Exiting with exit code 1. > REASON: Unable to detect a system user for Ambari Server. > - If this is a new setup, then run the "ambari-server setup" command to create the user > - If this is an upgrade of an existing setup, run the "ambari-server upgrade" command. > Refer to the Ambari documentation for more information on setup and upgrade. > > Ambari-server restart in debug log > > > 2017-02-01 04:36:34,630 DEBUG com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): Sending command [ambari-server restart --debug] > 2017-02-01 04:36:35,331 DEBUG com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence(): [OUTPUT STREAM] > Using python /usr/bin/python > Restarting ambari-server > Ambari Server is not running > ERROR: Exiting with exit code 1. > REASON: Unable to detect a system user for Ambari Server. > - If this is a new setup, then run the "ambari-server setup" command to create the user > - If this is an upgrade of an existing setup, run the "ambari-server upgrade" command. > Refer to the Ambari documentation for more information on setup and upgrade. > **ambari-server setup** without -s setup ambari successful and ambari-server start passed. > artifacts: /test-logs/ambari-setup-hw/artifacts/screenshots/com.hw.ambari.ui.tests.consol > e.TestInstallSeparateSSLCertificate/testA_InstallSeparateSSLCertificate/_1_4_4 > 0_52_Element_has_not_been_found_within_60_seconds__/> > cluster: 172.27.30.144 -- This message was sent by Atlassian JIRA (v6.3.15#6346)