Under Review

Better logging for failed schedulers

Currently the scheduler interface just shows if a job is done or not. It does not show if it failed and why.

It would be nice to have individual logs for scheduler jobs accessible from the Scheduler interface. At the very least the resolution and message fields from the job_queue should be included in the Job Log.

The two main messages I see in the database for failed jobs are "Forced failure on timeout" and "Unexpected failure, please check PHP logs and sugarcrm.log"

Whenever I get an "unexpected failure" there is never any indication of anything wrong in either the PHP or sugarcrm logs and it often leaves me wondering what caused it. I realize it's near impossible to catch everything under the sun but is there a way to give more information to the administrator than "unexpected failure"?

Thank you,

FrancescaS

Parents
  • Currently I use on a Windows server the following scheduler.cmd for monthly logs starting with "yyyy-mm-":

    @echo off
    SET DELIMITER=-
    SET DATESTRING=%date:~-4,4%%DELIMITER%%date:~-7,2%%DELIMITER%
    c:
    cd \xampp\htdocs\sugarent800\
    c:\xampp\php\php.exe -f cron.php >>%DATESTRING%cron.out 2>>%DATESTRING%cron.err

    cd \xampp\htdocs\

Comment
  • Currently I use on a Windows server the following scheduler.cmd for monthly logs starting with "yyyy-mm-":

    @echo off
    SET DELIMITER=-
    SET DATESTRING=%date:~-4,4%%DELIMITER%%date:~-7,2%%DELIMITER%
    c:
    cd \xampp\htdocs\sugarent800\
    c:\xampp\php\php.exe -f cron.php >>%DATESTRING%cron.out 2>>%DATESTRING%cron.err

    cd \xampp\htdocs\

Children
No Data