Description of problem: /etc/cron.daily/tmpwatch had deleted files which are not modified for more than 30 days from "/var/tmp/ovirt-engine/". This created issue with ovirt-engine (RHEV) service and it stopped functioning. Thus affecting customer's production environment Version-Release number of selected component (if applicable): tmpwatch-2.9.16-4.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. start ovirt-engine service 2. Make sure tmpwatch daily cronjob is running (/etc/cron.daily/tmpwatch) Actual results: After 30 days, tmpwatch will delete files which are not modified from /var/tmp/ovirt-engine/ Expected results: tmpwatch should exclude /var/tmp/ovirt-engine/ from its cleaning process. Additional info: Suggested the following workaround till the issue is resolved. Modify ' /usr/sbin/tmpwatch "$flags" 30d /var/tmp ' to ' /usr/sbin/tmpwatch "$flags" -x /var/tmp/ovirt-engine 30d /var/tmp ' (this will exclude /var/tmp/ovirt-engine)
Why is (In reply to Anil Vettathu from comment #0) > After 30 days, tmpwatch will delete files which are not modified from > /var/tmp/ovirt-engine/ No, it will delete files which are not _accessed_ for 30 days. Why is ovirt-engine storing long-term data in there in the first place? AFAICT it shouldn’t, contents of /var/tmp are explicitly expected to be deleted at unpredictable time per http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE50 .
I do not expect blind periodic delete /var/tmp, however it is easy enough to move this tmp to /var/lib/ovirt-engine/tmp. You can now set ENGINE_TMP within /etc/ovirt-engine/engine.conf/30-tmpdir.conf: ENGINE_TMP="${ENGINE_VAR}/tmp"
Sandro, When sending modification, please separate between the jboss tmp layout and the tmpdir, make the jboss layout reside at lib. Thanks,
(In reply to Alon Bar-Lev from comment #2) > I do not expect blind periodic delete /var/tmp, however it is easy enough to > move this tmp to /var/lib/ovirt-engine/tmp. > > You can now set ENGINE_TMP within > /etc/ovirt-engine/engine.conf/30-tmpdir.conf: > > ENGINE_TMP="${ENGINE_VAR}/tmp" Sorry... forgot the .d /etc/ovirt-engine/engine.conf.d/30-tmpdir.conf: --- ENGINE_TMP="${ENGINE_VAR}/tmp" ---
(In reply to Alon Bar-Lev from comment #3) > Sandro, > When sending modification, please separate between the jboss tmp layout and > the tmpdir, make the jboss layout reside at lib. Why not move all of ENGINE_TMP to lib? Is there anything that must stay at /var/tmp ?
(In reply to Yedidyah Bar David from comment #10) > (In reply to Alon Bar-Lev from comment #3) > > Sandro, > > When sending modification, please separate between the jboss tmp layout and > > the tmpdir, make the jboss layout reside at lib. > > Why not move all of ENGINE_TMP to lib? Is there anything that must stay at > /var/tmp ? please leave the ENGINE_TMP within /var/tmp/ovirt-engine, it may have other uses, please have a different variable for the jboss layout.
http://gerrit.ovirt.org/29752 is for ovirt-reports.
ok, looks for for engine (ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch) and reports (ovirt-engine-reports-3.5.0-0.5.el6.noarch.rpm).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html