Re: Bug#242499: libapache-mod-perl and request-tracker3 randomly sends html to error log instead of browser
Yes but this is not a solution. What scares me that nobody running your
setup is experiencing the same problem.
Fabio
On Thu, 20 May 2004, Andre Borrelly wrote:
> Never mind :'( After an hour of testing it began with the same errors. I
> gave up and installed apache-perl on a different port. Problem solved.
>
> Sorry for all the headaches!
>
> Andre
> > Hello all!
> >
> > I'm pleased to announce that I seem to have found the root of the problem.
> > After removing "Turck MMCache for PHP" from my php.ini I no longer have
> > the problem related to this bug. If it hasn't been closed yet, please do
> > so.
> >
> > Thank you all for all your help and support! I hope this helps others who
> > run into the same problems I did. Who would be responsible in resolving
> > this issue Turck MMCache or mod_perl?
> >
> > Thanks again,
> >
> > Andre
> >> tags 242499 + unreproducible
> >> thanks
> >>
> >> Hi Andre and Andrew,
> >>
> >> # If the perl module is installed, this will be enabled.
> >> <IfModule mod_perl.c>
> >> <IfModule mod_alias.c>
> >> Alias /perl/ /var/www/perl/
> >> </IfModule>
> >> PerlModule Apache::Registry
> >> <Location /perl>
> >> SetHandler perl-script
> >> PerlHandler Apache::Registry
> >> Options +ExecCGI +Indexes
> >> PerlSendHeader on
> >> allow from all
> >> </Location>
> >> </IfModule>
> >>
> >> I did test your "hello world" with the default apache configs plus the
> >> above configuration for mod_perl and i have no problems at all. Tested
> >> using ab -n 100000 -c 100:
> >>
> >> Complete requests: 100000
> >> Failed requests: 0
> >> Broken pipe errors: 0
> >>
> >> and there are no strange messages in the error log.
> >>
> >> Either your config is broken or request-tracker3 has a bug.
> >>
> >> I did take a look to your files but there are way too complicate to
> >> reproduce in my environment and i couldn't spot possible errors.
> >>
> >> Andrew would you be so kind to take a look at this bug report? I didn't
> >> reassign it before coordinating with you.
> >>
> >> Thanks
> >> Fabio
> >>
> >
> >
>
>
>
>
--
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.
Reply to: