Realized my comment (http://drupal.org/node/674914#comment-2447256) probably should have been an issue, so here goes with more detail:

Solaris 10
Apache 2.2.14
PHP 5.2.11
MySQL 5.1.30
Drupal 6.14
Supercron 6x-1.3

Our supercron is configured to run every 15 minutes. Boost max cache lifetime is set for 1 hr. The dblog shows appropriate Boost "Expired stale files from static page cache." message at the supercron intervals, however the expired data does NOT get cleared.

Manually running the boost cron hook via supercron's UI (admin/settings/supercron), either through Invoke All or specifically Invoke 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.

I apologize if this is something obvious that we simply missed out of the docs or the configuration settings. We found both fairly complete and straightforward, and furthermore the defaults seemed good enough for our needs. The fact that there is a different behavior between the automatic cron run vs. the manual one makes me wonder if there is something outside of our settings.

I have attached a screenshot of the settings (after a recent manual clearing of the expired cache) we are using for your convenience.

Thank you again for an awesome module, and thanks in advance for any guidance you may provide.

Sincerely,
Jason

CommentFileSizeAuthor
Performance_boost_settings.png212.21 KBjsharp

Comments

jsharp’s picture

jsharp commented
Status: Active » Closed (fixed)

I'm marking this closed, as I believe I understand what was happening. The cache is clearing fine now, and the change I made was to set to clear all sites (for the multi-site setting).

Explanation: We only have one site, however I was noticing in the cache folder several host names. Our site is a company intranet (the employee portal), and as it was rolled out it was referenced by several DNS names, including short ones (e.g. intranet) vs. fully justified ones (e.g. intranet.company.com). And I also realized that the OS-level cron job was hitting the supercron/cron script with the actual IP address (which made for yet another "site"). Consequently, I believe the cache was being cleared only for the "IP site" and not the other "sites". However, when invoking supercron and cron from my browser, anonymous or as an entitled user, since I was specifying the sitename, it did the right thing.

Anyway, sorry for the hassle. Hopefully this will help others who stumble along something similar.

One last time, I've got to say: awesome module!

Vayira’s picture

Vayira commented

Thanks for posting that. I was having the same problem & seem to have solved it with the same solution.

Boost makes 4 separate caches for our site (which is not actually multidomain)
www.mysite.com
www.mysite.es
mysite.com
&
mysite.es

So I have to run cron 4 times.

tran_tien’s picture

tran_tien commented
Status: Closed (fixed) » Active

Same here, auto cron running good but do not clear boost expired cache, when i try run cron manualy or run directly via cron.php, boost clear cache immediately.

My cronjob command :

/usr/bin/php /home/mysitesite/public_html/cron.php

Please tell me how to fix this.

aze2010’s picture

aze2010 commented

subscribing

please help...cron doesnt clear expired cache!