[
https://issues.apache.org/jira/browse/CLOUDSTACK-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359861#comment-14359861
]
Abhinandan Prateek commented on CLOUDSTACK-8325:
------------------------------------------------
There are some more factors involved in log file rotation:
1. Currently the logrotate is placed in /etc/cron.daily so granularity is a run
per day.
2. size option is exclusive of rotation time and right now that is the right
option to use for what we want.
In one BT case #547 I noted that there are very old logs present in the the log
directly could it be because the logotate process is not working as expected ?
The script that we are writing to gather trouble shooting data, can it figure
out if the logrotate will work as expected and that there is no violation of it
by scanning log directory ?
> it is observed that the VR fails as the log files have taken up all the disk
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8325
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8325
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.3.2
> Reporter: Abhinandan Prateek
> Assignee: Abhinandan Prateek
> Priority: Critical
> Fix For: 4.6.0
>
>
> It is observed from support cases logged that the log files sometime grow so
> fast that they take away all the available disk space on the VR.
> It could happen because 1. Either log rotate did not happen in timely fashion
> 2. There was intensive logging due to repeated changes in firewall rules (or
> API calls).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
