...lots of them.

First off, let me thank Torsten for the help understanding some of the
environment issues with forking.

I have created a class for running external programs that will be a
little bit smart and a little bit configurable to allow processes to be
run by system() calls directly, IPC::Run3, which uses system, or by
$r->spawn_proc_prog() under mod_perl and also it provides for setting
environment variables via Env::C or by using $r->subprocess_env->set(
$var => $vars->{$var} ) if running under Apache/mod_perl.

Ok, now I've got my programs forking with the proper environment, but
I'm experiencing numerous segfaults.  Same request issued multiple times
and a good number of them result in segmentation faults.  That would be
on the order of once every other request, where each request could fork
about 7 or 8 times.  

We're using DBI here as well, and I understand that there were related
issues with pre 1.3 versions of DBI.

I instantiate the ForkManager, and get into the loop, print out a
message right before I do my '$pm->start and next;', and then I get
this:

[Tue Aug 26 13:56:37 2008] [notice] child pid 19991 exit signal
Segmentation fault (11)

From what I've been able to determine so far, this happens when forking
the first process after creating the ForkManager object.

I'm running:

RHE Linux
Apache/2.2.9 (Unix) DAV/2 mod_apreq2-20051231/2.6.0 
mod_perl/2.0.4 
Perl/v5.10.0 
DBI 1.605

I've tried changing the numbers the prefork mpm to allow for more
Clients, more MaxSpareServers.  My config isn't tuned at all as you can
see:

    StartServers          5
    MinSpareServers       5
    MaxSpareServers      15
    MaxClients          150
    MaxRequestsPerChild   128

Any thoughts or questions?  

Eric D. Berg
Lehman Brothers
> Fixed Income Research
> 745 7th Avenue, 15th floor
> New York, NY 10019
> Phone +1 212 526 8118
> 
> 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - -

This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.

--------
IRS Circular 230 Disclosure:
Please be advised that any discussion of U.S. tax matters contained within this 
communication (including any attachments) is not intended or written to be used 
and cannot be used for the purpose of (i) avoiding U.S. tax related penalties 
or (ii) promoting, marketing or recommending to another party any transaction 
or matter addressed herein.

Reply via email to