[
https://issues.apache.org/jira/browse/AMBARI-19000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702819#comment-15702819
]
Hadoop QA commented on AMBARI-19000:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840666/AMBARI-19000.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/9418//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9418//console
This message is automatically generated.
> Ambari-server fails to restart with --debug if it is already running
> --------------------------------------------------------------------
>
> Key: AMBARI-19000
> URL: https://issues.apache.org/jira/browse/AMBARI-19000
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19000.patch
>
>
> Using python /usr/bin/python
> Restarting ambari-server
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start.........
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code -1.
> REASON: Ambari Server java process died with exitcode 134. Check
> /var/log/ambari-server/ambari-server.out for more information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
