On Thu, 17 Mar 2005 20:00:34 -0500, Stas Bekman wrote:
Andrew, any chance you could minimise the script so that you can still reproduce the problem...
Many thanks for responding, Stas. I'll certainly try.
I fear that the fact that the problem is really very intermittent might hamper this, however. I should also probably have pointed out that there's a PostReadRequestHandler and a TransHandler in the config as well, which I guess may make a huge difference!
To be honest, I was hoping that since the error is so bizarre, it might be easily recognised by someone.
Search the list archives. I think that error was reported multiple times in different contexts. You may find some useful tips in followups to those reports.
I'm restarting Apache a lot at the moment, as I'm doing some development work (on an different application, using a different virtual server, but nonetheless with the same Apache). I have a nagging suspicion that the "handler" error happens after certain restarts -- a further restart seems to clear it. But even then, it doesn't happen 100% of the time.
What may also be relevant is that on occasional restarts, the log fills with several pages of entries like this:
Attempt to free temp prematurely: SV 0xac6c488 during global destruction.
(the SV numbers are different for each). I suspect that the problems occur after a restart that results in those errors. The log from yesterday corroborates this, but I don't yet have enough evidence to be sure.
That's normal if you get this during a hard restart. Apache gives the procs a few secs to gracefully shutdown and then it send SIGTERM which brutally kills the servers. Perl freaks out and starts raining cats and dogs.
-- __________________________________________________________________ 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
