[
https://issues.apache.org/jira/browse/CLOUDSTACK-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886862#comment-15886862
]
ASF subversion and git services commented on CLOUDSTACK-9746:
-------------------------------------------------------------
Commit 5604b4c59e73472d3aa14d08c27a9e1bf1a7948b in cloudstack's branch
refs/heads/4.8 from [~serbaut]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5604b4c ]
CLOUDSTACK-9746 system-vm: logrotate config causes critical failures
* rotate both daily and by size by using maxsize in stead of size
* decrease the max size to 10M for rsyslog files
* remove delaycompress for rsyslog files
* increase rotate to 10 for cloud.log
> system-vm: logrotate config causes critical failures
> ----------------------------------------------------
>
> Key: CLOUDSTACK-9746
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9746
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
> Affects Versions: 4.8.0, 4.9.0
> Reporter: Joakim Sernbrant
> Priority: Critical
>
> CLOUDSTACK-6885 changed logrotate from time based to size based. This means
> that logs will grow up to its size times two (due to delaycompress).
> For example:
> 50M auth.log
> 50M auth.log.1
> 10M cloud.log
> 10M cloud.log.1
> 50M cron.log
> 50M cron.log.1
> 50M messages
> 50M messages.1
> ...
> Some files will grow slowly but eventually they will get to their max size.
> The total allowed log size with the current config is well beyond the size of
> the log partition.
> Having a full /dev/log puts the VR in a state where operations on it
> critically fails.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
