Re: [OOPS] TCP_ERROR (?)

[Philipp Buehler]

On 15/09/2000, Igor Khasilev <[EMAIL PROTECTED]> wrote To [EMAIL PROTECTED]:
> there is no furher explanation re these TCP_ERROR in access.log. You can
> check oops.log - depending the verbosity level you use, you can find some
> explanations. You even can run oop -xa to have maximum verbosity.
Ah ok, I tried to look it up backwards, but I have found out, that
there is every minute Statistics "crap" within oops.log :/ So the
file is big and I cant reference the coincidence, cause access.log uses
some weird timestamp, and oops.log normal time.

> There are several reasons for this erros. Most probable:
> 
> some problem arise during data transfer from server to proxy (anything from
> connection refused to timeout to some header-realated problems).
Hm, this could be

> some problem arise with data transfer to client (client aborted data
> transfer by clicking on some reference on the page - this is most probable
> reason)
Not in this case, there is just no reference :>

> There are some other, it is very likely that you will find answer if you
> will look at oops.log or show me suspicious places in log.
try to reproduce it next week, cant access the clients from here :P

ciao
-- 
Philipp Buehler, aka fIpS | sysfive.com GmbH | BOfH | NUCH | <double-p> 
%SYSTEM-F-TOOEARLY, please contact your sysadmin at a sensible time.
Artificial Intelligence stands no chance against Natural Stupidity.
           [X] <-- nail here for new monitor
=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://www.paco.net/oops/