[squid-users] sslReadServer: FD 95: read failure: (104) Connection reset by peer]

Hi Amos,
    That https_port doesn't work.
As for the squid version i am using squid-2.5.STABLE14-1.RHEL4. Thats
seems the only version compatible with Red Hat enterprise 4. I tried the
squid 3.0 tarball it gave me too many errors during make install.
Anyway, i would prefer to pinpoint the error "sslReadServer: FD 95: read
failure: (104) Connection reset by peer". I have read from previous post
someone suggested could be the internet connection or firewall problem,
but i have tested direct connection to internet without proxy, it works
so the internet line is good. As for firewall, i have switched it off
also, the problem still persist, so i can narrow down it is something
within squid.
thanks Amos

yong bong fong wrote:
> Dear friends,
>
> I have these error frequently in my squid log, that everytime i
> encounter this error my squid server starts to serve requests super slow.
> On google search i can find advise that by changing http_port to
> http_port my_lan_ip:3128 that could solve the problem but i have tried
> it it doesn't solve the problem. Anyone has any idea what is the problem?

That would work if its was httpS_port accepting SSL traffic...maybe.

> Below is the error in log:
> 2008/02/02 09:06:58| sslReadServer: FD 95: read failure: (104)
> Connection reset by peer
> 2008/02/02 09:56:55| parseHttpRequest: Requestheader contains NULL
> characters
> 2008/02/02 09:56:55| clientReadRequest: FD 140 Invalid Request
> 2008/02/02 09:56:55| parseHttpRequest: Requestheader contains NULL
> characters
> 2008/02/02 09:56:55| clientReadRequest: FD 140 Invalid Request
> 2008/02/02 10:00:28| parseHttpRequest: Requestheader contains NULL
> characters
> 2008/02/02 10:00:28| clientReadRequest: FD 101 Invalid Request
> 2008/02/02 10:00:28| parseHttpRequest: Requestheader contains NULL
> characters
> 2008/02/02 10:00:28| clientReadRequest: FD 101 Invalid Request
> 2008/02/02 10:05:46| sslReadServer: FD 95: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:22:56| sslReadServer: FD 72: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:23:27| sslReadServer: FD 117: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:23:33| sslReadServer: FD 71: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:26:42| sslReadServer: FD 77: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:31:59| sslReadServer: FD 31: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:37:05| sslReadServer: FD 44: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:38:33| sslReadServer: FD 46: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:57:01| sslReadServer: FD 27: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:57:01| sslReadServer: FD 81: read failure: (104)
> Connection reset by peer
> 2008/02/02 10:57:01| sslReadServer: FD 49: read failure: (104)
> Connection reset by peer
> 2008/02/02 11:03:57| parseHttpRequest: Requestheader contains NULL
> characters
> 2008/02/02 11:03:57| clientReadRequest: FD 69 Invalid Request
> 2008/02/02 11:03:57| parseHttpRequest: Requestheader contains NULL
> characters
> 2008/02/02 11:03:57| clientReadRequest: FD 69 Invalid Request
>
> thanks

You neglect to say which squid version and release you are running. Have
you tried a recent one?

Amos

-- 
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.