cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9746) system-vm: logrotate config causes critical failures
Date Tue, 21 Feb 2017 22:14:44 GMT

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

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

Github user dmabry commented on the issue:

    https://github.com/apache/cloudstack/pull/1915
  
    @serbaut Can you do a force push to kick off jenkins again.  I'm guessing Jenkins just
had an issue and not the PR.


> 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)

Mime
View raw message