id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 9698,memcached causes flup fastcgi to crash,Whitney Young ,nobody,"My threaded flup fastcgi instance continues to go down using the latest version of django. The errors I get to stderr are: {{{ [FATAL@1227645879.971403] mcm_fetch_cmd():1181: memcache(4) protocol error: Operation now in progress: server sent data for key not in request [WARN@1227645881.777358] mcm_server_readable():2587: timeout: Operation now in progress: select(2) call timed out for read(2)able fds [INFO@1227645881.777465] mcm_get_line():1597 [FATAL@1227645881.777481] mcm_server_send_cmd():2711: failed to send command to the memcache server: Operation now in progress: Operation now in progress }}} And in lighttpd, the generic: {{{ 2008-11-25 21:39:57: (mod_fastcgi.c.1743) connect failed: Connection refused on unix:site.sock 2008-11-25 21:39:57: (mod_fastcgi.c.2912) backend died; we'll disable it for 5 seconds and send the request to another backend instead: reconnects: 0 load: 1 2008-11-25 21:40:00: (mod_fastcgi.c.3524) all handlers for /site.fcgi/url/ on /site.fcgi are down. 2008-11-25 21:40:03: (mod_fastcgi.c.2725) fcgi-server re-enabled: unix:site.sock }}} Versions: * flup 1.0-1 * cmemcache 0.95 * django 1.0.2 * lighttpd 1.4.19 I've 'fixed' this issue by just restarting my fastcgi instance when it goes down, but any insight (or fixes) would be great.",,closed,Uncategorized,1.0,,invalid,,,Unreviewed,0,0,0,0,0,0