latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

About: Istvan Magyar

Sorry, I've not written a description yet. I'll get to it soon!


My Latest Replies (From Various Topics)

Viewing 3 replies - 1 through 3 (of 3 total)
Author Replies
Author Replies
Posted: Tuesday Feb 26th, 2013 at 1:40 pm #43254
Istvan Magyar
Username: istvan

Hi Jason,

Thank you for the detailed explanation.

1. I have checked the mutex lock settings. The lock file does exist in both Semaphore and Flock settings, I guess that means that it reverts to Flock for some reason. (which in itself would be fine if I understand what you are saying).

2. I have set the folder permission to 755 and then to 777. Still no cache file written due to the same error.

3. the traffic on my site is extremely low. how heavy it is on the server I am not sure as it is a cloud hosting package. But on my site itself, a dozen visitors a day. Cache expiration time is set to 604800 seconds, I don’t think that needs to be more does it?

4. “Seeing Mutex Lock notices in Quick Cache comments periodically is normal. Seeing them all the time is not. If you are seeing them all the time, it indicates a problem.”

Well, I see the comment all the time. It is always there regardless to the above settings.

Now what do I do? :)

Posted: Monday Feb 25th, 2013 at 2:38 pm #43178
Istvan Magyar
Username: istvan

Hello?
Any support for this plugin?

Posted: Thursday Feb 21st, 2013 at 10:53 pm #42778
Istvan Magyar
Username: istvan

Hi,

I have the same problem.

The line at the end of the html script is:

‘Quick Cache: failed to write cache, unable to obtain a mutex lock at the moment. Quick Cache will try again later.’

Details I can read from header: ‘Cache-Control: no-cache, no-store, max-age=0, must-revalidate’

I have checked the /wp-content/cache/ directory. Permission is 755. There was a file called qc-l-mutex.lock. It was completely blank, no text. I deleted the file, it keeps coming back, still blank.

I changed the mutex file locking settings to ‘Flock’, same error.

I cleared plugin cache, cleared browser cache, no change.

I tried if the problem disappears with all plugins deactivated, it didn’t, still got the same error message. I deactivated-uninstalled-reinstalled the plugin, no luck.

Please advise us, thanks,

Istvan

Viewing 3 replies - 1 through 3 (of 3 total)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.