CODEWITHSUNDEEP
cronsugarcrm
dkeeper09
dkeeper09

Reputation: 547

Setting up Crontab in SugarCRM

I need some help setting up my crontab for SugarCRM.

My SugarCRM log just looks like this:

Wed Aug 21 10:36:02 2013 [5145][1][FATAL] Job runs too frequently, throttled to protect the system.
Wed Aug 21 10:37:01 2013 [5156][1][FATAL] Job runs too frequently, throttled to protect the system.
Wed Aug 21 10:38:02 2013 [5181][1][FATAL] Job runs too frequently, throttled to protect the system.
Wed Aug 21 10:39:02 2013 [5196][1][FATAL] Job runs too frequently, throttled to protect the system.

I run crontab -e and this is what I have in it:

*    *    *    *    *     cd /var/www/sugarcrm; php -f cron.php > /dev/null 2>&1

I have my "Run Mass Email Campaigns" job running once an hour. My campaign emails aren't being sent. I can send them if I go into the Email Queue and click the Send Queued Campaign Email button, but even then it only sends out about 500. I have about 50,000 to send out lol. Any help with the crontab is greatly appreciated.

Upvotes: 4

Views: 5475

Answers (2)

pepper
pepper

Reputation: 1772

To make it upgrade safe just add this to your config_overrite.php

$sugar_config['cron']['min_cron_interval'] = 0;

Upvotes: 3

Ken Brill
Ken Brill

Reputation: 91

OK, The problem is that you are running the cron every minute, and it used to work that way fine. It still does sort of. They just found that it was bogging down systems too much, a new instance of the scheduler would start to run while the last one was still running.

so you have 2 choices

1) run the cron every 30 minutes. This should make that warning go away

2) Edit the file include/SugarQueue/SugarCronJobs.php and change the variable 

    public $min_interval = 30;

to 

    public $min_interval = 0;

This, of course, will not be upgrade safe but it is perfectly OK to do. You just have to make sure you update the file every time your instance is upgraded.

Upvotes: 2

Related Questions