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] ===
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.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Paramétrages de cookies
×
Cookies fonctionnels
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Veuillez vous connecter pour voir vos activités!
Autres cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.