[Users] Bug cron 3.3.1-2 ?

Hi, It seems, the ovirt-cron does something which does not work out of the box: From: Anacron <root(a)management.test&gt; To: root(a)management.test Content-Type: text/plain; charset="ANSI_X3.4-1968" Subject: Anacron job 'cron.daily' on management.test Message-Id: <20131025010702.1A48740038F(a)management.test&gt; Date: Fri, 25 Oct 2013 03:07:02 +0200 (CEST) /etc/cron.daily/ovirt-cron: ls: cannot access /var/log/ovirt-engine/server.log.*: No such file or directory ls: cannot access /var/log/ovirt-engine/jasperserver.log.*: No such file or directory ls: cannot access /var/log/ovirt-engine/server.log.*.gz: No such file or directory ls: cannot access /var/log/ovirt-engine/jasperserver.log.*.gz: No such file or directory Is this intended behaviour? ovirt-engine 3.3.1-2 on CentOS 6.4. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen