Hello everyone,Since upgrading to ProjeQtOr v12.3.2, we’ve been experiencing a significant increase in errors and instability, particularly with the cron job, which frequently stops or fails to restart properly.We’ve checked our configuration and logs, but haven’t identified a clear root cause yet. The issues seem to have started right after the upgrade. We’ve noticed that these cron interruptions often occur after errors related to ticket reception via email inboxes.
Are there any known issues, workarounds, or patches available related to cron failures or general instability in v12.3.2?Any help or guidance would be greatly appreciated.
Thanks in advance for your support
Exemple de log :2025-11-06 08:24:50.735 ----- DEBUG ----- [IMBT#28] User corresponding to email address is #411
2025-11-06 08:24:50.739 ----- DEBUG ----- [IMBT#28] Message identified as reply to message from Ticket #12282
2025-11-06 08:24:50.739 ----- DEBUG ----- [IMBT#28] note not stored : only emails from known users allocated to the project
2025-11-06 08:24:51.031 ** ERROR ** [V12.3.2] CRON abnormally stopped
2025-11-06 08:24:51.031 ** ERROR ** [V12.3.2] === Trace Stack for last error ===
2025-11-06 08:24:51.032 ** ERROR ** [V12.3.2] => /var/www/vhosts/xxx.xxx-xxx/httpdocs/model/Cron.php at line 324 calling debugPrintTraceStack()
2025-11-06 08:24:51.032 ** ERROR ** [V12.3.2] => /var/www/vhosts/xxx.xxx-xxx/httpdocs/tool/cronRun.php at line 35 calling Cron:abort()
2025-11-06 08:24:51.032 ** ERROR ** [V12.3.2] => calling cronAbort()
2025-11-06 08:24:51.032 ** ERROR ** [V12.3.2] ===2025-11-05 16:58:56.799 ----- DEBUG ----- [IMBT#108] User corresponding to email address is #300
2025-11-05 16:58:56.805 ----- DEBUG ----- [IMBT#108] Message identified as reply to message from Ticket #12289
2025-11-05 16:58:56.805 ----- DEBUG ----- [IMBT#108] note not stored : only emails from known users allocated to the project
2025-11-05 16:58:57.919 ** ERROR ** [V12.3.2] CRON abnormally stopped
2025-11-05 16:58:57.920 ** ERROR ** [V12.3.2] === Trace Stack for last error ===
2025-11-05 16:58:57.920 ** ERROR ** [V12.3.2] => /var/www/vhosts/xxx.xxx-xxx.com/httpdocs/model/Cron.php at line 324 calling debugPrintTraceStack()
2025-11-05 16:58:57.920 ** ERROR ** [V12.3.2] => /var/www/vhosts/xxx.xxx-xxx.com/httpdocs/tool/cronRelaunch.php at line 28 calling Cron:abort()
2025-11-05 16:58:57.920 ** ERROR ** [V12.3.2] => calling cronAbort()
2025-11-05 16:58:57.920 ** ERROR ** [V12.3.2] ===
Hello, any news on topics ?
Hi,
We did not face such issue.
What is strange is that last starck trace line is
calling cronAbort()
So we don't know which code line caused the abort.
This could mean it is a real "end of treatment", and ,ot an abort because of error.
This could be generated by :
- PHP Stop / Restart
- PHP Timeout : The Cron is a never ending process, but if your PHP is configured to forbid timeout extension, Cron will unexpectedly stop
- Error on some planned reports : we used to have reports that did "exit" when "no data found". This stopped the Cron. We fixed most reports, but some may still stop Cron. If you have specific report, this could be the case.
a {
text-decoration: none;
color: #464feb;
}
tr th, tr td {
border: 1px solid #e6e6e6;
}
tr th {
background-color: #f5f5f5;
}Hello,I'm following up regarding the cron stability issues we’ve been experiencing since upgrading to ProjeQtOr v12.3.2 / v12.3.3.We have applied several optimizations:
- General cron frequency: 30s → 120s
- Alerts & notifications: 120s → 240s
- Incoming emails: 300s
- PHP memory_limit increased to 1024M
- max_execution_time set to 0
However, the cron still stops unexpectedly, specifically during the email scanning phase, where more than 100 IMAP inboxes are checked. No useful error message appears in the logs, which seems consistent with an external interruption of the process, as mentioned in your previous reply.Do you have any new insights or known issues regarding this type of cron interruption in versions 12.3.2 / 12.3.3?You also mentioned that some scheduled reports might still contain an
exit()
call and could stop the cron.
Could you clarify what exactly we should check, or how to identify any reports that might still cause this?Thanks in advance for your help.
To check if issue come form reports, go to screen "Scheduled reports" and disable all sceduled reports.
If cron does not stop anymore, if come from here.
Then reenable reports one by one, to find which stops the cron and tell us about it.
Also try to chech apache / PHP error log file, possibly to errors may appear here (timeout, out pof memory, ...)