This is a total long shot, but we spent alot of time figuring out a similar issue that ended up being ephemeral port exhaustion.
Stephen Johnston On Tue, Sep 15, 2009 at 8:27 PM, Vladimir <[email protected]> wrote: > > nsheth wrote: > >> About once a day, usually during peak traffic times, I hit some major >> load issues. I'm running memached on the same boxes as my >> webservers. Load usually spikes to 35-50, and I see the apache error >> log flooded with messages like the following: >> >> [Sun Sep 13 14:54:34 2009] [error] [client 10.0.0.2] PHP Warning: >> memcache_pconnect() [<a href='function.memcache-pconnect'>function. >> memcache-pconnect</a>]: Can't connect to 10.0.0.5:11211, Unknown error >> (0) in /var/www/html/memcache.php on line 174, referer: xxxx >> >> Any thoughts? Restart apache, and everything clears up. >> >> > > > It's PHP. I have seen something but in last couple weeks it has "cleared" > itself. It could be coincidental with using memcached 1.4.1, code changes > etc. I actually have some Ganglia snapshots of the behavior you are > describing here > > http://2tu.us/pgr > > Reason why load goes to 35-50 is that Apache starts consuming greater and > greater amounts of memory indicating a PHP memory leak. Granted it could > also have something to do with session garbage collection. > > I'm running memcached 1.2.5 currently (which looks to be a bit out of >> date at this point, so perhaps an update is in order). >> >> > I think that would be a wise choice. > > Vladimir > >
