[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#242499: libapache-mod-perl and request-tracker3 randomly sends html to error log instead of browser



tags 242499 + moreinfo
stop

Hi Andre,
	please i need you to do some testing for me. I have never seen
this kind of behaviour and i find it really really strange.

Please create a simple perl page like hello world, disable everything that
is not required to run it (php4, mod_jk and so on..) and than use ab to
poll that script several thousands of times for a few hours. If there is
no segafult or no errors i suspect that one of the other modules or
request tracker3 do something that corrupts things around.

Thanks
Fabio


On Tue, 6 Apr 2004, Andre wrote:

> [Tue Apr  6 17:42:50 2004] [notice] child pid 9885 exit signal
> Segmentation fault (11)
>
> But this only happens after randomly sending request-tracker(perl) pages
> directly to the apache error log instead of the web-browser. This has
> affected my php pages as well although I have not noticed the php html
> in the log files I now occasionally get empty responses from apache.
>
> In an attempt to fix this problem I did the changed following in
> /usr/share/request-tracker3/libexec/webmux.pl
>
> #use Carp;
> use CGI::Carp qw(fatalsToBrowser);
>
> After restarting apache it worked fine for several hours.  Now it won't
> display a page from the request-tracker (perl pages) in the browser
> instead all the pages are going to error log instead.
>
>
> ---------------------- snip from error log ---------------------------
> [Mon Apr  5 06:44:49 2004] [notice] Apache/1.3.29 (Debian GNU/Linux)
> mod_jk/1.2.5 PHP/4.3.4 mod_ssl/2.8.16 OpenSSL/0.9.7c mod_perl/1.29
> configured -- resuming normal operations
> [Mon Apr  5 06:44:49 2004] [notice] suEXEC mechanism enabled (wrapper:
> /usr/lib/apache/suexec)
> [Mon Apr  5 06:44:49 2004] [notice] Accept mutex: sysvsem (Default:
> sysvsem)
> HTTP/1.1 200 OK^M
> Date: Mon, 05 Apr 2004 12:46:05 GMT^M
> Server: Apache/1.3.29 (Debian GNU/Linux) mod_jk/1.2.5 PHP/4.3.4
> mod_ssl/2.8.16 OpenSSL/0.9.7c mod_perl/1.29^M
> Expires: +30m^M
> Connection: close^M
> Content-Type: text/css^M
> ----------------------- end snip ------------------------------------
>
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.23
> Locale: LANG=en_US, LC_CTYPE=en_US
>
> Versions of packages libapache-mod-perl depends on:
> ii  apache-common               1.3.29.0.2-4 Support files for all Apache webse
> ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
> ii  libdevel-symdump-perl       2.03-3       Perl module for inspecting perl's
> ii  libperl5.8                  5.8.3-3      Shared Perl library.
> ii  liburi-perl                 1.30-1       Manipulates and accesses URI strin
> ii  libwww-perl                 5.76-2       WWW client/server library for Perl
> ii  perl [libmime-base64-perl]  5.8.3-3      Larry Wall's Practical Extraction
>
> -- no debconf information
>
>
>

-- 
<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: