There are no known bugs in this area (no reason to expect improvement
by upgrading Apache). Note that if Apache is not stopping cleanly the
semaphore won't be cleaned up.
You'll need to manually clean up the semaphores. Use "ipcs -s" to
display ids on Linux and "ipcrm sem <id>" to remove sem on Linux.
You can switch to another mutex mechanism ("AcceptMutex fcntl" in
httpd.conf) to work around this problem if your Apache is consistently
crashing or you're using a 3rd party module which allocates sems and
doesn't clean up.
Maurizio Marini <[EMAIL PROTECTED]> writes:
> Hello
>
> Redhat 7.3, apache 1.3.23-14 and the rest by distribution
>
> we are noting in a production env. that after stopped, apache deny to start
> again for shortness of Semaphore Arrays
> the default by distro is 128 arrays for a total of 32k semaphores
>
> the strange thing is that apache consumes 1 sem for each array
> so, after 128 sem, the count is exhausted
>
> we are wondering , then, if this is a known bug solved in next apache
> releases;
> we are installing 1.3.27, we hope in this one the problem is fixed
>
> we would add that this is a rev-proxy web server, so mod_proxy and mod_rewrite
> are intensively used
> 10x in advance for your help
> --
> Maurizio Marini
>
--
Jeff Trawick | [EMAIL PROTECTED]
Born in Roswell... married an alien...
