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

Hadoop QA commented on AMBARI-11332:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12734782/AMBARI-11332-1.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 patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.controller.internal.StackArtifactResourceProviderTest

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

This message is automatically generated.

> Ambari Server is not putting log in configured log directory
> ------------------------------------------------------------
>
>                 Key: AMBARI-11332
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11332
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Arshad Mohammad
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11332-1.patch
>
>
> Ambari Server logs are not created in configured log directory.
> In conf/log4j.properties following are configuration
> {code}
> ambari.log.dir=logs
> ambari.log.file=ambari-server.log
> {code}
> 1) When ambari-server.cmd setup is called, logs are generated in 
> {color:red}logsambari-server.log{color} file instead of  
> {color:green}logs/ambari-server.log {color}
> 2) When server starts, nothing is being logged in the log file



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

Reply via email to