You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by new-httpd User <ne...@slib.fr> on 2001/01/11 22:35:00 UTC

httpd 2.0 on Linux

Hi,

I'm preparing to build a RPM for Apache 2.0.
I'll use it to validate some stuffs like mod_jk/mod_webapp.

Questions :

- What flags must be given to ./configure ?
- Can I use mm 1.1.3 ?

I tried to build yesterday but I run time I've got :

...
[Mon Jan 08 19:54:10 2001] [warn] pid file /usr/local/logs/httpd.pid
overwritten -- Unclean shutdown of previous Apache run?
httpd: cannot allocate scoreboard: Cannot allocate memory
...

Thanks for Any Help ;-)


Re: httpd 2.0 on Linux

Posted by Greg Ames <gr...@raleigh.ibm.com>.
new-httpd User wrote:
> 
> 
> I tried to build yesterday but I run time I've got :
> 
> ...
> [Mon Jan 08 19:54:10 2001] [warn] pid file /usr/local/logs/httpd.pid
> overwritten -- Unclean shutdown of previous Apache run?
> httpd: cannot allocate scoreboard: Cannot allocate memory
> ...
>

another thought:  I've seen this before when virtual memory was _really_
constrained, and I had a huge number of threads and processes specified
in my config file, using the pthread mpm.  

Good luck...a Worthy Cause.

Greg

Re: httpd 2.0 on Linux

Posted by rb...@covalent.net.
> > - Can I use mm 1.1.3 ?
> 
> The second log message below answers this question loud and clear:
> "NO".  This reminds me of the little I know of the problem Apache/APR
> has with the the current (i.e., later than APR CVS) mm: some fudging
> is required when specifying the number of bytes to allocate or to put
> in a shmem pool or something like that.

This is definately the problem.  Basically, MM has requirements for
memory, so that when we allocate shared memory out of MM, if we specify
exactly what we need, it isn't enough to satisfy our request.  Think of it
this way:

Apache initializes shared memory for 1 Meg.
MM creates a 1 Meg shared memory segment, and uses 50 bytes of it (guess)
Apache tries to allocate 1Meg of shared memory.

There isn't 1 Meg left, so we bomb.  Ralf was going to add the options to
the core MM to take care of this case, but we needed it quickly, so I
hacked our version.  I am not interested in upgrading MM, only to have
Ralf finally add this support.  If he adds it, I will upgrade Apache 2.0's
version then.  If not, somebody else can upgrade our MM, or we will just
leave it where it is now.

Ryan


Re: httpd 2.0 on Linux

Posted by Jeff Trawick <tr...@bellsouth.net>.
"new-httpd User" <ne...@slib.fr> writes:

> Hi,

Hi, who are you?

> I'm preparing to build a RPM for Apache 2.0.
> I'll use it to validate some stuffs like mod_jk/mod_webapp.
> 
> Questions :
> 
> - What flags must be given to ./configure ?

stuff to specify optional modules (start with no extra modules and add
them as people complain?), prefix (e.g., /usr/local or something
else)...  you shouldn't have to add anything to configure in order to
get something useful

> - Can I use mm 1.1.3 ?

The second log message below answers this question loud and clear:
"NO".  This reminds me of the little I know of the problem Apache/APR
has with the the current (i.e., later than APR CVS) mm: some fudging
is required when specifying the number of bytes to allocate or to put
in a shmem pool or something like that.

> 
> I tried to build yesterday but I run time I've got :
> 
> ...
> [Mon Jan 08 19:54:10 2001] [warn] pid file /usr/local/logs/httpd.pid
> overwritten -- Unclean shutdown of previous Apache run?
> httpd: cannot allocate scoreboard: Cannot allocate memory
> ...
> 
> Thanks for Any Help ;-)

-- 
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...