dait Posted October 9, 2013 Report Share Posted October 9, 2013 I would like to request a feature that is related to a topic discussed here: http://www.blesta.com/forums/index.php?/topic/1052-system-status-there-are-one-or-more-cron-tasks-that-have-been-executing-for-more-than-60-minutes/ The current cron log contains very little information (task started, task finished). But if something bad happens, which could mean that some unusual condition was not handled properly (and this actually should be fixed to prevent cron task crashing), we have no information on what happened. Cron debug log would be handy here and could help us trace the causes of such events. The more information the better, so I can imagine two levels of logging, one enabled all the time, the second one enabled on demand, if we know that something goes wrong and need further information. Thanks for considering. Quote Link to comment Share on other sites More sharing options...
Tyson Posted October 9, 2013 Report Share Posted October 9, 2013 Cron tasks can fail for any number of reasons, including fatal errors, timeouts, infinite or continuous loops, etc., in which no data exists for Blesta to log. Blesta already logs what data it can. We plan to create a page of somesort to list out failed cron tasks so you can see what task is stalling and clear it, but additional information is not always available to explain why it stalled. Quote Link to comment Share on other sites More sharing options...
hsidhu Posted December 7, 2015 Report Share Posted December 7, 2015 Along with that If we could have log tables for plugin e.g log_plugin would be great. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.