Hi
Upgraded to 7.2 and the Responsive theme. Both the Scheduler and create schedule screens are blank. Cron jobs are also not running which were prior to the upgrade ?
Any suggestions ?
Thanks
David
Did you check any of the log files (apache error log, sugarcrm.log)?
We have same problem
https://suitecrm.com/forum/installation-upgrade-help/3789-scheduler-problem-after-upgrade-to-7-2
Apache Log not showing anything but Sugar Log is which I have attached
I’ve also just noticed I am receiving the following error notifications via email:
PHP Notice: Undefined index: db_port in /-domain-/include/database/MysqliManager.php on line 274 PHP Notice: Undefined index: module in /-domain-/modules/AOW_WorkFlow/AOW_WorkFlow.php on line 134 PHP Notice: Undefined index: module in /-domian-/modules/AOW_WorkFlow/AOW_WorkFlow.php on line 134 PHP Fatal error: Cannot redeclare pollMonitoredInboxesCustomAOP() (previously declared in /-domain-/custom/modules/Schedulers/_AddJobsHere.php:43) in /-domain/custom/modules/Schedulers/Ext/ScheduledTasks/scheduledtasks.ext.php on line 398 PHP Notice: Undefined index: db_port in /-domain-/include/database/MysqliManager.php on line 274 PHP Notice: Undefined index: module in /-domain-/modules/AOW_WorkFlow/AOW_WorkFlow.php on line 134
Shall we make this the official “Scheduler isn’t working” thread?
Here’s what I’ve found in my nginx logs (php logs):
So then I looked into into ~/custom/modules/Schedulers. It looks like these are removed in 7.2? https://github.com/salesagility/SuiteCRM/tree/master/custom/modules
I copied (moved) the directory elsewhere, and now the Schedulers screen is accessible, but still not displaying any of the jobs. However, I can confirm that they are now running (or at least attempting to run).
Snippets from “select message,target from job_queue, order by execute_time desc”. The NULLs are successful runs, which are also stock SugarCRM jobs.
NULL function::sendEmailReminders
Cannot call function: aodOptimiseIndex function::aodOptimiseIndex
Cannot call function: processAOW_Workflow function::processAOW_Workflow
Cannot call function: aodIndexUnindexed function::aodIndexUnindexed
Cannot call function: pollMonitoredInboxesCustomAOP function::pollMonitoredInboxesCustomAOP
Cannot call function: aodIndexUnindexed function::aodIndexUnindexed
Cannot call function: pollMonitoredInboxesCustomAOP function::pollMonitoredInboxesCustomAOP
NULL function::sendEmailReminders
Cannot call function: aodOptimiseIndex function::aodOptimiseIndex
Cannot call function: processAOW_Workflow function::processAOW_Workflow
Cannot call function: processAOW_Workflow function::processAOW_Workflow
Cannot call function: aodIndexUnindexed function::aodIndexUnindexed
NULL function::sendEmailReminders
Cannot call function: pollMonitoredInboxesCustomAOP function::pollMonitoredInboxesCustomAOP
This is as far as I’ve gotten right now. I’ll try to get back to it later.
Quick correction: Jobs are visible. My test system doesn’t automatically display …
FIXED … on my system.
~/custom/modules/Schedulers/_AddJobsHere.php contains the redeclaration of pollMonitoredInboxesCustomAOP() , which was causing the conflict and caused all jobs to fail. I’ve removed (renamed) this file, and then all of the jobs began firing.
In my case, pollMonitoredInboxesCustomAOP() is the ONLY function that lives in this file. Somebody @salesagility can explain how this file is generated?
Thanks. I renamed the file and now the scheduler screens are working. However, my group inbox is not getting polled ?
David
The redeclaration of the AOP scheduler/job is a known bug and was logged on the SuiteCRM GitHub.
I will update this topic once this has been resolved.
Thanks,
Will.
Correction: After a delay the group mail box is now being polled so above fix did work !
Fresh install of 7.2.1 this bug still exists
Wed Mar 11 16:32:02 2015 [1798][1][FATAL] Job 45cf0d6e-dce2-b0cf-a457-550098f48e37 (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:33:01 2015 [1842][1][FATAL] Job 4afc0e21-6e2f-05c1-6857-550098cce21b (Optimise AOD Index) failed in CRON run
Wed Mar 11 16:34:02 2015 [1899][1][FATAL] Job 59bfe013-a6a5-a85f-a4bc-550098841fda (Run Scheduled Reports) failed in CRON run
Wed Mar 11 16:34:02 2015 [1899][1][FATAL] Job 79acc0bf-c84c-74c5-a238-550098f1b4ea (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:35:02 2015 [1942][1][FATAL] Job d9dfd131-a53b-9278-ad92-5500982681c7 (Optimise AOD Index) failed in CRON run
Wed Mar 11 16:36:01 2015 [1997][1][FATAL] Job 10af02e3-b7b0-4fdd-55b4-550098664dd5 (Run Scheduled Reports) failed in CRON run
Wed Mar 11 16:36:01 2015 [1997][1][FATAL] Job e75e1e31-bd79-b01a-c233-550098aa3438 (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:37:01 2015 [2033][1][FATAL] Job 597ca911-0ea7-c6b1-6d82-55009952ca68 (Optimise AOD Index) failed in CRON run
Wed Mar 11 16:37:20 2015 [1707][1][FATAL] holidays for users_holidays failed to load
Wed Mar 11 16:37:20 2015 [1707][1][FATAL] project_resource for projects_users_resources failed to load
Wed Mar 11 16:38:02 2015 [2083][1][FATAL] Job 7c5b615e-eb88-3ffb-21f4-55009930587d (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:39:02 2015 [2121][1][FATAL] Job 8acd8e5f-f483-b6ae-e119-5500998e8eed (Run Scheduled Reports) failed in CRON run
Wed Mar 11 16:39:02 2015 [2121][1][FATAL] Job ebe0311a-2b49-e011-317a-5500997ddb95 (Optimise AOD Index) failed in CRON run
Wed Mar 11 16:40:01 2015 [2176][1][FATAL] Job 5ec90e29-5b21-1bf6-d1e2-550099cd0b10 (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:41:02 2015 [2212][1][FATAL] Job 7867bffb-7b8e-f0f7-059a-55009a1368cf (Optimise AOD Index) failed in CRON run
Wed Mar 11 16:42:02 2015 [2261][1][FATAL] Job 8f178292-f67a-948c-6536-55009a3604b5 (Run Scheduled Reports) failed in CRON run
Wed Mar 11 16:42:02 2015 [2261][1][FATAL] Job 1bbdb813-c443-52a3-8327-55009a9e6dae (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:43:01 2015 [2297][1][FATAL] Job e27f8385-63f0-602b-7949-55009a7b38c4 (Optimise AOD Index) failed in CRON run
Wed Mar 11 16:44:01 2015 [2346][1][FATAL] Job 73b2c610-a198-2860-73d0-55009a10a9cf (Perform Lucene Index) failed in CRON run
Wed Mar 11 16:45:02 2015 [2382][1][FATAL] Job 8c331ff4-e632-3606-0b18-55009a733c25 (Run Scheduled Reports) failed in CRON run
Wed Mar 11 16:45:02 2015 [2382][1][FATAL] Job 6fb86882-012f-7d51-8019-55009b200b42 (Optimise AOD Index) failed in CRON run
Best Regards
Is this the fix?
https://github.com/salesagility/SuiteCRM/commit/dda786a6489bfd8c743150033a29fd460f25b980
I have the same issue. Mine was a fresh 7.2.1 install, not an upgrade and those schedulers don’t run and are in the log like that.
Check your webserver/php logs for errors.
My log shows:
Wed Mar 25 13:27:01 2015 [3729][1][FATAL] Job 6de4f6b8-7958-f422-942c-5512ef3e6897 (Run Scheduled Reports) failed in CRON run
Wed Mar 25 13:27:02 2015 [3729][1][FATAL] Job 6ad10213-b9ae-925f-d31e-5512ef821005 (Perform Lucene Index) failed in CRON run
Wed Mar 25 13:28:02 2015 [4505][1][FATAL] Job c1726922-e230-7c47-9bfc-5512ef61a749 (Optimise AOD Index) failed in CRON run
Not your SuiteCRM/SugarCRM logs, but your Apache/PHP logs.
My server is hosted on a 1and1 shared server, I will look into finding those logs! Thanks!
No access to apache/php logs on shared server per 1&1 support. Any other ideas? If I turn off AOD, the aod index/lucene job says it ran, although it doesn’t build the index. When I turn AOD back on, the scheduler doesn’t work for them. Scheduled report still doesn’t run.
I am experiencing same problem with a FRESH NEW install of 7.2.1?