On Mon, Jan 14, 2019 at 21:27:31 -0800, Don Armstrong wrote: > On Mon, 14 Jan 2019, Julien Cristau wrote: > > the last few days our two bugs web hosts have been struggling. We've > > got apache set up with RLimitNPROC 256, which means once www-data has > > that many processes fork() dies with EAGAIN. > > > > In the case of version.cgi that means perl forking to run dot, for > > libravatar.cgi it looks like it's either cp or convert. Either way, the > > failure mode of fork returning EAGAIN is that perl does sleep(5) and > > tries again. Over and over. Which means by the time something happens > > the client has long gone, but we're still holding up one of the 256 > > nproc slots not doing anything useful for quite a bunch of time. > > Is there any reason why we're using RLimitNPROC instead of setting > MaxClients? > MaxRequestWorkers (new name for MaxClients) is set to 150 currently. We could try lowering that or bumping the RLimitNPROC value a bit?
Cheers, Julien
