On my live site the only way I can get cron to run is to do it manually even though I have the crontab set to 1 hour - this causes problems with search as the site is not being indexed on a regular basis . As I have additional modules which I thought might be causing problems I decided to test the cron by creating a vanilla open outreach site using Pantheon, check the cron and then add in the additional modules.
I set the vanilla site's cron tab to 1 hour but it is behaving in exactly the same way - cron only runs if I do it manually.
Is there something I am missing?


nedjo’s picture

When you config cron at admin/config/system/cron, a user must visit the site after the cron period has passed. See documentation for Drupal 7 here: http://drupal.org/cron. If you are having issues, you can consult the log for any error messages.

alicemoon’s picture

yes I read the cron documentation.
Cron does not appear to run on either the live site (regular visits by users) or the test vanilla site (I have two users created to test it) - both sites have crontab set to 1hour.
I can get cron to run via admin/config/system/cron and click the run cron button - then I get a log message to say that cron has run successfully - I get no cron log messages other than that and no errors relating to cron.

alicemoon’s picture

I have managed to get crontab to run on the live site using c-panel and curl as my hosting service prevents wget and lynx.
However I could not identify why cron was not triggered when a user visited the site - I had no error messages in the log and it ran fine if I did it manually - this was true for both the live and test site.
A vanilla drupal 7 site runs cron as it should but with the vanilla openoutreach the cron is not triggered by a user visiting the site

firesidelibrarian’s picture

I am experiencing the same problem on 7.x-1.2

edubacco’s picture

I have exactly the same problem on my site, both in production site, visited by many people everyday and in development site.
I've installed the openoutreach-7.x-1.1 version.
I've also installed these modules:

  1. auto_entitylabel
  2. botcha
  3. devel
  4. devel_themer
  5. google_analytics
  6. i18n
  7. l10n_update
  8. languageicons
  9. lightbox2
  10. moopapi
  11. shadowbox
  12. simplehtmldom
  13. variable

Edit: cron is set to automatically update every hour

edubacco’s picture

Priority: Normal » Major
Issue summary: View changes

Updated priority to major, because more people experience this issue, and cron is important for the site healt.

thangarajks’s picture

firesidelibrarian’s picture

In response to #7, I have used my web host to set a regular cron run, but that does not seem to trigger the indexing needed.

fr34ck’s picture

I have the same issue.
The #7 don't resolve, like the #8 i have used my web hosting to set the cron.

firesidelibrarian’s picture

Is there a fix for this issue any time soon?

ergonlogic’s picture

This issue is categorized as a 'support request'. This implies that work-arounds and other suggestions are the appropriate deliverables. If you feel this is a bug in Open Outreach, then I suggest updating the category to 'bug report'.

nedjo’s picture

Version: 7.x-1.0-rc8 » 7.x-1.x-dev
Category: Support request » Bug report

It appears that, at least on some Open Outreach sites, the 'install_task' variable is not properly set to 'done' when installation is completed. This prevents cron running. See system_run_automated_cron() for the relevant code.

To fix the issue on a given site, set the variable to the expected value. For example, you could do one of the following:

  • Install and enable the Devel module, visit /devel/php, enter
    variable_set('install_task', 'done');

    , and submit.

  • If you use drush, run drush vset install_task done.
  • Edit your settings.php file and add the following line in the $conf section:
    $conf['install_task'] = 'done';

If you try this, please report back here as to whether it's fixed the issue on your site.

I'll look into fixing this in Open Outreach and adding an update for existing sites.

nedjo’s picture

I edited comment #12 to correct an error, so if you try the fix be sure to get the corrected version in #1897076-12: Cron not running.

  • Commit 4b3ca6d on 7.x-1.x by nedjo:
    Issue #1897076: address cron issues by explicitly setting the...
edubacco’s picture

I used the fix in #12, point 3, and worked for me.

nedjo’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

stevenx’s picture

#12 worked for me too