Correction it is WPMU 2.6.1.
buch0090 – do you see any supercache files being deleted? I’m not sure what the problem would be. Do you have any filenames with unusual characters? Are there any files or directories named “\”?
Donncha,
It appears the issue is somehow with the ‘wp_cache_writers_entry’ function when its called by ‘wp_cache_phase2_clean_expired’. It always returns false. (I’ve put in error log when ‘wp_cache_phase2’ is first called and then after the wp_cache_writers_entry is called in there. $mutex variable is empty.
function wp_cache_writers_entry() {
global $use_flock, $mutex, $cache_path, $mutex_filename;
if( !$mutex )
return false;
if ($use_flock)
flock($mutex, LOCK_EX);
else
sem_acquire($mutex);
return true;
}
And when the prune function is called (i’m guessin thats the one that deletes super-cache) $mutex is defined like so…I’ve also installed that ‘cache cleaner’ function which has cleared out super cache files.
Resource id #55
Where do i go from here? Sorry this is a bit hurried, let me know if this makes no sense.
Thanks a ton for responding.
If $use_flock is commented out in wp-content/wp-cache-config.php try removing the “//” in front of it. That may help.
Or you could try changing the value of $sem_id in the same file.
Does that help?
I commented out $use_flock and deleted the expired pages and no difference after 24 hours. Then I changed the $sem_id to a different value and still no difference. Should i be manually deleting ALL files under wp-content/cache before doing these tests or is there something else I should be trying?
Also, I have noticed some wp-cache files with file names like this..
wp-87FC.tmp and wp-cache-industry.htm9d80b39581e2f79bbfc4ad68cd6212ef.html
..could either of these cause problems?
Thanks again in advance for any guidance/help.
Odd. The tmp file shouldn’t have a prefix of “wp-“. It should be completely random. That wp-cache-industry… filename looks strange too because that shouldn’t happen either. Do your urls end in .htm? Do you have a blog called “industry”?
Theres a category named industry. I’m thinking this issue with .htm in filenames is due to old URLs from the old website that people are still trying to access, before it was converted to wordpress.
I added a rule in super-cache settings to not cache files ending with .htm.
Any other ideas? Would you think these issues are mostly due to this site being on Windows? We are planning to move to Linux in the next month.
It seems others have this issue as well, does anyone who isn’t getting expired pages deleted have zeros for the wp-cached pages:
WP-Cache
0 cached pages
0 expired pages
It seems that that wp-cache cannot read the wp-cache files to see how many there are on the site. Going to start digging around a bit for wp-cache problems on WAMP setup.
i am having the same issue. i am quite new to super cache but with the default settings, after one hour, the expired files are still there growing and growing…any ideas?
So is the problem related to the fact that I get this warning when looking at the super-cache settings page?
Warning! \[siteroot]/wp-content is writeable!
You should change the permissions on \[siteroot]\wp-content and make it more restrictive. Use your ftp client, or the following command to fix things:
chmod 755 \[siteroot]\libn/wp-content/
OR is it related to the fact that, since this is on windows, I didn’t do the symlink as described in the readme?
3. Is there a wp-content/advanced-cache.php ? If not, then you must symlink wp-super-cache/wp-cache-phase1.php to it with this command while in the wp-content folder. (WordPress MU users should replace “plugins” with “mu-plugins”.)
ln -s plugins/wp-super-cache/wp-cache-phase1.php advanced-cache.php
