Dave wrote:
Hello,
This is a strange one. I've got a FreeBSD 6.2 router with squid on it
for transparent proxy. It has been working fine, until about 3 days ago
when i noticed one of my internal machines wasn't completing an http
transaction, in this case downloading of it's ports index. The
connection would start out extremely slowly and eventually timeout then
giving an error about a truncated file. I checked my firewall, hard
disks, debug logs, messages everything, couldn't find any error msgs or
anything obviously wrong. This morning an internal machine, this one a
centos box, began failing with it's yum updates, giving timeout errors
on retrieving rpm files from http sites. Again, i ran the log checks,
didn't see anything. So, i next checked the firewall, nothing in
debug.log or messages, but in the /usr/local/squid/logs directory i
found two things. The first was that the failed transactions were all
returning http response code 206, timeout? The second was that i had a
43 mb core file. I shut down squid, turned off the transparent redirect
rule in my firewall and everything started working normally. If this
core file is useful in debugging i'd like to know what to do or where to
send it, i can post it on a web page if interested. I'd appreciate any
suggestions.
The squid version used is 2.6.13, memory and cpu usage during the
times in question are not even moving, this system is not in any way
heavily loaded.
Hi Dave,
Are you sure that you did not modify anything substantial in the past 3
days? Firewall rules, sysctl tunables in your FreeBSD box?
The core file suggests that your Squid might have crashed. Are you sure
that there is nothing in your cache.log?
Which firewall do you use to do transproxy? Can you show us your
relevant firewall rules?
Also posting your squid.conf might help. How many users are accessing
your cache normally? If you manually use your proxy server in your web
browser, does it help speed up the web requests?
Thanking you...
Any suggestions appreciated.
Thanks.
Dave.
