[
https://issues.apache.org/jira/browse/AIRAVATA-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320844#comment-16320844
]
Marcus Christie commented on AIRAVATA-2608:
-------------------------------------------
Fixed the totalSizeCap by upgrading to latest logback 1.2.3. Now the property
is recognized
{noformat}
...
18:52:19,160 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming
appender as [LOGFILE]
18:52:19,162 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA
- Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder]
for [encoder] property
18:52:19,207 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@849373393 -
setting totalSizeCap to 1 GB
...
{noformat}
> Limit the size of airavata log fails
> ------------------------------------
>
> Key: AIRAVATA-2608
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2608
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
>
> gfacdev.scigap.org log files filled up available disk space. Currently log
> files are rotated but there is no automatic mechanism to delete older log
> files.
> [totalSizeCap|https://logback.qos.ch/manual/appenders.html#tbrpTotalSizeCap]
> looks like a good logback option to automatically delete older log files once
> a certain total filesize threshold is met by the log files.
> Also, I think it makes sense to turn off the CONSOLE logger. Not much sense
> to log to both the CONSOLE and the LOGFILE. Also, there is no way to
> configure log rotation in logback for what is written to CONSOLE. Rotating
> the stdout log file (output.log) requires some external tool.
> To rotate output.log we could use
> [logrotate|https://linux.die.net/man/8/logrotate] which is already available
> on centos.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
