I’m seeing this error on my blog’s front page. When W3C is configured to cache the front page in memcached, such requests return a 500 error. If I disable memcached, or configure W3C to not cache the front page, it is served properly. I therefore believe the error is related to memcached.
I started a memcached server with the -vv option to see client commands and server responses. Here’s some example output. 9132ff75232182b4e3b1de9ba6cf6fdc
is the front page. I separated HTTP requests with a blank line. The first and second requests work; the third returns an HTTP 500.
<30 new auto-negotiating client connection
30: Client using the ascii protocol
<30 get w3tc_0_pgcache_0_779812058_key_version
>30 END
<30 set w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0 3 3600 15871
>30 STORED
<30 get w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0
>30 sending key w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0
>30 END
<30 get w3tc_0_pgcache_0_779812058_key_version
>30 END
Failed to write, and not due to blocking: Connection reset by peer
<30 connection closed.
<30 new auto-negotiating client connection
30: Client using the ascii protocol
<30 get w3tc_0_pgcache_0_779812058_key_version
>30 END
<30 set w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0 3 3600 15869
>30 STORED
<30 get w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0
>30 sending key w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0
>30 END
<30 get w3tc_0_pgcache_0_779812058_key_version
>30 END
<31 new auto-negotiating client connection
31: Client using the ascii protocol
<31 get w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0
>31 sending key w3tc_key_hashbang.ca_0_pgcache_9132ff75232182b4e3b1de9ba6cf6fdc_0
>31 END
<31 get w3tc_0_pgcache_0_779812058_key_version
>31 END
This issue will be fixed in upcomming release.
Frederick, did the fix for this get released in .11, or are we still waiting for that?