Re: give 2.0 a shot

[Brian Behlendorf <br...@collab.net>]

OK, we're running 2.0 now on apache.org.  I'm seeing a ton of the
following in the error log:

[Mon Feb 05 15:24:09 2001] [warn] (54)Connection reset by peer: setsockopt: (TCP_NODELAY)
[Mon Feb 05 15:24:09 2001] [warn] (54)Connection reset by peer: setsockopt: (TCP_NODELAY)
[Mon Feb 05 15:24:09 2001] [warn] (54)Connection reset by peer: setsockopt: (TCP_NODELAY)
[Mon Feb 05 15:24:09 2001] [warn] (54)Connection reset by peer: setsockopt: (TCP_NODELAY)
[Mon Feb 05 15:24:10 2001] [warn] (54)Connection reset by peer: setsockopt: (TCP_NODELAY)

Every time I used to see that it used to mean a core dump, but so far no
core dumps.  No, the problem now is that after awhile the server falls
behind in processing requests - exactly as if the maxclients setting were
way too low and requests were queueing up, but maxclients is set to 450
and when this happens under 200 httpd children are running.

I suspect the two observations are related, but I don't know; I do know
that it's unacceptably slow right now, so I've put 1.3 back up.

The new mod_status stuff is a good start =)

	Brian

On Mon, 5 Feb 2001, Greg Ames wrote:
> I have a build ready for you to try.  Jeff did some replay testing on
> :8092 and couldn't break it.  He did notice an anomaly where 2 sockets
> hung, but it could be something in the test driver.
>
> I'm hoping the latest seg fault fix also took care of the weird heap
> corruption problem we saw last time in a few of the core dumps.
>
> You can raise MaxClients back up to 500.  8092 is running that way now.
>
> Cheers,
> Greg