On 05/04/2012 14:51, Colin Coe wrote:
<SNIP>

OK, I did
export ftp_proxy=http://benpxy1p:3128
wget ftp://ftp2.bom.gov.au/anon/gen/fwo
--2012-04-05 19:43:38--  ftp://ftp2.bom.gov.au/anon/gen/fwo
Resolving benpxy1p... 172.22.106.10
Connecting to benpxy1p|172.22.106.10|:3128... connected.
Proxy request sent, awaiting response... ^C

An entry appeared in access.log only after I hit ^C.

Changing ftp_proxy to ftp://benpxy1p:3128 did not change anything.

CC

well if a access_log entry appears it means that the client is contacting the squid server.
did you notice that the size of this list\dir is about 1.8 MB?
take something simple such as:
ftp://ftp.freebsd.org/pub
it should be about 2.9Kb.
then if it didnt go within 10 secs try using without upper stream proxys.
maybe something is setup wrong on the cache_peer.
there are options to debug with a lot of output from squid that can simplify the problem.
but i would go to minimum settings and up.
use only one proxy and without a name.
just use the ip for the cache_peer acls.
you can use the debug sections:
http://wiki.squid-cache.org/KnowledgeBase/DebugSections
to make more use of it.
use like this:
debug_options ALL,1 section,verbosity_level
debug_options ALL,1 9,6

there are couple of sections that will provide you with more network layer info that will help you find the source of the problem.

to see the log tail the cahce.log file.

well i gave you kind of the worst case scenario i could think of.
if you need more help i'm here.

Regards,
Eliezer

--
Eliezer Croitoru
https://www1.ngtech.co.il
IT consulting for Nonprofit organizations
eliezer <at> ngtech.co.il

Reply via email to