failing crons must report properly

[Ferdinand]

currently crons fail quietly
IMHO there should be a default notification function (sending a requst or mail to the job owner od a dedicated user) which runs if the cron job fails.

I see a problem sending requests to the administrator, because this account will not be used regulary

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Hello,

we came to the same suggestion in an ecommerce project where we were exporting products to the external ecommerce front end using crons, we would have liked failing cron to generate requests or something like that. Still, I see no easy solution with the problem of reporting to the admin. May be the cron object could have some extra optionnal field, report_ti_user_id and if it's set, it makes a request to that user; if no user is set, it reports to admin; or say it's admin by default and it's mandatory. Just suggestions. Thoughts?

[Jay Vora (Serpent Consulting Services) (jayvora)]

Experts,
This has been improved both on stable and trunk.

Would you please check and share a thought?

Thanks.

[Ferdinand (office-chricar)]

please tell us where the error messages of failed crons are made visible

[Nhomar - Vauxoo (nhomar)]

Please jay, can you tell us a little how can we check what do you made or on what revid it was done.

regards.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello Experts,

Looking at the code, _poolJobs and _callbackl methods have been improved for the same.

You may check this revision which was linked to this bug:

http://bazaar.launchpad.net/~openerp/openobject-server/5.0/revision/1860.1.7

We would be interested to know if this bug still harasses.

Thanks.

[Anup(SerpentCS) (anup-serpent)]

Hello,

     Our R&D Teams are focused on the latest OpenERP version, and this issue does not affect it. Our policy is to keep the changes applied on stable branches to a minimum, in order to limit the regression risks for customers that are in production. This means that bugs reported on Launchpad are fixed in the trunk branch only by default, even if they were reported against other stable versions.

     We stand of course ready to backport the change to stable releases if it has an impact on any customer. In this case please report it to our maintenance team via the OpenERP Publisher's Warranty. They will quickly help solve the issue and backport the fix if needed.

Thank you for your understanding!

[Jay Vora (Serpent Consulting Services) (jayvora)]

I would be interested to know an illustrative situation where I can face this on trunk.
Thanks.

[Ferdinand (office-chricar)]

we start linux shell scripts - if these fail it should be reported in OpenERP (as a request?)

[Olivier Dony (Odoo) (odo-openerp)]

Currently in OpenERP (v5/v6), it is the responsability of the cron job to do its own error-management and reporting.
As you noted yourself, it allows you to implement a much appropriate solution than a default notification mechanism.

We could consider implementing a default mechanism for this after v6, so I leave it open as Wishlist. Although ultimately the most flexible way will still be to do it properly in the cron job itself.

Thank you for this suggestion