You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Will McQueen (Created) (JIRA)" <ji...@apache.org> on 2012/04/04 01:46:23 UTC
[jira] [Created] (BIGTOP-510) log4j property must be set with
property in for Flume NG pkg
log4j property must be set with property in for Flume NG pkg
------------------------------------------------------------
Key: BIGTOP-510
URL: https://issues.apache.org/jira/browse/BIGTOP-510
Project: Bigtop
Issue Type: Bug
Components: General
Affects Versions: 0.3.0
Environment: [CentOS 5.7 64-bit]
Reporter: Will McQueen
Assignee: Bruno Mahé
Fix For: 0.3.0
The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
flume.log.dir=/var/log/flume-ng
Thank you.
--
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-510) log4j property must be set with
property in for Flume NG pkg
Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252121#comment-13252121 ]
Bruno Mahé commented on BIGTOP-510:
-----------------------------------
Thanks!
I will add a fixme before commiting this
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-510.patch
>
>
> The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
> flume.log.dir=/var/log/flume-ng
> Thank you.
--
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-510) log4j property must be set with
property in for Flume NG pkg
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246002#comment-13246002 ]
Roman Shaposhnik commented on BIGTOP-510:
-----------------------------------------
Wouldn't it be possible to parameterize log4j.properties upstream in such a way that it would allow overrides from the command line via -Dfoo=bar ? We do it for most of the components and it works fine without changing the content of the upstream file.
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Fix For: 0.3.0
>
>
> The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
> flume.log.dir=/var/log/flume-ng
> Thank you.
--
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-510) log4j property must be set with
property in for Flume NG pkg
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252118#comment-13252118 ]
Roman Shaposhnik commented on BIGTOP-510:
-----------------------------------------
I *really* would like it to be fixed upstream and at least have a big fat FIXME in Bigtop's code
otherwise looks good
+1
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-510.patch
>
>
> The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
> flume.log.dir=/var/log/flume-ng
> Thank you.
--
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-510) log4j property must be set with
property in for Flume NG pkg
Posted by "Mike Percy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245939#comment-13245939 ]
Mike Percy commented on BIGTOP-510:
-----------------------------------
Maybe we can just cd /var/log/flume-ng instead of replacing the file. I'm concerned about not being able to gracefully incorporate changes to the logger defaults across Flume releases if we do a complete replacement.
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Fix For: 0.3.0
>
>
> The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
> flume.log.dir=/var/log/flume-ng
> Thank you.
--
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-510) log4j property must be set with
property in for Flume NG pkg
Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252124#comment-13252124 ]
Peter Linnell commented on BIGTOP-510:
--------------------------------------
+1 LGTM
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-510.patch
>
>
> The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
> flume.log.dir=/var/log/flume-ng
> Thank you.
--
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-510) log4j property must be set with
property in for Flume NG pkg
Posted by "Bruno Mahé (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruno Mahé updated BIGTOP-510:
------------------------------
Attachment: BIGTOP-510.patch
Here is a patch.
Tested locally the content is indeed modified and set to the right location
> log4j property must be set with property in for Flume NG pkg
> ------------------------------------------------------------
>
> Key: BIGTOP-510
> URL: https://issues.apache.org/jira/browse/BIGTOP-510
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.3.0
> Environment: [CentOS 5.7 64-bit]
> Reporter: Will McQueen
> Assignee: Bruno Mahé
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-510.patch
>
>
> The /etc/flume-ng/log4j.properties file is configured by default to write to the current dir, which causes perms issues when the /etc/init.d/flume-ng-node daemon (running as user 'flume') attempts to write it. A fix would be to provide log4j.properties so that the property's value specifies /var/log/flume-ng as the log dir, like this:
> flume.log.dir=/var/log/flume-ng
> Thank you.
--
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