Wondering if someone can give me a hand with these… I’m looking at the workflows and schedular jobs and the IDs below don’t match up with any of them after a cross check in excel.
I’m not sure where else to look?
Thu Feb 1 15:00:01 2024 [86730][1][FATAL] Job a863c244-ed43-faec-6beb-65bbb10cdeac (Optimise AOD Index) failed in CRON run
Thu Feb 1 18:00:01 2024 [89488][1][FATAL] Job bd402f28-78c7-8c7f-553d-65bbdc176b62 (Optimise AOD Index) failed in CRON run#
It seems like you’re encountering issues with scheduled jobs in SuiteCRM. Here are some steps you can take to troubleshoot:
1. Check Job Definitions: Verify if the job IDs mentioned in the error logs correspond to any existing job definitions in SuiteCRM. You can do this by navigating to Admin > Schedulers and checking the job definitions.
2. Review Log Details: Look for more detailed error messages or stack traces related to these jobs. You can find additional information in SuiteCRM logs. Navigate to Admin > System Settings and enable Debug Mode. Check the sugarcrm.log file for more detailed error messages.
3. Correct Job Names: It appears there might be a typo in the job names. Ensure that the job names match the actual job definitions in SuiteCRM.
4. Reschedule Jobs: If you’ve identified the correct job definitions, try rescheduling these jobs to see if the issue persists. You can do this from the Admin > Schedulers section.
5. Check CRON Configuration: Verify your CRON configuration to ensure it’s running correctly and at the expected intervals. Incorrect CRON settings could lead to job failures.
If the problem persists, provide more details about your SuiteCRM version, any recent changes, or additional error messages.
Hope this helps! Let me know if you have any concerns.
Go in phpMyAdmin and select the SuiteCRM database (not a specific table, but the database itself).
Click the Search tab on top.
Paste the record id into the search box.
Select ALL tables in the “inside tables” area. An easy way to do this is to click the first one and then press “ctrl-shift-end”.
Your screen should look something like this:
Now click to search, and scroll down to examine in which tables that id was found. This might explain why it is considered a duplicate. Searching here in the database, instead of from the UI, ensures you’re not restricted by security groups or any other filters.
I’ve looked into it, also been pruning the DB and all sorts after a good read on other threads. I’ve got debug mode on and looking out for anything as it pops up…