Return-Path: Mailing-List: contact modperl-help@apache.org; run by ezmlm Delivered-To: mailing list modperl@apache.org Received: (qmail 29358 invoked from network); 2 Mar 2000 22:51:09 -0000 Received: from adsl-216-103-208-11.dsl.snfc21.pacbell.net (HELO mojo.covalent.net) (216.103.208.11) by locus.apache.org with SMTP; 2 Mar 2000 22:51:09 -0000 Received: from localhost (dougm@localhost) by mojo.covalent.net (8.8.8/8.8.8) with ESMTP id OAA24399; Thu, 2 Mar 2000 14:47:02 -0800 X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs Date: Thu, 2 Mar 2000 14:47:02 -0800 (PST) From: Doug MacEachern X-Sender: dougm@mojo.covalent.net To: Bill Moseley cc: modperl@apache.org Subject: Re: exit signal Alarm Clock (14) In-Reply-To: <3.0.3.32.20000301101207.00776750@fpage3.ba.best.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 100/1000/N On Wed, 1 Mar 2000, Bill Moseley wrote: > > That message is generated in http_main.c when a child exists with a signal. right. > They seem to always happen about 5:03 minutes after the last logged > Apache::RegistryNG request for that child. Apache Timeout is set to five > minutes. This leads me to think that some non-mod_perl request is > following a mod_perl request, and timing out. when you log the RegistryNG request, to you include the url? i mean, do you know which script is triggering the problem? seeing that would help a great deal. > In my testing I'm unable to reproduce the error by doing a request to > mod_perl script, and then doing a request to a mod_cgi script that sleeps > for longer than Timeout. That works fine and as expected. And I've never > been able to reproduce the message on my test server. it's easy to reproduce the error message: local $SIG{ALRM}; alarm 1; sleep 2; SIGALRM restoration is not broken in this case, there's just no handler in that scope. we just need to figure out how your code is triggering it. > I don't want to enable mod_perl 'g' debugging due to the volume on our live > system. Is there a way I could just enable this one debugging message? > > MP_TRACE_g(fprintf(stderr, > "mod_perl: restoring SIG%s (%d) handler from: 0x%lx to: 0x%lx\n", > my_signame(sigs[i]->signo), (int)sigs[i]->signo, > (unsigned long)Perl_rsignal_state(sigs[i]->signo), > (unsigned long)sigs[i]->h)); > > I tried to remove the MP_TRACE_g() wrapping around fprintf(), but it won't > compile. My C skills are weak to say the least. what's the error message?