[
https://issues.apache.org/jira/browse/CLOUDSTACK-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359871#comment-14359871
]
Abhinandan Prateek commented on CLOUDSTACK-8325:
------------------------------------------------
Even after fixing the conf there are corner cases like someone manually deletes
the log file or during rotation time the file is open in an editor. Once the
log rotation fails due to one of these reasons the logger continues to write in
the intermediate file, all subsequent log rotation will fail as the main file
remains empty, this is exactly what is noted in few deployments.
The fix will be to write a post processing script that ensures that checks
primary as well as the intermediate log file and resets the logging if any of
those exceeds file size permitted.
> 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)
