I tried running the mc_conn_tester script, but wasn't able to trigger the 
problem with that.
 
The interesting thing is that even if I close down all apps that are 
communicating with memcached, eg. Apache (due to the pecl memcached 
modules), the memcached daemon still has thousands of CLOSE_WAIT 
connections.  There are no other outstanding apps or connections talking to 
it, yet there are thousands of sockets stuck in a CLOSE_WAIT state.
 
Shouldn't memcached be cleaning those up as the sockets hard close?
 

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to memcached+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to