[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2170:
-------------------------------------
Assignee: (was: Chris Nauroth)
Thank you for the patch, Arshad. Since you are working on this, I have
unassigned it from myself. I couldn't assign it to you though. Maybe you're
not listed in jira as a ZooKeeper contributor. A committer would be able to
help add your account as a contributor and get this assigned to you.
I applied this patch and built a distro locally with {{ant clean tar}}. I saw
a few potential problems.
# {{zkServer.sh start-foreground}} no longer logs to console. Seeing the logs
in the console is one of the primary reasons to run {{start-foreground}}.
# Running {{zkCli.sh}}, the logs are no longer going to the console.
# It looks like {{ZOO_LOG_FILE}} now can be user-specified in the environment,
and the scripts only override if it's not set. Is that required? If so, then
is the same change needed in {{zkCli.sh}}?
# Ideally, the same changes would be applied to the cmd scripts so that it's
consistent on Windows.
> Zookeeper is not logging as per the configuraiton in log4j.properties
> ----------------------------------------------------------------------
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Arshad Mohammad
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2170-002.patch, ZOOKEEPER-2170.001.patch
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
