I put a new apache 2.0 build up on daedalus for a while this afternoon.
This was from a cvs up done early this afternoon. It was serving
requests like gangbusters for about a minute and a half. But I had to
take it back down because it was also spewing the following stuff to the
error logs at a pretty high rate:
[Fri Jun 15 14:20:21 2001] [error] (32)Broken pipe: core_output_filter:
writing data to the network
[Fri Jun 15 14:20:24 2001] [error] (57)Socket is not connected:
core_output_filter: writing data to the network
[Fri Jun 15 14:20:24 2001] [error] (32)Broken pipe: core_output_filter:
writing data to the network
[Fri Jun 15 14:20:25 2001] [error] (57)Socket is not connected:
core_output_filter: writing data to the network
[Fri Jun 15 14:20:25 2001] [error] (32)Broken pipe: core_output_filter:
writing data to the network
[Fri Jun 15 14:20:27 2001] [error] (57)Socket is not connected:
core_output_filter: writing data to the network
[Fri Jun 15 14:20:27 2001] [error] (32)Broken pipe: core_output_filter:
writing data to the network
I *think* this is normal stuff for a production server, and that maybe
the log level just needs tweaking. I almost convinced Jeff of this too,
but it sounds like he wants to make sure there's not some more serious
breakage going on.
Anyway, the 2.0 code base is in pretty good shape at the moment IMO.
I'd like to see it tagged once we do something about these log errors.
I'm off to the high seas for a couple of weeks. See you when I get
back.
Greg
