Re: Squid seems to "HANG UP"! (NEW FINDINGS)

Hi to all!

Thanks Michael about 2.2.12 info!

I have some new finding regarding my current problem which many have already
contributed to .. thus new questions. Before I move the kernel to 2.2.12 or
before changing some TCP items .... I would like to make these final
clarifications:

(for those who did not receive my previous postings)
distribution : slackware 4.0
kernel version : 2.2.6
squid version : 2.2.STABLE4
eth0 : 202.8.254.3
eth1 : 172.16.12.254
squid (proxy) port: 8085
clients : 100 pcs (Intel Pentium using IE 4.0) all connected to eth1
note : eth0 is connected to our router while eth1 is connected to a
switch where all the pcs are also connected (through a series of hubs). this
means that the two networks are physically separated by the linux server.

I made some discoveries a while ago. When I experienced the "hang up"
around 30 minutes ago ... I tried to modify the proxy settings of one of
the clients from 172.16.12.254:8085 to 202.8.254.3:8085 without touching the
physical network. This client was able to connect to the proxy. Also I
have observed that during these moments of "hang up" .. I can ping eth1
(172.16.12.254) but could not telnet to it ... but i can telnet eth0 from
any client. i have to wait sometime before any client can access the proxy
again.

Here is my question ... if I am running out of file descriptors .... why was
I be able to access the same proxy using another interface? .. if my problem
is TCP ... doing a netstat -a | grep 8085 lists only a few tcp items:

tcp 0 12179 172.16.2.251:8085 172.16.2.127:1036
FIN_WAIT1
tcp 0 4366 172.16.2.251:8085 172.16.2.128:1117
FIN_WAIT1
tcp 0 1 172.16.2.251:8085 172.16.2.128:1116
FIN_WAIT1
tcp 0 3393 172.16.2.251:8085 172.16.2.128:1115
FIN_WAIT1
tcp 0 0 172.16.2.251:8085 172.16.2.128:1114
TIME_WAIT
tcp 0 0 172.16.2.251:8085 172.16.2.128:1113
TIME_WAIT
tcp 0 0 172.16.2.251:8085 172.16.2.128:1112
TIME_WAIT
tcp 0 1 172.16.2.251:8085 172.16.2.128:1116
FIN_WAIT1
tcp 0 3393 172.16.2.251:8085 172.16.2.128:1115
FIN_WAIT1
tcp 0 0 172.16.2.251:8085 172.16.2.128:1114
TIME_WAIT
tcp 0 0 172.16.2.251:8085 172.16.2.128:1113
TIME_WAIT
tcp 0 0 172.16.2.251:8085 172.16.2.128:1112
TIME_WAIT
tcp 0 0 dbccproxy.donbosco:8085 172.16.2.253:1689
TIME_WAIT
tcp 0 0 172.16.2.251:8085 172.16.2.128:1111
TIME_WAIT
tcp 0 278 172.16.2.251:8085 172.16.2.119:1050
FIN_WAIT1
tcp 0 8747 172.16.2.251:8085 172.16.2.56:1037
FIN_WAIT1
tcp 0 1 172.16.2.251:8085 172.16.2.118:1045
FIN_WAIT1
tcp 0 222 172.16.2.251:8085 172.16.2.128:1107
FIN_WAIT1
tcp 0 10184 172.16.2.251:8085 172.16.2.63:1300
FIN_WAIT1
tcp 0 1 172.16.2.251:8085 172.16.2.127:1031
FIN_WAIT1
tcp 0 1 172.16.2.251:8085 172.16.2.127:1030
FIN_WAIT1
tcp 0 18026 172.16.2.251:8085 172.16.2.112:1049
ESTABLISHED
tcp 0 698 172.16.2.251:8085 172.16.2.118:1038
FIN_WAIT1
tcp 0 998 172.16.2.251:8085 172.16.2.118:1030
FIN_WAIT1
tcp 0 0 *:8085 *:* LISTEN
tcp 0 698 172.16.2.251:8085 172.16.2.118:1038
FIN_WAIT1
tcp 0 998 172.16.2.251:8085 172.16.2.118:1030
FIN_WAIT1
tcp 0 0 *:8085 *:* LISTEN

Hope someone could give me some final words before i change my kernel.

Thanks again guys for any help you can extend to me :):):) !

Sarah @:)

Systems Administrator
DBIT Systems, Inc., Philippines
sarah_rodriguez@consultant.com
Received on Thu Sep 16 1999 - 04:16:52 MDT