Hi,
But I have tried to reproduce the problem using USR1 and it also
dumped core. I have tried to reproduce the error on Apache 2.0.43 and
the error_log gave a different message. It gave the following message.
[Thu Nov 18 00:00:01 2004] [notice] configured -- resuming normal operations
[Fri Nov 19 00:00:05 2004] [warn] child process 12783 still did not
exit, sending a SIGTERM
[Fri Nov 19 00:00:05 2004] [notice] SIGHUP received. Attempting to
restart
panic: pthread_key_create <<<<<<here is the message
[Fri Nov 19 00:12:33 2004] [notice] configured -- resuming
normal operations
I did a strings on mod_perl and found the panic: pthread_key_create
message. Where can I find this message being generated so that I can
work on it. I also wanted to know if the errors on 2.0.43 and that of
2.0.52 are related.
I did this
# strings mod_perl.so | grep "panic: pthread_key_create"
panic: pthread_key_create
# strings /opt/perl/bin/perl | grep "panic: pthread_key_create"
panic: pthread_key_create
This suggests that the perl interpreter is generating this message.
Where do I proceed from here.
Thanks and Regards,
Pradeep
On Thu, 02 Dec 2004 17:15:51 -0500, Stas Bekman <[EMAIL PROTECTED]> wrote:
> Stas Bekman wrote:
>
>
> > [please don't forget to Reply-All when following up on list's discussion!
> > Thanks]
> >
> > pradeep kumar wrote:
> >
> >> Hi, By sending a "httpd -k graceful" multiple
> >> times does not
> >> reproduce the problem. But kill -HUP definetly produces it. On Apache
> >> 2.0.52 it dumps core with seg fault. On runnig the same on Apache
> >> 2.0.43 it does not produce a core but gives a
> >> "panic:pthread_key_create" error in the error_log.
> >
> >
> > Excellent. Why can't you use "httpd -k graceful" then?
> >
> >> [Thu Nov 18 00:00:01 2004] [notice] configured -- resuming
> >> normal operations
> >> [Fri Nov 19 00:00:05 2004] [warn] child process 12783 still did not
> >> exit, sending a SIGTERM
> >> [Fri Nov 19 00:00:05 2004] [notice] SIGHUP received. Attempting to
> >> restart
> >> panic: pthread_key_create <<<<<<here is the message
> >> [Fri Nov 19 00:12:33 2004] [notice] configured -- resuming normal
> >> operations
> >>
> >>
> >> Are these two problems related. The problem occurs only when the
> >> mod_perl module is loaded. It is not reproduced when it now loaded.
> >
> >
> > I think it just happens to trigger the problem. Looking at the source
> > looks like both approaches should work. Let me ping the httpd-dev list to
> > see if SIGHUP can be used.
>
> So here is the answer from httpd-dev (courtesy of Jeff Trawick):
>
> graceful uses signal USR1; ungraceful restart uses HUP;
>
> so you want to use "kill -USR1" or "httpd -k graceful"
>
> ungraceful is doomed not to work (even normal shutdown) due to problems in
> the MPM implementation:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=23238
>
>
>
> --
> __________________________________________________________________
> Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org http://ticketmaster.com
>
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
