Closed (fixed)
Project:
SuperCron
Version:
6.x-1.3
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Mar 2010 at 13:59 UTC
Updated:
3 Apr 2010 at 08:20 UTC
I have supercron working well. However whenever supercron runs hourly I do not get a log message that it has run, is this by design?
Comments
Comment #1
MisterSpeed commentedYes; there is no logging code at all included after cron runs; in 1.3 (and 1.4-dev) we only log exceptions; it would be very easy to add though, will keep a note of it. Thanks.
Comment #2
MisterSpeed commentedImplemented in 1.4: http://ftp.drupal.org/files/projects/supercron-6.x-1.4-beta1.tar.gz Enjoy !
Comment #3
gmasky commentedI had disabled update module (D6) on two of my sites for some time now as I could not access the admin area if it was enabled (white screen). I have tried cron and then been using poormanscron v1 and v2 but could never get update to work. On one of my sites I just installer suprecron and the next day update module started working. On my second site I had to delete the variables cron_last and cron_semaphore as well as delete update from within system table. The update module started working. I have tried all of this with both versions of poormanscron but could never get update to work.
Thanks for this module as well as for getting supercron to show in the logs
Comment #4
MisterSpeed commentedThanks :) What was rpobably happening is that another hook above Update was most likely crashing. The standard cron solutions do not protect the downstream hooks against that.
Comment #5
gmasky commentedIt seems the update path does not work, update.php did not update to the new version. I had to uninstall the previous version and only then did the new version work. Great Job with the new version.
Comment #6
MisterSpeed commentedThanks :) we had an issue reported about the supercron launcher not working though so for now the best best is to use the autocron feature. We'll work on a fix and post it within about 15 days.
The database schemas haven't changed so update.php has nothing to do. I'll update the installation instructions as well.
Comment #7
gmasky commentedI have downgraded to 1.3 once again as Cron Daemon was throwing up this error
After the downgrade Cron Daemon is now telling me
supercron.php is definitely present in my root directory