You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Created) (JIRA)" <ji...@apache.org> on 2011/10/27 19:30:32 UTC

[jira] [Created] (BIGTOP-193) zookeeper doesn't generate any logs

zookeeper doesn't generate any logs
-----------------------------------

                 Key: BIGTOP-193
                 URL: https://issues.apache.org/jira/browse/BIGTOP-193
             Project: Bigtop
          Issue Type: Bug
          Components: General
    Affects Versions: 0.1.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.2.0


The root cause here is the setting in the /etc/zookeeper/conf/log4j.properties:
   log4j.rootLogger=INFO, CONSOLE

Basically all logging goes to the console and then gets redirected to /dev/null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-193) zookeeper doesn't generate any logs

Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik updated BIGTOP-193:
------------------------------------

    Attachment: BIGTOP-193.patch.txt
    
> zookeeper doesn't generate any logs
> -----------------------------------
>
>                 Key: BIGTOP-193
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-193
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>         Attachments: BIGTOP-193.patch.txt
>
>
> The root cause here is the setting in the /etc/zookeeper/conf/log4j.properties:
>    log4j.rootLogger=INFO, CONSOLE
> Basically all logging goes to the console and then gets redirected to /dev/null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-193) zookeeper doesn't generate any logs

Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138472#comment-13138472 ] 

Peter Linnell commented on BIGTOP-193:
--------------------------------------

+1  LGTM
                
> zookeeper doesn't generate any logs
> -----------------------------------
>
>                 Key: BIGTOP-193
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-193
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.1.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.2.0
>
>         Attachments: BIGTOP-193.patch.txt
>
>
> The root cause here is the setting in the /etc/zookeeper/conf/log4j.properties:
>    log4j.rootLogger=INFO, CONSOLE
> Basically all logging goes to the console and then gets redirected to /dev/null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira