Closed (fixed)
Project:
SuperCron
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Jun 2009 at 13:14 UTC
Updated:
25 Jun 2009 at 23:10 UTC
I keep getting this in my dblog/watchdog table after a supercron run (see attached).
| Comment | File | Size | Author |
|---|---|---|---|
| Picture 1.png | 33.17 KB | geerlingguy |
Comments
Comment #1
geerlingguy commentedHmm... this seems to happen only when I run cron via the Administration Menu's "Run cron" command.
Comment #2
MisterSpeed commentedInteresting case; I'm having some difficulty duplicating it. Normally, the Run Cron command should call admin/reports/status/run-cron which doesn't use supercron.php at all. If it was crontab calling it the entry wouldn't appear in dblog as Drupal isn't bootstrapped yet, so errors of any kind would just be dumped to standard output.
The only plausible cause that I can think of would be when running multithreaded hooks if the file supercron.php either wasn't located in $base_url or if it wasn't accessible to the web server. If you simply open your home page to http://site/supercron.php do you also get an error ?
If so it may make sense to add a sanity check to the code to verify that supercron.php is well-located and has the proper permissions; if that doesn't solve the problem could you pl. run ConfigDoc and append the report ?
Comment #3
tseven commentedI'm getting the same error.
The problem seems to be the link to the watchdog-error.png file.
This is where the link is pointing to:
http://domain.com/drupal/misc/watchdog-error.png
Notice the extra 'drupal' dir.
This should be removed.
Comment #4
MisterSpeed commentedGot it; thanks. I've replaced those by theme_image() which should be better than hardcoded URLs; it is in the CVS. If the change works for you to remove the log entries pls. close the ticket.
Comment #5
MisterSpeed commentedComment #6
geerlingguy commentedHaven't had time to test yet... had a few big events (sorry about that)!
I'll test in a few days.