Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM. Created by Fanatical Labs, 2023 SugarCRM Partner Award Winner.
#1123 - SugarChimp scheduler is not running afterward
Hi,
I managed to import target list from SugarCRM to MailChimp for one time only. After that, all the list seems to be pending and cannot be executed.
The scheduler setting does not seems to have problem. And the status is healthy from the dashboard in SugarCRM.
I approached SugarCRM support team, the following is the replies from the team. I do not understand why such thing could resolved.
Please advise accordingly. If there is no solution to this, we should not be continuing the subscription.
Replies from SugarCRM support team:
SugarChimp scheduler having issues. Crone is not completed properly. This is affecting existing scheduler. Because of this, Other cron Job is also in queue.
We decide to disable this scheduler, Because it is impacting other scheduler.
In SugarCRM we have 10+ scheduler. Scheduler is a PHP script that run on a configured time. It means Currently there is more then 10+ PHP script configured. Server run scripts one by one. After completing one script it run another script. In Case, One script have issue, So either it fails or it will be in infinite loop. (Based on how you write the code). In Case it is infinite loop or job is is not completing, the status of scheduler is "In Progress". If One Job Stuck (In Progress) other Job will be "In queue". Thus other job will not run.
What we experience in SugarChimp is It Stuck on some point and that cause other Job to be stuck as well. That's why we Make it Disable. So that other scheduler(script) can run.
You mention to configure * * * * * cd ; php -f cron.php > /dev/null 2>&1
This is the first thing we configured when we create a sugar Instance. Because of this other scheduler is working.
-
"Nice product and nice team behind it. They helped us with everything we needed in order to get our system working as we wanted to."
Read More Reviews
- Most Recent Love from Users
melissa- Westcoat
- Mark Westerhoff
- danielolivas
- kgm
- Evolution Marketing
9 years ago
Hi Ian, I can help you with this.
It sounds like there may be a php or Sugar error that's causing the Scheduler from not finishing. Can you check the sugar logs and server logs to see if any errors for SugarChimp are being reported?
You can also check the scheduler record in the job_queue table where name='SugarChimp' to see if it is failing and if a reason is listed there.
It looks like you use iZeno has your Sugar host. If you don't know how to check the things above, they'll be able to help you get the answers.
Definitely let me know what you find. Thanks!
9 years ago
Hi SugarChimp,
This is the sample of error message in SugarCRM log.
_Thu Jan 22 21:10:10 2015 [19054][1][FATAL] Job 63e1ae83-4b34-f6e7-33dd-54bf087ebef3 (MailChimp to SugarCRM Job - Initial Import) failed in CRON run
Wed Feb 4 16:25:08 2015 [17430][1][FATAL] Job 3d6c380c-ad8a-8bae-7474-54d0013537f5 (MailChimp to SugarCRM Activity Job - Initial Campaign Activity Import ) failed in CRON run_
This is the Job Log in SugarChimp Scheduler. Apparently there is no reason stated in this Job Log why it is in queued.
Job Name Job Status Execute Time Date Modified:
SugarChimp queued 04.02.2015 07:05am 04.02.2015 07:05am
Currently, the status of SugarChimp module is set to active again by iZeno support team. According to iZeno support team, the team has to set the SugarChimp Scheduler to inactive in order for other scheduler continue to run. But "failed in CRON run" still appear in SugarCRM error message.
Is there any solution to this issue? What are the configurations or codes required to change?
Regards, Ian
9 years ago
Thanks for the details Ian. Can you please have iZeno check the php logs to see what error is occurring at the PHP level? That should let us know the reason the scheduler jobs are hitting the "failed in CRON run" error. There's definitely a solution to the issue, we just need to diagnose what's causing the error first.
The reason the errors continue to happen with the scheduler still turned off is because the second log example you provide "MailChimp to SugarCRM Activity Job" is not driven by the SugarChimp scheduler. It will fail 100 times and then ultimately stop trying.
If nothing comes up in the php error logs, the next step will be to setup a screenshare/call for us to debug and see if we can find the issue.
Thanks!
9 years ago
Hi SugarChimp,
I got feedback from Izeno.
The issue is happening due to following error: PHP Fatal error: Class 'MailChimpToSugarCRMActivity' not found in /var/www/vhosts/basic/ultimate.izenoondemand.com/httpsdocs/modules/SchedulersJobs/SchedulersJob.php on line 525
We tried to include the file where MailChimpToSugarCRMActivity class has been declared but it is causing another error: PHP Fatal error: Cannot redeclare SugarChimp() (previously declared in /var/www/vhosts/basic/ultimate.izenoondemand.com/httpsdocs/custom/modules/Schedulers/Ext/ScheduledTasks/scheduledtasks.ext.php:19) in /var/www/vhosts/basic/ultimate.izenoondemand.com/httpsdocs/custom/modules/Schedulers/Ext/ScheduledTasks/scheduledtasks.ext.php on line 62
This issue is only happening when MailChimpToSugarCRMActivity Job is trying to run on the server.
Please advise. Thanks.
Regards, Ian
9 years ago
Hi SugarChimp,
Any concrete solution based on the php log errors? We are hoping to solve it before the free trial. We did not actually really try out since we sign up. It would be great if you can help us to resolve it as soon as possible. Thanks a lot.
9 years ago
Hi Ian, I'm still not able to replicate this on my side.
Do you know if a Repair & Rebuild was run after installing SugarChimp?
I'm wondering if the installation process did not fully install. I'd ask them to try re-installing SugarChimp and after it finishes run a Repair & Rebuild. After trying this, let me know if they still see the error.
If this doesn't resolve the issue, we'll probably need to have a quick call/screenshare to look closer at what's going on.
Thanks!
9 years ago
Hi SugarChimp,
What do you mean by replicate that on your side? The error?
I did not run the Repair and & Rebuild after installing SugarChimp. What is the purpose to run Repair & Rebuild after installing it?
It seems like I cannot reintall SugarChimp by myself. I shall get iZeno to do it for me then.
Somehow it is really not so effective. Anyway, hope it really can be solved as soon as possible.
Thanks.
Regards, Ian
9 years ago
Hi Ian
Just stepping in here as I noticed based on the error messages you posted above that the install didn't complete correctly. As suggested by SugarChimp, if you do an uninstall and then an install again it should address the issue of files not copying over correctly. It is also a good idea after any module install to do a repair by going to Admin->Repair->Quick Repair & Rebuild as some installs have some tricky situations that cause the installer not to do it correctly. Always run any generated SQL that appears after the repair.
If you still have a file missing error like above then you likely have file permission issues on your server. iZeno should be able to address these for you.
Sorry that you are experiencing these issues, but they are not the norm. Unfortunately sometimes certain servers just aren't configured correctly for SugarCRM to run as it should.
Hope this helps! -Jason SugarOutfitters
9 years ago
Hi Jason,
Thanks for your assistance.
I have just uninstalled and reinstalled SugarChimp. A repair and rebuild is also done. Now I'm testing it.
The importing of list seems to be working fine now.
Regards, Ian
9 years ago
Hi Jason,
I thought it would be helpful for you if I include this debug for you to see what is going on after the re-installation.
Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: Instantiate SugarChimp_Scheduler Driver SugarChimp_Scheduler_MailchimpActivityToSugarCRM Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver::start Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver->start_timer timer started at 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver->start_timer elapsed time is empty Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver::start License is good. Run it! Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Original Start time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Current time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time since last check 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Elapsed time 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time used 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_MailchimpActivityToSugarCRM->run Running... Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Original Start time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Current time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time since last check 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Elapsed time 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time used 0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT mailchimp_list_id FROM sugarchimp_mc_activity ORDER BY date_entered ASC Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_MailchimpToSugar->get_next_mailchimp_list_id get oldest job: SELECT mailchimp_list_id FROM sugarchimp_mc_activity ORDER BY date_entered ASC LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT mailchimp_list_id FROM sugarchimp_mc_activity ORDER BY date_entered ASC LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.011916160583496 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_MailchimpToSugar->get_next_mailchimp_list_id There are no jobs to be processed for the list. Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Original Start time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Current time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time since last check 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Elapsed time 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time used 0 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT COUNT(id) AS pending_count FROM job_queue WHERE target = 'class::MailChimpToSugarCRMActivity' AND status = 'queued' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.01948618888855 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Activity::is_activity_import_job_queued: there is no job pending Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_MailchimpActivityToSugarCRM->run: queue up the next import activity job Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_MailchimpActivityToSugarCRM->run: sql to get next job to queue: SELECT mailchimp_campaign_id, mailchimp_list_id, initial_sync, last_sync FROM sugarchimp_activity_tracker WHERE DATE_ADD(start_date, INTERVAL 30 DAY) > '2015-02-10 02:45:05' AND (last_sync IS NULL OR DATE_ADD(last_sync, INTERVAL 1 DAY) < '2015-02-10 02:45:05') ORDER BY last_sync ASC, start_date DESC LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT mailchimp_campaign_id, mailchimp_list_id, initial_sync, last_sync FROM sugarchimp_activity_tracker WHERE DATE_ADD(start_date, INTERVAL 30 DAY) > '2015-02-10 02:45:05' AND (last_sync IS NULL OR DATE_ADD(last_sync, INTERVAL 1 DAY) < '2015-02-10 02:45:05') ORDER BY last_sync ASC, start_date DESC LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0030720233917236 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_MailchimpActivityToSugarCRM->run: activity tracker, there are no MailChimp Campaigns on the account yet, nothing needs syncing Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver::end Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver::end The scheduler ran successfully Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Original Start time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Current time 1423536315 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver Time since last check 0 Tue Feb 10 10:45:15 2015 [7048][1][FATAL] SugarChimp:debug:1423536315: SugarChimp_Scheduler_Driver::end final result: Array ( [status] => success [message] => All activities are processed from Mailchimp to sync to SugarCRM. [elapsed_time] => 0 )
Tue Feb 10 10:45:15 2015 [7048][1][INFO] Resolving job b613244b-cbc9-5aa7-9c15-54d970b07450 as success: Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::before_save Tue Feb 10 10:45:15 2015 [7048][1][DEPRECATED] SugarBean.php: preprocess_fields_on_save() is deprecated Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE job_queue SET assigned_user_id='1',name='SugarChimp',date_modified='2015-02-10 02:45:05',scheduler_id='97797b90-befb-54d6-7b37-54d95d89d44f',execute_time='2015-02-10 02:45:00',status='done',resolution='success',message=NULL,target='function::SugarChimp',data=NULL,requeue=0,retry_count=NULL,failure_count=NULL,job_delay=0,client='CRON1c5d072676309395bd010d69d45b82c7:7048',percent_complete=NULL WHERE job_queue.id = 'b613244b-cbc9-5aa7-9c15-54d970b07450' AND deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0048129558563232 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Updating records related to SchedulersJobs b613244b-cbc9-5aa7-9c15-54d970b07450 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve Team: SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.00071907043457031 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::after_save Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Creating new instance of hook class SugarSearchEngineQueueManager without parameters Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Adding the following bean to the populate queue- module: SchedulersJob , id: b613244b-cbc9-5aa7-9c15-54d970b07450 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE schedulers SET last_run='2015-02-10 02:45:05' WHERE id='97797b90-befb-54d6-7b37-54d95d89d44f' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.007634162902832 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Get One: |SELECT id FROM job_queue WHERE execute_time <= '2015-02-10 02:45:05' AND status = 'queued' ORDER BY date_entered ASC| Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT id FROM job_queue WHERE execute_time <= '2015-02-10 02:45:05' AND status = 'queued' ORDER BY date_entered ASC Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT id FROM job_queue WHERE execute_time <= '2015-02-10 02:45:05' AND status = 'queued' ORDER BY date_entered ASC LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0072269439697266 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::before_retrieve Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve SchedulersJob : SELECT job_queue.* FROM job_queue WHERE job_queue.id = 'dfb2afc5-c97f-6e84-8e6e-54d970269d03' AND job_queue.deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT job_queue.* FROM job_queue WHERE job_queue.id = 'dfb2afc5-c97f-6e84-8e6e-54d970269d03' AND job_queue.deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT job_queue.* FROM job_queue WHERE job_queue.id = 'dfb2afc5-c97f-6e84-8e6e-54d970269d03' AND job_queue.deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0041060447692871 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::after_retrieve Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE job_queue SET status='running', date_modified='2015-02-10 02:45:05', client='CRON1c5d072676309395bd010d69d45b82c7:7048' WHERE id='dfb2afc5-c97f-6e84-8e6e-54d970269d03' AND status='queued' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0049688816070557 Tue Feb 10 10:45:15 2015 [7048][1][DEPRECATED] Formatting correction: SchedulersJobs->date_entered had formatting automatically corrected. This will be removed in the future, please upgrade your external code Tue Feb 10 10:45:15 2015 [7048][1][DEPRECATED] Formatting correction: SchedulersJobs->date_modified had formatting automatically corrected. This will be removed in the future, please upgrade your external code Tue Feb 10 10:45:15 2015 [7048][1][DEPRECATED] Formatting correction: SchedulersJobs->execute_time had formatting automatically corrected. This will be removed in the future, please upgrade your external code Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::before_save Tue Feb 10 10:45:15 2015 [7048][1][DEPRECATED] SugarBean.php: preprocess_fields_on_save() is deprecated Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE job_queue SET assigned_user_id='1',name='Update tracker_sessions Table',date_modified='2015-02-10 02:45:05',scheduler_id='7177389e-52b0-3a5c-54a9-50da608e0b28',execute_time='2015-02-10 02:45:00',status='running',resolution='queued',message=NULL,target='function::updateTrackerSessions',data=NULL,requeue=0,retry_count=NULL,failure_count=NULL,job_delay=0,client='CRON1c5d072676309395bd010d69d45b82c7:7048',percent_complete=NULL WHERE job_queue.id = 'dfb2afc5-c97f-6e84-8e6e-54d970269d03' AND deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0073361396789551 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Updating records related to SchedulersJobs dfb2afc5-c97f-6e84-8e6e-54d970269d03 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve Team: SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0077838897705078 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::after_save Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Creating new instance of hook class SugarSearchEngineQueueManager without parameters Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Adding the following bean to the populate queue- module: SchedulersJob , id: dfb2afc5-c97f-6e84-8e6e-54d970269d03 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: Users::before_retrieve Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve User : SELECT users.,users_cstm. FROM users LEFT JOIN users_cstm ON users.id = users_cstm.id_c WHERE users.id = '1' AND users.deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT users.,users_cstm. FROM users LEFT JOIN users_cstm ON users.id = users_cstm.id_c WHERE users.id = '1' AND users.deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT users.,users_cstm. FROM users LEFT JOIN users_cstm ON users.id = users_cstm.id_c WHERE users.id = '1' AND users.deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0023341178894043 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT u1.first_name, u1.last_name from users u1, users u2 where u1.id = u2.reports_to_id AND u2.id = '1' and u1.deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0023469924926758 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT team_id, teams.name, teams.name_2 FROM team_memberships rel RIGHT JOIN teams ON (rel.team_id = teams.id) WHERE rel.user_id = '1' AND rel.team_id = '1' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0086460113525391 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: Teams::before_retrieve Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve Team : SELECT teams.* FROM teams WHERE teams.id = '1' AND teams.deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT teams.* FROM teams WHERE teams.id = '1' AND teams.deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT teams.* FROM teams WHERE teams.id = '1' AND teams.deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.011477947235107 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: Teams::after_retrieve Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: Teams::before_retrieve Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve Team : SELECT teams.* FROM teams WHERE teams.id = '1' AND teams.deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT teams.* FROM teams WHERE teams.id = '1' AND teams.deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT teams.* FROM teams WHERE teams.id = '1' AND teams.deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.00074410438537598 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: Teams::after_retrieve Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT id ,teams.name as team_name , teams.created_by owner FROM teams WHERE deleted=0 AND id='1' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.001276969909668 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] SugarBean[User].load_relationships, Loading relationship (reports_to_link). Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT ea.email_address, ea.email_address_caps, ea.invalid_email, ea.opt_out, ea.date_created, ea.date_modified, ear.id, ear.email_address_id, ear.bean_id, ear.bean_module, ear.primary_address, ear.reply_to_address, ear.deleted FROM email_addresses ea LEFT JOIN email_addr_bean_rel ear ON ea.id = ear.email_address_id WHERE ear.bean_module = 'Users' AND ear.bean_id = '1' AND ear.deleted = 0 ORDER BY ear.reply_to_address, ear.primary_address DESC Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0045311450958252 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: Users::after_retrieve Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] ----->SchedulersJob calling function: updateTrackerSessions Tue Feb 10 10:45:15 2015 [7048][1][INFO] ----->Scheduler fired job of type updateTrackerSessions() Tue Feb 10 10:45:15 2015 [7048][1][INFO] ----->Scheduler is about to update tracker_sessions table by running the query UPDATE tracker_sessions set active = 0 where date_end < '2015-02-09 20:45:05' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE tracker_sessions set active = 0 where date_end < '2015-02-09 20:45:05' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.014986038208008 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Resolving job dfb2afc5-c97f-6e84-8e6e-54d970269d03 as success: Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::before_save Tue Feb 10 10:45:15 2015 [7048][1][DEPRECATED] SugarBean.php: preprocess_fields_on_save() is deprecated Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE job_queue SET assigned_user_id='1',name='Update tracker_sessions Table',date_modified='2015-02-10 02:45:05',scheduler_id='7177389e-52b0-3a5c-54a9-50da608e0b28',execute_time='2015-02-10 02:45:00',status='done',resolution='success',message=NULL,target='function::updateTrackerSessions',data=NULL,requeue=0,retry_count=NULL,failure_count=NULL,job_delay=0,client='CRON1c5d072676309395bd010d69d45b82c7:7048',percent_complete=NULL WHERE job_queue.id = 'dfb2afc5-c97f-6e84-8e6e-54d970269d03' AND deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0052027702331543 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Updating records related to SchedulersJobs dfb2afc5-c97f-6e84-8e6e-54d970269d03 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Retrieve Team: SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT teams.* FROM teams WHERE associated_user_id = '1' AND deleted=0 LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.00059819221496582 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Hook called: SchedulersJobs::after_save Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Creating new instance of hook class SugarSearchEngineQueueManager without parameters Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Adding the following bean to the populate queue- module: SchedulersJob , id: dfb2afc5-c97f-6e84-8e6e-54d970269d03 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:UPDATE schedulers SET last_run='2015-02-10 02:45:05' WHERE id='7177389e-52b0-3a5c-54a9-50da608e0b28' Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0048849582672119 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Get One: |SELECT id FROM job_queue WHERE execute_time <= '2015-02-10 02:45:05' AND status = 'queued' ORDER BY date_entered ASC| Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Limit Query:SELECT id FROM job_queue WHERE execute_time <= '2015-02-10 02:45:05' AND status = 'queued' ORDER BY date_entered ASC Start: 0 count: 1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query:SELECT id FROM job_queue WHERE execute_time <= '2015-02-10 02:45:05' AND status = 'queued' ORDER BY date_entered ASC LIMIT 0,1 Tue Feb 10 10:45:15 2015 [7048][1][INFO] Query Execution Time:0.0014970302581787 Tue Feb 10 10:45:15 2015 [7048][1][DEBUG] Calling MySQLi::disconnect()
9 years ago
Thanks for the help Jason.
Ian, thanks for sharing the log and glad to hear everything is cleared up.
Everything in the log file looks good. Everything SugarChimp is reporting is debug statements, no errors. You can turn of SugarChimp debugging by going to Admin > Health Status and at the bottom change the SugarChimp Logger to Normal.
Closing this case for now. Let me know if you need anything else. Thanks!
9 years ago
Hi SugarChimp,
This is appeared in the debug "failed in cron run" for MailChimp activity to SugarChimp.
Wed Feb 11 09:10:11 2015 [30077][1][FATAL] Job 90f8883e-085c-cf8c-4ea3-54d9025b7f29 (MailChimp to SugarCRM Activity Job - Initial Campaign Activity Import ) failed in CRON run Wed Feb 11 09:10:11 2015 [30077][1][INFO] Resolving job 90f8883e-085c-cf8c-4ea3-54d9025b7f29 as failure: Unexpected failure, please check PHP logs and sugarcrm.log Wed Feb 11 09:10:11 2015 [30077][1][INFO] Will retry job 90f8883e-085c-cf8c-4ea3-54d9025b7f29 at 2015-02-11 01:10:36 (25) Wed Feb 11 09:10:11 2015 [30077][1][DEBUG] Hook called: SchedulersJobs::job_failure_retry Wed Feb 11 09:10:11 2015 [30077][1][DEBUG] Hook called: SchedulersJobs::before_save Wed Feb 11 09:10:11 2015 [30077][1][DEPRECATED] SugarBean.php: preprocess_fields_on_save() is deprecated Wed Feb 11 09:10:11 2015 [30077][1][INFO] Query:UPDATE job_queue SET assigned_user_id='1',name='MailChimp to SugarCRM Activity Job - Initial Campaign Activity Import ',date_modified='2015-02-11 01:10:06',scheduler_id='',execute_time='2015-02-11 01:10:36',status='queued',resolution='failure',message='Forced failure on timeout\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\nUnexpected failure, please check PHP logs and sugarcrm.log\n',target='class::MailChimpToSugarCRMActivity',data='YTo0OntzOjIxOiJtYWlsY2hpbXBfY2FtcGFpZ25faWQiO3M6MTA6IjA1MmIzOTgxMDQiO3M6MTc6Im1haWxjaGltcF9saXN0X2lkIjtzOjEwOiJiMzk3NDYyZjFkIjtzOjEzOiJpbmNsdWRlX2VtcHR5IjtiOjA7czo1OiJzaW5jZSI7YjowO30=',requeue=1,retry_count=25,failure_count=75,job_delay=30,client='CRON1c5d072676309395bd010d69d45b82c7:30077',percent_complete=NULL WHERE job_queue.id = '90f8883e-085c-cf8c-4ea3-54d9025b7f29' AND deleted=0 Wed Feb 11 09:10:11 2015 [30077][1][INFO] Query Execution Time:0.0098340511322021
9 years ago
Hi SugarChimp,
The cron run failed seems to only occur to MailChimp Activity to SugarChimp. The export and import of contact list seems to be working fine.
MailChimp Activity to SugarChimp is a feature for professional version right?
Is that belong to one of these two feature Activity Data Pushed to Sugar and Report on Campaign Activity in Professional version?
What about See Campaign Activity? What are the actual functions for these three features (Activity Data Pushed to Sugar, Report on Campaign Activity and See Campaign Activity)
If only these features are causing issues but not arising from synchronizing the contact details, then we shall consider to use Basic if the features were not really essential to us.
Regards, Ian
9 years ago
I just removed the SugarChimp activity that I created to test after reinstallation, the queue issue is no longer appear in SugarChimp scheduler log.
9 years ago
Thanks again Ian, let us know if you run into anything else. Have a good one!
9 years ago
Hi SugarChimp,
**I removed the activity hence the cron can continue to run. It does not solve the fundamental problem. Therefore, you need to help me understand the queries below so I can decide whether to continue professional version. **
_The cron run failed seems to only occur to MailChimp Activity to SugarChimp. The export and import of contact list seems to be working fine.
MailChimp Activity to SugarChimp is a feature for professional version right?
Is that belong to one of these two feature Activity Data Pushed to Sugar and Report on Campaign Activity in Professional version?
What about See Campaign Activity? What are the actual functions for these three features (Activity Data Pushed to Sugar, Report on Campaign Activity and See Campaign Activity)
If only these features are causing issues but not arising from synchronizing the contact details, then we shall consider to use Basic if the features were not really essential to us._
Regards, Ian
9 years ago
Hi Ian, I misunderstood what you said then, sorry about that.
That's correct MailChimp Activity syncing is a Professional feature.
The Basic edition includes the ability to see the activity data for each contact/target/lead in Sugar using the connector tool, you can set it up using these instructions (follow the steps for Sugar 6): https://www.sugaroutfitters.com/docs/SugarChimp/view-mailchimp-data-in-sugar
The Basic edition also includes the ability to see campaign summary data in Sugar. You can get to this report by going to Admin > SugarChimp Health Status then click on "Campaign Summary Report".
The two views described above just reads the data on-demand from MailChimp when you view them.
The professional edition actually imports that data into Sugar into the custom SugarChimp Activities module. Once they are inside of Sugar in a module, you can then use the Sugar reporting tools to make reports on the data from within Sugar. This is what "Activity Data Pushed to Sugar, Report on Campaign Activity" means.
Unless you have a specific use case for this data in Sugar, usually the reporting tools provided in MailChimp are enough.
If you want to switch to Basic, I would recommend uninstalling SugarChimp Pro, cancel your current SugarChimp trial, start a new SugarChimp Basic trial, install SugarChimp Basic.
If you want to stick with the Pro features, let me know and I can help further debug the activity syncing issues. 99% of the time, issues like this are due to the server or sugar environment that is running.
Let me know if you have any other questions. Thanks!
9 years ago
In a nutshell, can I say the above mentioned is simply more convenient to generate report within Sugar?
If that is the case, we shall downgrade to Basic.
Thanks a lot for your assistance.
9 years ago
I'm happy to help!
I'd say that the pro edition isn't necessarily more convenient, it just provides more records/data inside of Sugar so that if you have special use cases where you want your own Sugar Report/Workflow/Custom script to interact with the activity data you can do so. The reporting tools in MailChimp are far better than Sugar's Reports module, so it's tough to beat MailChimp unless you have a specific use case you're trying to solve on the Sugar side. I hope that clears it up. Thanks!