I see the message "No channels ready to be executed, skipping cron." in my dblog when debug is enabled for elysia cron and I run it by clicking "Run cron" at admin/config/system/cron or when I invoke elysia_cron_run(TRUE) from within PHP. I have many jobs set to run at 2 minute intervals but if I run this command 60 times over 60 minutes, I see 60 log entries with this message. What am I doing wrong?

Comments

charlie-s’s picture

charlie-s commented

When I visit the elysia_cron status page, I see something like this:

Last run: 08/23/2012 - 10:27
Channel: default (Running since 08/23/2012 - 10:22)
Last run: 08/23/2012 - 10:22

Why are there 2 runs? Is the second run for the channel "default"? If elysia_cron runs every minute, why aren't all of these timestamps the same?

charlie-s’s picture

charlie-s commented

I upgraded to dev to get things running again. The current stable release for D7 doesn't seem to be executing any cron hooks.

gotheric’s picture

gotheric commented

New DEV version has a great code refactoring in several functions... i plan to release it soon.

Sinan Erdem’s picture

Sinan Erdem commented
Category: support » bug
Priority: Normal » Critical

Can you put a notification to the project homepage to direct the users to the dev version? Current stable version is not executing any crons, which seems like a major bug.

OldAccount’s picture

OldAccount commented

I'm using 7.x-2.1 and was getting this message too, but only when I had "debug mode" enabled in the "Installation Settings" section in the Settings (admin/config/system/cron/settings). Just mentioning this in case some people accidentally have that enabled, I'm not having any problems with this version.

muschpusch’s picture

muschpusch commented
Priority: Critical » Normal

I can confirm that the message disappears in current dev. I installed Elysia Cron to debug my cron jobs so I think it would be nice to have a new release. I'm pretty sure that this is no critical bug just a confusing message...

muschpusch’s picture

muschpusch commented
Issue summary: View changes

typo

lissy’s picture

lissy commented
Issue summary: View changes

I am working with elysia_cron 7.x-2.1.
I am importing a number of feeds with a cron-hook.
This has funktioned for some time and know I get suddently the message "No channels ready to be executed, skipping cro" with and without Debug-Mode.
I don't get other error messages.

kenorb’s picture

kenorb commented
Related issues: +#1952624: Automatic cron runs stop working: "No channels ready to be executed, skipping cron." on every run.
kala4ek’s picture

kala4ek
Primary language Russian
Location 🇷🇺 Novosibirsk
commented

@kenorb, does it still actual in latest dev release?

xaqrox’s picture

xaqrox
he/him
Primary language English
Location Washington, D.C.
commented

having this same issue. I'm hittin cron.php via wget in my crontab, the master "Last Run" count goes up once a minute, but all tasks seem to run once an hour, even the once set to go once a minute.

manasiv’s picture

manasiv commented

I am facing the same issue with drush cron:
$/drush/drush cron --root=/var/www/html
No channels ready to be executed, skipping cron.

Is there a cooling period after every cron run?

jukka792’s picture

jukka792 commented

I am facing same issue with the latest version 7.x-2.5
Everything was working fine for a long time, I am importing multiple feeds.
Now only "feeds_cron" is constantly running, and none of the others are executed.
Log says "No channels ready to be executed, skipping cron."
I did uninstall the module and installed it again, no help

jeffreysmattson’s picture

jeffreysmattson
Primary language English
commented

I am having this issue with 7.x-2.4.
Was working for a very long time.
Now "No channels ready to be executed, skipping cron."

Update:
I discovered that the "No channels ready to be executed, skipping cron." statement occurred when the Acquia cron ran the sites cron tasks. Since these tasks ALSO had cron times set for them, if the Acquia cron ran before those set times had passed, it would return this statement.

In other words, if the Aqcuia cron runs every minute (60 an hour) and your site cron jobs are set to every 2 minutes, you are going to get the "No channels ready to be executed, skipping cron." every time a cron it attempting to run but hasn't passed the 2 minutes since execution.

Hope that saves somebody some time. :-)

kala4ek’s picture

kala4ek
Primary language Russian
Location 🇷🇺 Novosibirsk
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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