For some time, I am facing some strange issue that cron is starting/stopping anytime and that is why mail is not being sent to the receiver on schedule but delaying too long.
Could you please assist me in solving this.
Please find the below log file lines for reference.2024-07-30 12:41:03.914 ===== TRACE ===== Cron started at 30/07/2024 12:41:03
2024-07-30 12:41:34.371 ----- DEBUG ----- ../model/Mail.php not found, current directory is :'C:Apache24'
Try to move up with chdir('../')
2024-07-30 12:41:34.372 ** ERROR ** [V11.3.1] CRON abnormally stopped
2024-07-30 12:41:34.372 ** ERROR ** [V11.3.1] === Trace Stack for last error ===
2024-07-30 12:41:34.372 ** ERROR ** [V11.3.1] => C:Apache24htdocsprojeqtormodelCron.php at line 321 calling debugPrintTraceStack()
2024-07-30 12:41:34.373 ** ERROR ** [V11.3.1] => C:Apache24htdocsprojeqtortoolcronRun.php at line 35 calling Cron:abort()
2024-07-30 12:41:34.373 ** ERROR ** [V11.3.1] => calling cronAbort()
2024-07-30 12:41:34.373 ** ERROR ** [V11.3.1] ===
2024-07-30 12:42:07.228 ===== TRACE ===== Cron started at 30/07/2024 12:42:07
2024-07-30 12:42:37.325 ----- DEBUG ----- ../model/Mail.php not found, current directory is :'C:Apache24'
Try to move up with chdir('../')
2024-07-30 12:42:37.326 ** ERROR ** [V11.3.1] CRON abnormally stopped
2024-07-30 12:42:37.327 ** ERROR ** [V11.3.1] === Trace Stack for last error ===
2024-07-30 12:42:37.327 ** ERROR ** [V11.3.1] => C:Apache24htdocsprojeqtormodelCron.php at line 321 calling debugPrintTraceStack()
2024-07-30 12:42:37.327 ** ERROR ** [V11.3.1] => C:Apache24htdocsprojeqtortoolcronRun.php at line 35 calling Cron:abort()
2024-07-30 12:42:37.328 ** ERROR ** [V11.3.1] => calling cronAbort()
2024-07-30 12:42:37.328 ** ERROR ** [V11.3.1] ===
Hi,
If you have no other issue written in the logs then possibly issue is due to Sceduled reports.
Try and disable all scheduled reports and see if Cron runs fluently.
Then you can try and reactivate reports one by one to identify erroneous one.
Hi,
Thanks for the suggestion, I have deleted two and disabled 1 scheduled report(s). Will observe now.
Hi,
I followed the instructions what you suggested i.e. disabled scheduled reports, but the cron is still stopping frequently and ProjeQtOr log is showing the same result (as following)!2024-08-03 16:44:23.624 ----- DEBUG ----- ../model/Mail.php not found, current directory is :'C:Apache24'
Try to move up with chdir('../')
2024-08-03 16:44:23.625 ** ERROR ** [V11.3.1] CRON abnormally stopped
2024-08-03 16:44:23.626 ** ERROR ** [V11.3.1] === Trace Stack for last error ===
2024-08-03 16:44:23.626 ** ERROR ** [V11.3.1] => C:Apache24htdocsprojeqtormodelCron.php at line 321 calling debugPrintTraceStack()
2024-08-03 16:44:23.626 ** ERROR ** [V11.3.1] => C:Apache24htdocsprojeqtortoolcronRun.php at line 35 calling Cron:abort()
2024-08-03 16:44:23.627 ** ERROR ** [V11.3.1] => calling cronAbort()
2024-08-03 16:44:23.627 ** ERROR ** [V11.3.1] ===
At the same time I checked the error log from apache also, it's showing the following resoult.
[Sat Aug 03 16:44:23.623680 2024] [php:error] [pid 12044:tid 1152] [client 192.168.1.2:49296] PHP Fatal error: Maximum execution time of 3000 seconds exceeded in C:\Apache24\htdocs\projeqtor\model\Cron.php on line 503, referer: http://192.168.77.266/projeqtor/view/main.php
Hope, the above two logs may help you in assisting me. Could you please help me with this?
It seems the set_time_limit function doe snot work on your instance.
Check tool/projeqtor.php, if line 4835 is "return;", remove it
function projeqtor_set_time_limit($timeout) {
return;
if (ini_get('safe_mode')) {
to
function projeqtor_set_time_limit($timeout) {
if (ini_get('safe_mode')) {
Hi,
Thank you so much for your help. Following your suggested steps seems to have resolved the issue of the cron stopping abnormally. However, I do have a question: Regarding the change made in the `projeqtor.php` file where I commented on line 4835 as per your guidance, I noticed in the ticket #8746 on https://track.projeqtor.org/ that a permanent resolution has been implemented in the upcoming stable release version 11.3.2.
Could you please clarify this further? Your insights would be greatly appreciated.
Yes, the fix will be included in V11.3.2.
Moreover, if you register to Subscription Service, you can get the fix as soon as it is published (as soon as fixed and validated), so you may have never faced the issue as you would get the fix before you notice the issue 😉