[
https://issues.apache.org/jira/browse/AMBARI-9851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341762#comment-14341762
]
Hadoop QA commented on AMBARI-9851:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701619/AMBARI-9851.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1861//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1861//console
This message is automatically generated.
> "ambari-server start command" hangs if was executed via ssh command
> -------------------------------------------------------------------
>
> Key: AMBARI-9851
> URL: https://issues.apache.org/jira/browse/AMBARI-9851
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.0.0
> Environment: Ubuntu
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9851.patch
>
>
> When executing {{ambari-server start}} command via ssh, process hangs.
> Reproducible only when executing ambari-server start without login only on
> Ubuntu
> {code}
> andrew@pc:~/vagrant/ubuntu12.4$ ssh -i ../insecure_private_key root@u1201
> "ambari-server start"
> Using python /usr/bin/python2.7
> Starting ambari-server
> Ambari Server running with 'root' privileges.
> About to start PostgreSQL
> Organizing resource files at /var/lib/ambari-server/resources...
> 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....................
> Ambari Server 'start' completed successfully.
> {code}
> User need to drop ssh connection afterwards.
> This affects our QA automation tests, because we need to create workaround
> for it.
> Per my investigations, in tests we can now make something like:
> {code}
> ssh root@host "ambari-server start < /dev/null > /tmp/ambari-start-log 2>&1 &"
> {code}
> But this will breaks our ability for easily checking outputs of ambari-server
> We had similar bug before, but for different OS
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
