Skip to main content
CiviCRM

Return to Answer

deleted 1 character in body
Source Link
artfulrobot
artfulrobot
  • 4k
  • 16
  • 33

Sounds like a cron/scheduled tasks issue.

CiviCRM has a scheduled tasks system to organise jobs that need running at regular intervals. This in turn requires that something pokes it into action frequently (e.g. every 15 mins). Typically on Linux this is done with the system's cron utility.

Without CiviCRM being given chance to run its scheduled tasks, it will only ever do one batch - there's nothing to give it chance to run a second batch.

Setting this up is detailed in the book and on the wiki.

In brief, if you're on Linux + Drupal hosting, then you want a line like this in /etc/crontab

*/15 * *   *   *   <USER>  umask 0002; /usr/bin/php /var/www/your.civi.site/sites/all/modules/civicrm/bin/cli.php -j -s <example.com> -u admin -p 'F<DATABASE'<DATABASE PASSWORD>' -e Job -a execute

Nb. you might like to put those commands in another shell script and then just reference that so as to avoid your database password entering your syslog.

Sounds like a cron/scheduled tasks issue.

CiviCRM has a scheduled tasks system to organise jobs that need running at regular intervals. This in turn requires that something pokes it into action frequently (e.g. every 15 mins). Typically on Linux this is done with the system's cron utility.

Without CiviCRM being given chance to run its scheduled tasks, it will only ever do one batch - there's nothing to give it chance to run a second batch.

Setting this up is detailed in the book and on the wiki.

In brief, if you're on Linux + Drupal hosting, then you want a line like this in /etc/crontab

*/15 * *   *   *   <USER>  umask 0002; /usr/bin/php /var/www/your.civi.site/sites/all/modules/civicrm/bin/cli.php -j -s <example.com> -u admin -p 'F<DATABASE PASSWORD>' -e Job -a execute

Nb. you might like to put those commands in another shell script and then just reference that so as to avoid your database password entering your syslog.

Sounds like a cron/scheduled tasks issue.

CiviCRM has a scheduled tasks system to organise jobs that need running at regular intervals. This in turn requires that something pokes it into action frequently (e.g. every 15 mins). Typically on Linux this is done with the system's cron utility.

Without CiviCRM being given chance to run its scheduled tasks, it will only ever do one batch - there's nothing to give it chance to run a second batch.

Setting this up is detailed in the book and on the wiki.

In brief, if you're on Linux + Drupal hosting, then you want a line like this in /etc/crontab

*/15 * *   *   *   <USER>  umask 0002; /usr/bin/php /var/www/your.civi.site/sites/all/modules/civicrm/bin/cli.php -j -s <example.com> -u admin -p '<DATABASE PASSWORD>' -e Job -a execute

Nb. you might like to put those commands in another shell script and then just reference that so as to avoid your database password entering your syslog.

Source Link
artfulrobot
artfulrobot
  • 4k
  • 16
  • 33

Sounds like a cron/scheduled tasks issue.

CiviCRM has a scheduled tasks system to organise jobs that need running at regular intervals. This in turn requires that something pokes it into action frequently (e.g. every 15 mins). Typically on Linux this is done with the system's cron utility.

Without CiviCRM being given chance to run its scheduled tasks, it will only ever do one batch - there's nothing to give it chance to run a second batch.

Setting this up is detailed in the book and on the wiki.

In brief, if you're on Linux + Drupal hosting, then you want a line like this in /etc/crontab

*/15 * *   *   *   <USER>  umask 0002; /usr/bin/php /var/www/your.civi.site/sites/all/modules/civicrm/bin/cli.php -j -s <example.com> -u admin -p 'F<DATABASE PASSWORD>' -e Job -a execute

Nb. you might like to put those commands in another shell script and then just reference that so as to avoid your database password entering your syslog.