Errors: unable to auto purge

Oops, sorry there’s actually much more:

[16-Jun-2014 04:07:37 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1443
[17-Jun-2014 04:05:49 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1132
[18-Jun-2014 04:13:27 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1443
[18-Jun-2014 05:18:37 UTC] PHP Fatal error: Uncaught exception ‘RuntimeException’ with message ‘SplFileInfo::getMTime(): stat failed for public_html/wp-content/cache/quick-cache/cache/http/*-com/2014/04/11/t/pagead2-googlesyndication-com/pagead/js/adsbygoogle-js.v/desktop.html’ in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php:888
Stack trace:
#0 /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php(888): SplFileInfo->getMTime()
#1 [internal function]: quick_cache\plugin->purge_cache()
#2 public_html/wp-includes/plugin.php(546): call_user_func_array(Array, Array)
#3 public_html/wp-cron.php(100): do_action_ref_array(‘_cron_quick_cac…’, Array)
#4 {main}
thrown in public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 888
[19-Jun-2014 04:16:19 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1443
[20-Jun-2014 04:11:29 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1443
[22-Jun-2014 04:05:45 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1039
[23-Jun-2014 04:06:12 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1443
[24-Jun-2014 04:17:22 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1201
[25-Jun-2014 04:07:41 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /public_html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 1443

This sounds like an issue with permissions on the filesystem.

I recommend manually deleting the wp-content/cache/quick-cache/ directory using FTP and then hitting the “Restore” button from the Quick Cache options panel to reset Quick Cache to its default settings.

If you still experience these errors, I would contact your web host and inquire why there might be trouble deleting cache files on the filesystem.

Hi Raam Dev, thank you for your response.

This doesn’t seem to be a hosting issue, because these sites are on two different providers (bluehost and mediatemple) and the issues started at the same time on both after the recent QuickCache update.

Also QuickCache has no problem accessing the cache files when it needs to purge them after updating a post. Those operations show as successful so it would seem the permissions are correct. My best guess was that the operation is timing out when it tries to purge large amounts of files due to the massive amount of cache files generated by QuickCache.

I also can’t delete spam comments on either site now unless I do it one by one, which as suggested in another thread seems to be due to cache purging issues.

I also can’t delete spam comments on either site now unless I do it one by one, which as suggested in another thread seems to be due to cache purging issues.

I’m fairly certain this is related to an existing bug in the current version, which is being tracked and worked on here (a fix will go out with the next release): https://github.com/websharks/quick-cache/issues/159

Perhaps your other issue is related to the same bug?

Hi, I’ve tried your advice of restoring and clearing manually, and even set the cache to expire after 2 days. I’ve played around with it and if I let the cache build for an hour or so I can clear it fine from the QuickCache dashboard. However even left sitting overnight when I try to clear it I get errors. Here’s the latest batch:

Warning: rmdir(/html/wp-content/cache/quick-cache/cache/http/www-filesnews-com/category/mma-combat-sports/page) [function.rmdir]: Directory not empty in /html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 857

Fatal error: Uncaught exception ‘Exception’ with message ‘Unable to clear dir: /html/wp-content/cache/quick-cache/cache/http/www-filesnews-com/category/mma-combat-sports/page.’ in /html/wp-content/plugins/quick-cache/quick-cache.inc.php:858 Stack trace: #0 /html/wp-content/plugins/quick-cache/includes/actions.php(41): quick_cache\plugin->clear_cache(true) #1 /html/wp-content/plugins/quick-cache/includes/actions.php(13): quick_cache\actions->clear_cache(‘1’) #2 /html/wp-content/plugins/quick-cache/includes/actions.php(180): quick_cache\actions->__construct() #3 /html/wp-content/plugins/quick-cache/quick-cache.inc.php(517): require_once(‘/nfs/c09/h05/mn…’) #4 [internal function]: quick_cache\plugin->actions(”) #5 /domains/filesnews in /html/wp-content/plugins/quick-cache/quick-cache.inc.php on line 858

Errors are still pouring in on both sites. Also am unable to post, refresh my Jetpack publicize to Facebook connection, and other tasks until I deactivate QuickCache or clear the cache manually via FTP. Both sites were fine until the last update, and the one thing I can think of that they have in common is that they are both quite large sites (c. 1000 pages and posts each).

Any ideas? I really like the simplicity of QuickCache and don’t want to switch but I can’t be clearing thousands of cache files via FTP whenever I need to perform a simple task on the sites.

I think I just fixed half the issue…permissions, as you said. On the above site I set the permissions to 755 for that folder and was able to clear the cache from the Dashboard.

However the first site (with the error logs posted in my first two messages) has its permissions set at the recommended 755 and continues to get the errors related to the auto-purge function. Hopefully its related to the same bug you mentioned and will get fixed in the next release.

Thanks!

However the first site (with the error logs posted in my first two messages) has its permissions set at the recommended 755 and continues to get the errors related to the auto-purge function.

Hmm, could it be that you need to apply the permissions change recursively? If there are subdirectories that have the wrong permissions, Quick Cache would still be unable to delete those cache directories.

You might try disabling Quick Cache, manually deleting the entire cache directory using FTP, then reactivating Quick Cache and making sure the cache directory has the correct permissions.

There’s one other thing you could do that would help me track this down:

Right after attempting to clear the cache and receiving the error, if you could login via FTP and inspect the directory that Quick Cache was attempting to delete (in error message above, that would be /html/wp-content/cache/quick-cache/cache/http/www-filesnews-com/category/mma-combat-sports/page) and tell me if you see any files in that directory, that would help me.

Looking at the Quick Cache code, it sounds like what’s happening is Quick Cache is thinking that directory is already empty (e.g., it already deleted all cache files from inside that directory) but for some reason that’s not the case and the directory actually isn’t empty, so you’re seeing an error.

If we can figure out what file(s) are in that directory that Quick Cache is not properly deleting, that would help track down this bug, if there is indeed a bug here.