Assuming you haven't found a resolution to the issue yet...
Have you tried running running Apache with a single child (MaxClients
1) to try to help isolate the issue? I realize this is only a viable
setup on a test machine.
The code hack in me would probably try putting something along the lines
>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'
Thanks to everyone for the replies. I'll get to them all, but I can answer
Sherman Culler's questions now.
>Just curious - why not upgrade Apache/Embperl/mod_perl to the latest
>versions - Apache 2.x, Embperl 2.x and mod_perl 2?
We tried this a while ago. Embperl 2 is stricter with its HTML val
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
>
> It is defined as a constant:
>
> *bgcolor = \"beige";
>
> This is the way to do constants which I read about in the Programming
> Perl book...
Never saw this before, but it really defines a constant. The problem is from
within Perl I don't see any chance to catch the difference between such a
> > The last message is weird. The variable concerned is a constant, which
> > should never be changed. There are many other constants which I defined,
> > so I am not sure why this one should cause a problem. I have checked my
> > code and it is used 3 times, in different files, in very simple
>
>
> [2772]CUP: Error while cleanup $HTML::Embperl::DOC::_1::page_bgcolor:
> Modification of a read-only value attempted at
> /usr/lib/perl5/site_perl/5.6.0/i386-linux/HTML/Embperl.pm line 1393.
>
> The "processblock" stuff looks a lot like the logging which you added to
> epmain.c when we were tr
> > Yes, in the CVS version there sometimes some extra logging. To turn all
> > logging off, just set
> >
> > PerlSetEnv EMBPERL_LOGFILE /dev/null
> >
> > I normaly remove this extra logging before I release a new version.
>
> I tried putting this line in my production server httpd.conf, but I am
> > I am using the CVS latest version currently, because it seems to have
> > the latest fix which you made to EmbperlObject as a result of all those
> > problems I was having. It's working great, but I notice that I am still
> > getting a lot of debug logging into /tmp/embperl.log, even with
> >
Neil,
>
> I am using the CVS latest version currently, because it seems to have
> the latest fix which you made to EmbperlObject as a result of all those
> problems I was having. It's working great, but I notice that I am still
> getting a lot of debug logging into /tmp/embperl.log, even with
> E
10 matches
Mail list logo
