I also recieve the same stuck R...
And, it doesn't timeout either. I have written a small perl script to kill the stuck
processes after 1200 seconds of R.
This is a relativly new issue that I have never seen before the last couple of days.
And I am pretty sure we haven't changed any
configuration settings in apache.
For anyone who has this problem.... this may be at least a temporary solution for you
as well
#!/usr/bin/perl
use strict;
open (FILE, "/usr/bin/GET http://www.yourserver.net/server-status |");
my $s;
my $s2;
my $s3;
while ($s = <FILE>) {
if ($s =~ /<td>\?<td nowrap>\?<td nowrap>\.\.reading\.\. <\/tr>/) { #check if
the process is stuck
$s2 =~ /<td>(.*?)<td>(.*?)<td>/;
if ($2 > 1200) { #has it been stuck for 1200+ seconds
$s3 =~ /<tr
bgcolor=\"\#ffffff\"><td><b>(.*?)<\/b><td>(.*?)<td>/; #get the PID so we can kill it
open (KILLFILE, "/bin/kill -15 $2 |"); #kill the process
print "httpd process $2 was stuck reading the request and was
killed.\n";
close(KILLFILE);
}
}
$s3 = $s2;
$s2 = $s;
}
close (FILE);
oh yeah, standard legal crap about me not guarnanteeing that this script wont eat your
computer and stuff :)
-Jason
----- Original Message -----
From: "Emmanuel Anne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 14, 2000 3:32 AM
Subject: Re: Confirmation of bug
> On Fri, Mar 10, 2000, Emmanuel Anne wrote:
>
> > > About one month ago, I posted a message about some connections staying stuck
> >> for ever in the R state (reading). The timeout was not working anymore.
> >> I finally switched to apache-ssl and the problem disappeared !!!
> >
> ><grin> Fine, thanks for letting us know that you're convinced your
> >problem was just a nasty bug in our unclean and broken mod_ssl code and
> >not related to anything else you perhaps messed up locally (for instance
> >a SSLRandomSeed /dev/random which blocks, or the fact that mod_ssl used
> >the stricter and secure connection shutdown which some broken browsers
> >dislike, etc.).... ;)
> > Ralf S. Engelschall
> > [EMAIL PROTECTED]
> > www.engelschall.com
>
> Well actually I have been using modssl for a very long time, feeling that it
> was more powerfull than the equivalent apache-ssl. But if this situation was
> caused by broken browsers, well I can't do anything about it : it is absolutely
> impossible and even unthinkable to refuse access to these browsers. If people
> want to use them I can not force them not to.
> So if the only option to allow them to come in without having a script which
> regularly chechs the status of my http processes is to switch to apache_ssl,
> well...
> Believe me, I checked my confs carefully. But I have no time to look in the
> source of modssl myself.
>
> For now, I am not even sure that apache_ssl is working 100% correctly. Still
> checking !!!
>
> Emmanuel Anne - ABS
> T�l : 01 53 45 90 90
> email : [EMAIL PROTECTED]
> site web : http://www.absysteme.fr
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
