Closed (outdated)
Project:
Elysia Cron
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jul 2011 at 04:25 UTC
Updated:
22 May 2016 at 08:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jdleonardComment #2
geerlingguy commentedSame here. I get logged out when I click on the run cron link...
Comment #3
rich.3po commentedAlso getting the same problem.
Running from drush command crashes drush, and running from the admin panel causes you to be logged out (which i believe is as a result of cron crashing)
I'm using the cron script method for configuring my cron hooks, if that helps
(bumping up priority as this seems pretty critical...)
Cheers
Comment #4
gotheric commentedI've commited a new (D7) version that should fix the problem.
Let me know if this works, and let me know if drush now is OK (i've tested only running from admin panel).
Comment #5
geerlingguy commentedI will test things out in the next few days; the -dev release with your latest commit won't show up until this evening, and I typically don't pull straight from git :(
Comment #6
rich.3po commentedThanks for the update
It appears that running cron from the admin panel (/admin/reports/status/run-cron) is now working. However, running 'drush cron' still bombs out, unfortunately with a non-helpful error message.
As an additional note (this may belong in a new ticket), after cron is run the 'last run' timestamp does not appear to be updated. This is viewable on the status page here: /admin/reports/status, and makes it hard to determine whether cron ran successfully or not. Also the watchdog message "cron ran successfully" is not being created, which is useful for similar reasons.
Thanks
Comment #7
gotheric commentedThe method to run elysia cron from drush in running "drush elysia-cron", not "drush cron".
Have you tried this?
Comment #8
gotheric commentedNo response, i consider this bug as closed. Reopen it if it's not
Comment #10
obrienmd commentedI'm still having this issue with Drush (running latest stable from Nov 2011). Unfortunately, Aegir queues force us to hit cron via 'drush core-cron', rather than 'drush elysia-cron', so having the ability to run normal cron as Drush entry point (which should then call elysia) is really important.
Comment #11
wiifmSurely a cron helper module that actively breaks existing cron functionality can be considered critical.
Here is the error message the drush produces (not very helpful):
From reading #1140842: Drush command terminated abnormally due to an unrecoverable error. - if you call
exit()explicity in your code, drush will fail to work, grepping through the Elysia Cron codebase, there is such a call on line 168 insidehook_cron().Commenting it out, means that drush will work again
However by commenting out the
exit()call then all other module cron runs will execute as per normal (not desired). So what we really need is a way to allow drush to return success here and still exit().After a bit more research, it turns out that another cron related module has already experienced this issue and have resolved it in the best way that they can - see #1357154: Drush integration: usage of exit() - [Drush command terminated abnormally due to an unrecoverable error.]
Attached is a patch that ports this functionality across to elysia cron.
In any case, I think it needs to be made clearer that
drush cronis not to be run anymore, but ratherdrush elysia-crononly.Comment #12
obrienmd commentedThis works great for me against 7.x-2.x-dev. Would love to get this committed!
Comment #13
Yorgg commentedI confirm that point 3) on issue #1 still occurs in version 7.x-2.1
meaning that using devel's run-cron produces a wsod.
Comment #14
obrienmd commentedWith the patch in #11, 'drush core-cron' just ignores Elysia Cron and runs every cron hook on every run. I'd like to have it run on 'drush core-cron' - is there any way to make this happen?
I would be happy to sponsor work to make this happen!
Comment #15
gotheric commented@obrienmd: thank for your proposal of sponsorship. However i'm already working in a totally new drush support (the current one is very poor), i plan to release a new DEV version in a couple of weeks.
If you want a quick support before that time, you can try applying the patch here:
http://drupal.org/node/939592#comment-6155392
In general, for questions about drush support refer to this issue:
http://drupal.org/node/939592
Comment #16
obrienmd commentedThanks!
Comment #16.0
obrienmd commentedadding detail
Comment #17
kala4ek