You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/12/10 02:01:20 UTC

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

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

Chris Nauroth commented on ZOOKEEPER-2342:
------------------------------------------

To reproduce the issue, run {{ant clean tar}} on the tip of current trunk, unpack the distro, copy zoo_sample.cfg to zoo.cfg, and then run it.  Both {{zkServer.sh start-foreground}} and {{zkCli.sh}} will show this error:

{code}
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
{code}

There will be no additional logging after that.

> ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.
> --------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2342
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Chris Nauroth
>            Priority: Blocker
>             Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that this also removed the Log4J SLF4J binding jar from the runtime classpath.  Without any SLF4J binding jar available on the runtime classpath, the it is impossible to write logs.



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