Closed (fixed)
Project:
Boost
Version:
6.x-1.18
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
18 Apr 2012 at 05:06 UTC
Updated:
23 Oct 2012 at 09:21 UTC
Jump to comment: Most recent
I receive this error on dblog when cron is executed: "Expired stale files from static page cache".
Could anyone tell me what this message means and how can it be prevented?
Comments
Comment #1
bboybenny commentedI am getting that msg too every time cron is executed, please help. Thanks.
Comment #2
rogeriodec commentedAre you trying to run cron.php, outside of Drupal (via cPanel)?
Comment #3
n20 commentedYes, i do run cron via cpanel and get that message also every time cron runs.
Expired 0 stale files from static page cache.Comment #4
rogeriodec commentedAs I abandoned Boost module in favor of Advanced CSS/JS Aggregation I could not tell you if the following solution would work for you, however I think if you look at the topic http://drupal.org/node/1484456 I created about solutions to cron (especially #12) perhaps this may solve your problem.
Comment #5
bgm commentedIt's a watchdog notice, not an error:
You can reduce your Boost debug verbosity level to silence the message.
Comment #6
n20 commentedYes, you could disable the setting to delete all expired files on cron run. but then the files wont be deleted. lets assume you run cron every minute - this gives you one extra sql-query per minute for the watchdog notice even no files deleted.
we are here in an discussion about the 6.x version. in 7.x version im talking about the code looks like:
may im wrong, but wouldnt it better to have it something like that:
only if files arre really removed you get the notice.
not sure about the 6.x version...
Comment #7
n20 commentedi created a new issue for the 7.x version here: http://drupal.org/node/1807186
cheers, N20
Comment #8
Anonymous (not verified) commentedThe general scenario is this. The site administrator sets up cron to run hourly/ daily, the pages are set up to expire weekly. He/ She checks the logs and see that boost is running even if it's not expiring anything. If something breaks, then the dblog provides a trail as to when it stopped working, even expiring 0 pages.
Another example from a debugging POV, the dblog states that 0 pages have been expired but the pages in the cache are older than a week, so something is wrong and the 0 pages has pointed that out etc...
Comment #9
n20 commentedgood point. the _boost_rmdir() does not provide any logging if something goes wrong... as far as i can see.
however, there is some kind of check if boost is "up and running" at: admin/reports/status
not sure whats underlying this check.
Comment #10
Anonymous (not verified) commentedI believe the status report is very dismissive :-) Yep, you've got boost installed, it should be working if properly configured.
I'm (newest member) working through the back issues to clear down the queue then I'm going to have a hard look at status updates for boost, because a lot of issues are non-specific with no means of debugging. Some also seem to be features by design so I need to work on the documentation.