Closed (outdated)
Project:
Elysia Cron
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Sep 2011 at 00:57 UTC
Updated:
26 Apr 2016 at 16:38 UTC
Jump to comment: Most recent
Comments
Comment #1
gotheric commentedThe jobs you are running should write something to dblog?
(= if elysia_cron is disabled logs are written to dblog?)
If so:
1) try use standard cron mode:
Elysia cron is active even in that mode (just A LITTLE slower).
2) Try enabling debug mode in elysia cron settings page, and see if elysia_cron logs are written.
Let me know your results, i'm interested in this bug.
Comment #2
candelas commentedat the end it was a problem of the server.
they change something on permisions and now it works perfect.
thanks a lot!
Comment #3
gotheric commentedComment #4
jelo commentedSorry, I have a similar question and am setting this back to active. Could you please clarify if Elysia Cron is supposed to leave a message in the watchdog if debugging is disabled or not? The original cron job left the message "Cron run completed." after each cron execution in my log. With Elysia I do not get any message in the log, however, in the Elysia status screen I can see the # of job executions for each individual cron hook based on my timing settings. If I turn debugging on, I get a lot of message (every minute when cron is skipped and actually for each execution of cron hooks). So everything works, I am just not sure if I should be getting any additional stuff in the watchdog if debugging is off. Given that Elysia now runs every minute on my site, I am not even sure if it would be appropriate to have entries in the dblog. Maybe this could be a feature: the option to configure for each hook if a log message should be made in the dblog? In my scenario I would not want messages for hooks such as captcha, but database backups (which I only run once a day) might be helpful to have in the dblog.
Comment #5
gpk commentedYou should get messages like "Cron channel default run started." and "Cron channel default run completed." whether or not you have extended (debug) logging enabled.
Am splitting your suggestion out into a separate issue #1539410: Option to enable extended (debug) logging for specific hooks.
Comment #6
akki123 commentedI get the cron message in dblog after enable debugging. It was skipping cron run due to global disable while install.txt says to disable it. I got cron working after enable global disable.
I am using system cron
* * * * * wget -O - -q -t 1 http://www.example.com/sites/all/modules/elysia_cron/cron.php?cron_key=1...
Comment #7
kala4ekDrupal 6 is not supported anymore.