Re: New Windows mod_perl binaries available

Michiel Beijen <[email protected]>
Newsgroups gmane.comp.apache.mod-perl
Message-ID <CABD0r134faPdqn83yWa8S-K3CHp__O5dSEuQK7hc6=JGJv1ejA@mail.gmail.com>
Hi Issac,

Thanks for your response.
On Mon, Apr 29, 2013 at 12:54 PM, Issac Goldstand <[email protected]> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.