httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Slive" <>
Subject Re: [users@httpd] Overloaded rewrite handler?
Date Fri, 27 Apr 2007 13:13:12 GMT
On 4/26/07, Aaron Macks <> wrote:
> First a bit of background, the server is a SunFire 440, 4 proc, 8gig of
> ram, running httpd 1.3.34 due to the needs of out closed-source CMS
> We have been trying something that requites a huge number of redirects,
> and it seems that the rewrite engine is running out of memory.
> Here is the memory usage line out of 'top' while the rewrite config was
> in use:
> Memory: 8192M real, 4675M free, 5972M swap in use, 431M swap free
> and here are some snippets of the error log
> [Thu Apr 26 21:45:29 2007] [error] (12)Not enough space: fork: Unable to
> fork new process
> [Thu Apr 26 21:45:40 2007] [info] server seems busy, (you may need to
> increase StartServers, or Min/MaxSpareServers), spawning 16 children,
> there are 0 idle, and 7 total children
> Is there a way to increase the memory available to the rewrite engine,
> or is it using as much as there is already?

I'm not sure why you came to the conclusion that mod_rewrite is at
fault. I find that unlikely. You system is running out of resources to
fork new children with only 7 children active. That is tiny. What else
is going on on this box? How big is each apache child process?

I'm not a sun expert, but one things that looks problematic is your
lack of swap space. It is typical to configure at least as much swap
space as you have physical RAM.

If mod_rewrite is at fault, then the first thing to do is to run the
RewriteLog to check and see if it is looping someplace.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message