Yes, this echos my experiences exactly! Using apache ab benchmark alone would NOT trigger the error. I had plenty of RAM available. Seems to be a concurrency bug.
On Jan 19, 10:53 am, VP <vtp2...@gmail.com> wrote: > What is curious is that RAM is still available, with this error. > Monitoring CPU (using top) shows CPU % is about 70% for apache2 (70% > is probably capped by my VPS host, given to each VPS slice). > > And this occurs for a very simple app. I hope Massimo or someone else > can reproduce this error with this app. Note that while testing with > ab, you might have to browse the site, clicking on images, etc. > Otherwise, ab just it the same domain name repeatedly.
