I am not sure that my cron run well, because nothing change on the cron interface.

The crons times in the table are not updated. In the status report, the cron is updated correctly but the other informations not (out of date modules, etc...). Is it a normal behaviour or not ?

I mean, if I run my cron only with drush, no information are updated in the cron section in Drupal, but the Cron maintenance tasks in the status report is updated correctly.

CommentFileSizeAuthor
#8 ultimate_cron-drush.patch3.26 KBgielfeldt

Comments

gielfeldt’s picture

gielfeldt commented

Hmmm. Sounds a bit odd.

Have you disabled Ultimate Cron's poorman's feature, and what does your crontab line look like?

michee.lengronne’s picture

michee.lengronne
Primary language French
commented

Yes, I have desactivated poormanscron. here is my crontab:

* * * * * /usr/bin/env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin COLUMNS=72 /usr/local/bin/drush -r /test @sites cron-run --cli all --y > /dev/null 2>&1

gielfeldt’s picture

gielfeldt commented

Hi again

Sorry for the late reply. I have not had time to look further into this, and I have no immediate idea on where the problem lies. I'll see if I can find some time for this tonight.

gielfeldt’s picture

gielfeldt commented

Just to clarify, is it on /admin/config/system/cron or /admin/reports/status that nothing gets updated?

In any case, I can't seem to reproduce this error. Is the problem also present if you run drush cron-run manually?

michee.lengronne’s picture

michee.lengronne
Primary language French
commented

when I do it manually, /admin/config/system/cron works but not /admin/reports/status.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented

Another problem. When I use the cron manually by the drupal interface there is no problem, but when I use it via Drush all the crons are blocked.

It is maybe the origin of the bug. What is the way to debug the crons via Drush ?

gielfeldt’s picture

gielfeldt commented

Hi

I think it might be due to the -r parameter (among others) not being passed to the subrequests.

Does it work when running a single job from drush, e.g.

/usr/local/bin/drush -r /test @sites cron-run --cli ultimate_cron_cleanup_log --yes
gielfeldt’s picture

gielfeldt commented
StatusFileSize
new ultimate_cron-drush.patch3.26 KB

BTW, you're using --cli, but that's only available in the dev-version now that I think of it? Are you using the dev version or 1.6?

If running a single job works, as mentioned in my previous post, I have a patch (for 7.x-1.x-dev) you can try out.

michee.lengronne’s picture

michee.lengronne
Primary language French
commented

Thank you. I will test it when I have time. I don't ude the dev version so, maybe, --cli is the origin of the troubles.

gielfeldt’s picture

gielfeldt commented

Hi

Did this patch work for you?

gielfeldt’s picture

gielfeldt commented
Status: Active » Postponed (maintainer needs more info)
gielfeldt’s picture

gielfeldt commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (fixed)