By adam_b on
I'm getting this notice frequently (about every 8 hours) in dblog:
The file was not deleted, because it does not exist.
Any thoughts?
I'm getting this notice frequently (about every 8 hours) in dblog:
The file was not deleted, because it does not exist.
Any thoughts?
Comments
ctools?
I have the warning message with a drupal 7 beta 3 installation. The message comes from /includes/file.inc line 1260:
I've displayed the backtrace and it seems to point to ctools (at least in my case):
It looks like the following function should not be executed when running cron (as the comment suggests) but for some reason, the "variable_get('cron_semaphore', FALSE)" test returns FALSE instead of TRUE as the cron_semaphore is set at the beginning of running cron using lock_acquire('cron').
Hope this help as as a starting point (I'm not sure what's next as I have no clue of what/why/when this function ought to do).
Filed issue and patch
See http://drupal.org/node/1001836
Good. — Fast. — Cheap.
(Pick any two.)
happens on every cron run
I am seeing this also ("The file was not deleted, because it does not exist.") and it happens at every cron run. I also have ctools loaded (required by Views).
Did you try the patch?
The problem and a possible correction has been reported; see the comment just previous to your own. The fix is described the following issue:
Unfortunately, that issue is still marked "needs review." You can help the process by applying the patch attached to comment #6.
Good. — Fast. — Cheap.
(Pick any two.)
Patch?
Any thoughts on how to apply a patch through the admin interface or with PHP? I don't have access to the server.
How to apply patch with no server access.
If you have (at least) FTP access, then:
Good FTP programs will auto-detect which files have changed and only re-upload the changed files.
If you don't have FTP access then you cannot patch. Sorry.
Good. — Fast. — Cheap.
(Pick any two.)