dutchsnowden Posted Saturday at 04:48 PM Share Posted Saturday at 04:48 PM How can I check error logs and see what was this about? I run manually the task and I could see no errors and it completed succesfully... Link to comment Share on other sites More sharing options...
Daniel F Posted Saturday at 04:51 PM Share Posted Saturday at 04:51 PM Thx, we're aware of this. It happens only when the cleanup task is called via the cronjob dutchsnowden and SeNioR- 1 1 Link to comment Share on other sites More sharing options...
dutchsnowden Posted Saturday at 04:53 PM Author Share Posted Saturday at 04:53 PM Yes indeed, I setup cronjob for all background tasks. What I am supposed to do in the meantime. Just run it manually when it errs? Logs do not indicate any error... Link to comment Share on other sites More sharing options...
Jim M Posted Saturday at 05:00 PM Share Posted Saturday at 05:00 PM 6 minutes ago, dutchsnowden said: Yes indeed, I setup cronjob for all background tasks. What I am supposed to do in the meantime. Just run it manually when it errs? Logs do not indicate any error... This would be a known issue which will be resolved in a future release. You can do that if it clears it up but we will not have a fix till he future release, I'm afraid. SeNioR- and dutchsnowden 1 1 Link to comment Share on other sites More sharing options...
dutchsnowden Posted Saturday at 05:10 PM Author Share Posted Saturday at 05:10 PM Sure, that is understandable. I was just trying to find out what I need doing until then and/or what are the consequences. Link to comment Share on other sites More sharing options...
Marc Stridgen Posted Monday at 08:58 AM Share Posted Monday at 08:58 AM There is nothing you ned to be doing until then. dutchsnowden 1 Link to comment Share on other sites More sharing options...
Recommended Posts