With the update to 5.019, the emailing of the nightly Executive Reports seems to have stopped functioning. This is occurring on every firewall running 5.019 that we manage.
[ QUOTE ] Nothing new yet. However, we did email our contacts in Astaro support and there's no reason to believe that they're not looking at this issue.
-Steve
[/ QUOTE ]
Confirmned bug here too. 5.019 is not mailing executive reports anymore.
I installed 5.019 on two ASL installs I have access to and did a reboot of both machines after the update. This evening, I recieved Exec Reports from both machines.
To me, it appears a simple reboot after installing 5.019 did the trick.
while awaiting a convenient time for reboot, i wonder if Astaro is working on this and a potential fix (which requires no reboot). i emailed their support and was informed we no longer have a valid support contract; unfortunately, no Astaro rep ever contacted to say "Heads up!" Valid license, no support. Bah humbug.
while awaiting a convenient time for reboot, i wonder if Astaro is working on this and a potential fix (which requires no reboot). i emailed their support and was informed we no longer have a valid support contract; unfortunately, no Astaro rep ever contacted to say "Heads up!" Valid license, no support. Bah humbug.
Yes, we are working on that. Besides doing postings in the UBB we also have a job to do, so writing that we work on something and working on something is mutually exclusive ;-)
For the last few days, we are trying to find the reason for that problem, but didn't quite get to the point of total enlightenment. It seems to be related to the cron daemon and|or the syslog daemon, but that still includes some guessing from my side. The problem is not even reproducable - some times it just works, without having changed anything, so it's giving us real trouble tracking down, although im sure it's just a minor problem which causes all that. I am convinced that it can be fixed without having to reboot, but since we are working on finding the source of the problem and not the best workaround for it, I don't have any workaround at hand of which I am 100% sure it works. If you are on the brink of rebooting your machine, you can try to restart the cron and syslog daemons instead. Maybe it is a workaround; if not, it can't hurt either.
By the way - You can trigger the sending of executive reports manually by typing "/usr/local/bin/report_render --sendmail" on the console.
