wp-super-cache – could not get mutex lock

  • I have looked at 7 pages of support questions for wp-super-cache and cannot find the answer to my problem. I get the error message below at the bottom of the page:

    “Page not cached by WP Super Cache. Could not get mutex lock.”

    the url is auditpundit.com hosted on a linux server.

    Anyone know the fix? Thanks.

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

  • Check the readme.txt, this is in the troubleshooting section.

    Thread Starter brew13

    (@brew13)

    I checked with my domain hosting service and they don’t have servers with mutex lock capability. I use ixwebhosting and thought that they specialized in supporting wordpress . . . I guess not. Thanks!

    Just use file locking, as suggested in the readme.txt. grrr.

    Just use file locking, as suggested in the readme.txt. grrr.

    how i do that ?

    Ok – first off…. readme.txt has nothing that says mutex. I read through and then grep’ped the file…

    [northcarolinagenealogy][~/www/wp-content/plugins/wp-super-cache]$ cat readme.txt | grep -i mutex
    [northcarolinagenealogy][~/www/wp-content/plugins/wp-super-cache]$

    NOTHING – but THANKS for at least mentioning file locking….

    [northcarolinagenealogy][~/www/wp-content/plugins/wp-super-cache]$ cat readme.txt | grep locking
    13. sem_acquire() errors such as “failed to acquire key 0x152b: Permission denied in…” are a sign that you must use file locking. Edit wp-content/wp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value.

    thanks for mentioning locking it got things caching on one of my sites.

    I had this same issue. Making the wp-content/cache/wp_cache_mutex.lock file writable fix the issue. That is also not mentioned in the the readme.

    Ok, that’ll teach me. I updated the code without updating the readme but that’s done now. Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘wp-super-cache – could not get mutex lock’ is closed to new replies.