Re: AW: print throwing intermittent Segfaults
Kurt Hansen <[email protected]>
| Newsgroups | gmane.comp.apache.mod-perl |
|---|---|
| Organization | CharityWeb |
| Message-ID | <[email protected]> |
Hello, I started to see the following when I setup a new server on CentOS 5.4 and installed perl modules from CPAN on Dec. 4: Denis Banovic wrote: > This is from the error_log from the RedHat 5 Production machine: > > Apache2::RequestIO::print: (103) Software caused connection abort at > > The guys from rackspace are saying that I should recompile all my perl modules installed directly from CPAN ( see above ) , do you think this would help? > Or has someone another hint? > > I do not see this on another server with CentOS 5.2 and perl modules primarily built Feb 09. I think something has changed in either CentOS, Apache, or the perl modules I use in the interim. I think it has something to do with Apache children being killed either because of size or request limit reached. So, Denis, have you tried adjusting these: > >From my Apache Config: > <IfModule prefork.c> > StartServers 8 > MinSpareServers 5 > MaxSpareServers 20 > ServerLimit 256 > MaxClients 200 > MaxRequestsPerChild 15 > </IfModule> > > The MaxRequetsPerChild especially seems awfully small. Plus, you say you see the problem happening every 30 to 250 requests. (StartServers)8 * (MaxRequestsPerChild)15 = 120. This sounds like roughtly around the time you'd expect Apache children to die. I had MaxRequests set at 2000 and saw the problem intermittently. I'm going to set MaxRequests to 0 to turn it off and see if it goes away. I wonder if something has changed in Apache recently? Or, mod_perl? Both servers are running Apache 2.2.3. One is running mod_perl 2.0.2 and the other one is 2.0.4. Judging on the version numbers...could this be a bug in 2.0.4? Take care, Kurt Hansen