perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Issac Goldstand <mar...@beamartyr.net>
Subject Re: New Windows mod_perl binaries available
Date Mon, 29 Apr 2013 14:08:53 GMT
First of all, see if you can get a stacktrace.

There's also always spreading print/debug statements around - I'm
unfortunately not so up-to-date on the various perl profiling modules
around, but they might be helpful.

  Issac

On 29/04/2013 14:16, Michiel Beijen wrote:
> Hi Issac,
> 
> Thanks for your response.
> On Mon, Apr 29, 2013 at 12:54 PM, Issac Goldstand <margol@beamartyr.net> wrote:
> 
>> This is a known issue related to the winnt MPM.  You're likely seeing
>> your worker segfault.  On linux, there are usually extra processes so if
>> one segfaults there's another process that can step in fast enough.  But
>> on the winnt MPM, there's one master and exactly one multi-threader
>> worker.  So when that worker blows up, the master needs to completely
>> tear it down, and bring it back up, which is what you're seeing.
>>
>> Look for a bug in user-code, not in the mod_perl binary.
> 
> But if the worker 'blows up', this is still caused by some code I run right?
> If I set the Apache log level to 'debug' I still see nothing in the
> logs except for the restart.
> 
> What should I do to find out *what* is causing the restart?
> --
> Mike
> 


Mime
View raw message