By nosro on

I'm having a problem with the Boost module where expired files are not being cleared. I rechecked my settings, using the Boost handbook as a reference, and I noticed this button's function described in more detail:

"Clear Boost expired data:

Clears all pages that are past the cache lifetime. You may have been logged in during the cron run and nothing was cleared due to being logged in. It's like a manual cron run."

This seems to be saying that Boost will not clear expired pages on a scheduled cron run if you are logged in. Does this mean if the admin account is logged in? Or any user with admin permissions (like site config)? Why is that? Is there a way to prevent this behavior and clear all expired pages on every cron run, regardless of whether the admin is logged in or not?

The Boost module is great and has helped my server performance quite a bit. It's just this issue which is causing me some trouble as I'm trying to fine tune the cache cycle.

Thanks to anyone who knows the answers!
Orson

⋅ Categories: Drupal 6.x

Comments

mikeytown2’s picture

mikeytown2 commented

Yeah I need to fix the documentation for that then
http://drupal.org/node/545908#psa

This part is false
"You may have been logged in during the cron run and nothing was cleared due to being logged in." That doesn't happen, I don't think its ever happened as that's fairly odd behavior. Just did a quick run through boost_cron() and there is no code in there that could do that.

This is a bug in the documentation; that has now been fixed. If you have something else, please drop a line in the boost issue queue.
http://drupal.org/project/issues/boost

jsharp’s picture

jsharp commented

Mikeytown2,

let me start off by saying THANK YOU for a great module. We used it to launch a new site on Monday (~1600+ conc. users on one Solaris 10 box with a separate MySQL server) and without it we would have been DOA or on the hook for $ignificantly different hardware.

I have noticed, however, that while our cron runs (actually using supercron 6.x-1.13) and the dblog shows the appropriate Boost "Expired stale files from static page cache." message, the expired data does NOT get cleared. We have supercron running every 15 minutes, btw, and our default max cache lifetime is set to 1 hr.

If, on the otherhand, I go to the supercron (admin/settings/supercron) page and either manually Invoke All or manually Invoke specifically the boost entry, then the expired data DOES get cleared. The dblog shows the same, successful "Expired" message--the only difference is that my user ID is shown in this entry vs that of anonymous for the automated cron run.

We are not running the crawler, no agressive tweak options...nothing was changed from the default install of 6.x-1.17.

Fyi, next week we'll upgrade to D6.15 and a few other module updates.

Any assistance or clarification would be much appreciated, as we would really like the automatic cache clearing to work.

Thanks again,
Jason

** EDIT: I just posted this as an issue with more detail, after realizing that would be a better place for it (http://drupal.org/node/678336)