[ 
https://issues.apache.org/jira/browse/AMBARI-19851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850005#comment-15850005
 ] 

Hadoop QA commented on AMBARI-19851:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12850639/AMBARI-19851.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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 increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10379//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10379//console

This message is automatically generated.

> 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: <http://qelog.hortonworks.com/log/nat-yc-r7-sius-ambari-setup-hw-6
> /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)

Reply via email to