[ https://issues.apache.org/jira/browse/CLOUDSTACK-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886858#comment-15886858 ]
ASF subversion and git services commented on CLOUDSTACK-9746: ------------------------------------------------------------- Commit fa85151be962824cc88776a0264e1ac6ef90560c in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fa85151 ] Merge release branch 4.9 to master * 4.9: CLOUDSTACK-9746 system-vm: logrotate config causes critical failures CLOUDSTACK-9788: Fix exception listNetworks with pagesize=0 CLOUDSTACK-8663: Fixed various issues to allow VM snapshots and volume snapshots to exist together Fix HVM VM restart bug in XenServer > 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)