Bug 999475
Summary: | Rotate engine.log by size not working - logrotate | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | vvyazmin <vvyazmin> |
Component: | ovirt-engine | Assignee: | Ofer Schreiber <oschreib> |
Status: | CLOSED DUPLICATE | QA Contact: | vvyazmin <vvyazmin> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | acathrow, alonbl, hateya, iheim, lpeer, oschreib, Rhev-m-bugs, vvyazmin, yeylon |
Target Milestone: | --- | Keywords: | Regression, Triaged |
Target Release: | 3.3.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-27 11:07:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
vvyazmin@redhat.com
2013-08-21 11:35:30 UTC
Workaround if engine.log is too large, run following command: logrotate --force /etc/logrotate.d/ovirt-engine Normally, linux logrotate runs once a day (by a cronjob), and is not size based (it has a minsize that tell logrotate the minimal size of log file to rotate). It looks like we're using the mechanism as intended, so I'm not sure why you wrote "Expected results: engine.log should rotate when log reached 10Mb" Why do you think that's the expected behaviour? Per bug#948481, ovirt-engine is now well behaved component, this means that logrotate is in charge of rotating log instead of proprietary rotation. It has many advantages, such as sysadmin to know what and how to change log rotation without digging into application, and at application side it reduces the need to maintain rotation logic and configuration. The disadvantage is that by default logrotation is executed once a day. On busy systems, log rotation can be executed in higher intervals, this is up to sysadmin to configure. Marking as duplicate of bug#948481. *** This bug has been marked as a duplicate of bug 948481 *** |