[
https://issues.apache.org/jira/browse/AMBARI-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555905#comment-14555905
]
Arshad Mohammad commented on AMBARI-11332:
------------------------------------------
The problem is because of single backward slash used instead of double backward
slash in bellow lines of log4j.properties
{code}
log4j.appender.DRFA.File=${ambari.log.dir}\${ambari.log.file}
log4j.appender.configchange.File=${ambari.log.dir}\${ambari.config-changes.file}
log4j.appender.alerts.File=${ambari.log.dir}\${ambari.alerts.file}
{code}
This may be a small configuration issue which can user can change to make it
work but by default the configuration should be corrected.
> 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
>
>
> 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)
