Contrib.social

Cron Jobs are not executed

Open on Drupal.org →
Created on 18 May 2013, about 11 years ago
Updated 28 May 2024, about 1 month ago

Hi,

I just set up 'Elysia Cron' on a larger Drupal site (D6) and noticed that within Drupal no Cron jobs appear to be executed anymore.

The module has been set up like documented in the instructions; there is a separate Crontab setting that is supposed to be executed every minute:

* * * * * wget -O - -q -t 1 http://mysite.tld/sites/all/modules/elysia_cron/cron.php

From the server's syslog:

…
May 18 18:41:01 ns225163 /USR/SBIN/CRON[12388]: (root) CMD (wget -O - -q -t 1 http://mysite.tld/sites/all/modules/elysia_cron/cron.php)
May 18 18:42:01 ns225163 /USR/SBIN/CRON[12456]: (root) CMD (wget -O - -q -t 1 http://mysite.tld/sites/all/modules/elysia_cron/cron.php)
May 18 18:43:01 ns225163 /USR/SBIN/CRON[12518]: (root) CMD (wget -O - -q -t 1 http://mysite.tld/sites/all/modules/elysia_cron/cron.php)
May 18 18:44:01 ns225163 /USR/SBIN/CRON[12587]: (root) CMD (wget -O - -q -t 1 http://mysite.tld/sites/all/modules/elysia_cron/cron.php)
May 18 18:45:01 ns225163 /USR/SBIN/CRON[12660]: (root) CMD (wget -O - -q -t 1 http://mysite.tld/sites/all/modules/elysia_cron/cron.php)
…

To this point, Cron appears to be working fine (no errors, no indications of wrong paths etc.)

However, according to "Last run" at ./admin/build/cron, within Drupal no Cron jobs are executed ("Last run" is the time I ran it manually through the "Execute Cron" button).

At ./admin/build/cron/settings I enabled "extended logging (in watchdog)", nothing was logged in watchdog. When I ran Cron again manually, watchdog logged: "Cron channel default run completed."

Having to run Cron manually opposes the whole idea of Cron - executing Cron jobs in the background without user interference. So how do I get Elysia Cron to execute automatically?

Thanks!

🐛 Bug report
Status

Closed: won't fix

Version

2.0

Component

Code

Created by

🇩🇪Germany asb

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment about 1 month ago →
    🇩🇪Germany asb

    New server, trying 'elysia_cron' again on three sites (in the past decade, I had been using 'ultimate_cron', which also did not work reliably)

    Now using 'elysia_cron' 6.x-2.2, LTS version, from Jan 19, 2023 (https://github.com/d6lts/elysia_cron) with PHP 7.3.31-1~deb10u6.

    Results as of May 28, 2024 as shown at the respective ./admin/build/cron admin pages:

    1) Last run: 24.05.2024 - 23:12
    2) Last run: 25.05.2024 - 05:12
    3) Last run: 25.05.2024 - 05:12

    These were the times I ran cron manually via ./admin/reports/status/run-cron.

    According to Legend, everything is in status: "Waiting for execution Job is ready to be executed, and is waiting for system cron call".

    So after a decade, still the identical issue: Cron is not automatically executed according to the settings from crontab; the search index becomes quickly stale and also has to be manually updates (e.g. drush search-index); maintenance jobs like cleaning expired access logs or removing older rows from flood and batch table are not executed unattended.

    Running cron manually from ./admin/build/cron takes an exec time between 25s, 51s, and 87s, so I guess timeouts should not be an issue. Really odd.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024