Hide Forgot
Description of problem: The daily log rotate is not enough, for example when configuring debug mode, and in parallel messages flood the log. On a setup with little space, after log was filled, and caused 100% of disk space, Postgresql service crashed (DB connection lost). Please consider some alternative mechanism for log rotate, in which log size is also taken under consideration. Version-Release number of selected component (if applicable): is20.1
Created attachment 817748 [details] engine_log
ls -ltrh total 850M drwxr-xr-x. 2 root root 4.0K Sep 5 22:27 ovirt-image-uploader drwxr-xr-x. 2 root root 4.0K Sep 7 17:09 ovirt-log-collector drwxr-xr-x. 2 ovirt ovirt 4.0K Oct 24 16:51 notifier drwxr-xr-x 2 ovirt ovirt 4.0K Oct 24 16:51 dump drwxr-xr-x. 2 root root 4.0K Oct 28 11:08 ovirt-iso-uploader drwxr-xr-x. 2 root root 4.0K Oct 30 12:17 setup drwxr-xr-x. 2 ovirt ovirt 4.0K Oct 30 13:00 host-deploy -rw-r--r-- 1 root root 6.8K Oct 30 13:04 engine-manage-domains.log -rw-r--r--. 1 root root 540K Oct 30 13:04 engine-config.log -rw-r--r--. 1 ovirt ovirt 0 Oct 31 09:26 console.log -rw-r--r--. 1 ovirt ovirt 875 Oct 31 09:26 boot.log -rw-r--r--. 1 ovirt ovirt 247K Oct 31 09:26 redhat-support-plugin-rhev.log -rw-r--r--. 1 ovirt ovirt 136M Oct 31 10:44 engine.log -rw-r--r--. 1 ovirt ovirt 662M Oct 31 10:44 server.log
Administrator is more than welcome to set logrotate service at higher interval.
(In reply to Alon Bar-Lev from comment #3) > Administrator is more than welcome to set logrotate service at higher > interval. Closing as not a bug as per comment #3.
See also the discussion in bug #948481 which triggered the move to logrotate.