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

ASF GitHub Bot commented on CLOUDSTACK-9746:
--------------------------------------------

GitHub user serbaut opened a pull request:

    https://github.com/apache/cloudstack/pull/1915

    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 and reduce the number of kept files to a 
maximum of 5

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/serbaut/cloudstack CLOUDSTACK-9746

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1915.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1915
    
----
commit de9c0ab0a4cf31f097c9f7e7039add4240a62ac9
Author: Joakim Sernbrant <joakim.sernbr...@trioptima.com>
Date:   2017-01-23T11:13:15Z

    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 and reduce the number of kept files to a 
maximum of 5

----


> 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.4#6332)

Reply via email to