We had an incident like that back in our development of our pages. We tracked it down to someone having set EMBPERL_DEBUG to -1 in one of their pages, and assumed that the automatic garbage collection at the end of the page would fix it up. So whenever an apache child showed that page, it'd start logging like this.
I found it by grepping the log file for EMBPERL_DEBUG, if I remember correctly. Note that it didn't actually log the section that did it to us on the *first* pass through that page for any child. But it did, of course, tattle if a child showed the same page twice. Of course, if the bug was in perl code, rather than one of our pages, we wouldn't have caught it that way. Instead, we'd have caught it from my earlier grep of all of our perl code and all of the non-EmbPerl library code for EMBPERL_DEBUG. Note that, while it wouldn't solve your issue, you could make a web page to report those same variables, and when you found out which one was wrong, modify some pages to fix it. Of course, this sort of kludge-fix should only be used as a last resort. I am assuming that all of your processing is within Apache. We've also had an issue regarding excessive debugging output from offline processing, that was initially blamed on our more prominent Apache-directed processing. Ed On Wed, 12 Dec 2007 [EMAIL PROTECTED] wrote: > Folks, > > We run Embperl 1.3.6 under mod_perl 1.29 and Apache/1.3.31. Recently we'd > noticed that Embperl seems to be logging "everything." So much stuff that > we have to truncate them every hour or so. > > Below is a snippet from one of our httpd.conf files, which contains the > embperl directives. It looks like this was intended to shut off Embperl > logging, but it's not working. I've tried to debug this, for instance by > using PerlSetEnv to set the variables, or setting EMBPERL_DEBUG to 1. The > only thing that's been effective so far is setting the EMBPERL_LOG to > /dev/null - not a very elegant elegant solution there. > > 7 PerlSetEnv EMBPERL_SESSION_HANDLER_CLASS no > 8 SetEnv EMBPERL_SESSION_HANDLER_CLASS no > 9 SetEnv EMBPERL_OPTIONS 1024 > 10 SetEnv EMBPERL_COMPARTMENT test > 11 SetEnv EMBPERL_LOG /some/custom/directory.txt > 12 SetEnv EMBPERL_DEBUG 0 > > Any help is appreciated. > -- > Regards, > Tim Grant > Application Developer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
