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

Hadoop QA commented on AMBARI-19061:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12841443/AMBARI-19061.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/9494//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9494//console

This message is automatically generated.

> Ambari-server restart command not working. if any parameters are changed and 
> reset to default. 
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19061
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19061
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19061.patch
>
>
> **Steps to reproduce:**  
> 1\. Change any of the parameters that hamper the ambari-server to restart
> successfully.(password.dat file)  
> 2\. Restart ambari-server, ambari-server restart will fail saying (This is
> expected as we have changed the parameter.)
>     
>     
>     
>     Unable to determine server PID. Retrying...
>     DB configs consistency check: no errors and warnings were found.
>     ERROR: Exiting with exit code -1. 
>     
> 3\. Now set the Parameter to its actual value.  
> 4.Restart ambari-server, ambari-server restart will fail saying
>     
>     
>     
>     Using python  /usr/bin/python
>     Restarting ambari-server
>     WARNING: '' is incorrect PID value. 
> /var/run/ambari-server/ambari-server.pid is corrupt. Removing
>     Ambari Server 'restart' completed with warnings.
>     
> 5.If you Restart the Ambari server again. It gets restarted successfully.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to