You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "David Capwell (JIRA)" <ji...@apache.org> on 2015/01/18 00:47:34 UTC

[jira] [Commented] (BIGTOP-1607) Tachyon application logs in /var/lib rather than /var/log

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

David Capwell commented on BIGTOP-1607:
---------------------------------------

[~rvs] [~jayunit100] This is controlled by log4j and has the following in there

{code}
# vi /etc/tachyon/log4j.properties
...
log4j.appender.MASTER_LOGGER.File=${tachyon.home}/logs/master.log
...
log4j.appender.WORKER_LOGGER.File=${tachyon.home}/logs/worker.log
...
log4j.appender.USER_LOGGER.File=${tachyon.home}/logs/user.log
...
{code}

Im thinking that tachyon's log4j should not state tachyon.home but something like log.dir and the rpm overrides this value to point to /var/log/tachyon.  Does that make sense, or is there a better way to solve this?

> Tachyon application logs in /var/lib rather than /var/log
> ---------------------------------------------------------
>
>                 Key: BIGTOP-1607
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1607
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: David Capwell
>
> Looks like tachyon places the application logs in {{/var/lib/tachyon/logs/master.log\@172.17.0.3_01-17-2015}} rather than /var/log
> {code}
> bash-4.1# ls /var/log/tachyon/
> master.out  tachyon-master.out
> {code}



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