Content-Type: text/plain
squid-users-digest Digest Volume 98 : Issue 314
Today's Topics:
Re: Microsoft (need I say more). [ Henrik Nordstrom <hno@hem.passagen. ]
Re: squid 1.15b OS/2 - dnsserver won [ Henrik Nordstrom <hno@hem.passagen. ]
stop squid logs? [ Les Higger <lhigger@lausd.k12.ca.us ]
Re: squid 1.15b OS/2 - dnsserver won [ "Doug Nazar" <nazard@man-assoc.on.c ]
Re: squid 1.15b OS/2 - dnsserver won [ Duane Wessels <wessels@ircache.net> ]
redireccion with transproxy [ "Daniel Valfre" <dvalfre@ubp.edu.ar ]
Re: Digital Unix - Squid dies [ Oreste Dimaggio <oreste@mediatec.it ]
question [ fakhri <fakhri@mimos.my> ]
Virtual hosts problems [ Toby Chamberlain <toby@peoplesearch ]
Re: Virtual hosts problems [ Q <q@fan.net.au> ]
Re: digest only peering? [ Bruce Campbell <bc@thehub.com.au> ]
Re: illigal character in hostname [ Marc van Selm <marc.van.selm@nc3a.n ]
Re: digest only peering? [ Alex Rousskov <rousskov@nlanr.net> ]
Failed to select source [ Robin Breyl <robin.breyl@produktion ]
Re: problem reaching home.netscape.c [ "Paykar Chamani" <paykar@pacbell.ne ]
Re: FAQ request [ Peter Polkinghorne <Peter.Polkingho ]
Date: Wed, 25 Nov 1998 01:31:02 +0100
From: Henrik Nordstrom <hno@hem.passagen.se>
To: Mark Rogers <markrogers@ozemail.com.au>
Cc: squid-users@ircache.net
Subject: Re: Microsoft (need I say more).
Message-ID: <365B4FC6.4E8AA293@hem.passagen.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mark Rogers wrote:
> My problem is down to the age old "Connection Reset" problem. Can you tell
> me, where is squid up to with this problem.
It depends on which "Connection Reset" problem you are referring to.
Reported by the browser, or seen as as a Squid error message?
Squid has historically been as sensitive as most browsers is on Unix.
I.e.
if it sees a "Connection Reset" message when trying to contact the
origin
server then request failed. Windows browsers on the other hand retries
requests when seeing a "Connection Reset". I think this is addressed by
the current code.
> Last I heard was some people were trying the retry patch, how did this work
> out?
The retry patch is partially incorporated in Squid 2. Work is being
made on a more complete retry model including false hit recovery.
> >Hard to tell which screws up worst. IE or Netscape.. Both has major
> >flaws in some (or most) versions.
>
> Any big ones (cache specific) you would like to point out??
Not all are cache specific, but people notice them when using a Squid
as Squid may do things differently than the origin server, or the
browser behaves slightly different when using a proxy..
Netscape:
Persistent proxy connections and https requests.
FTP URL style.
Spaces in URLs.
Range requests in some versions / plugins.
IE:
Persistent proxy connections when not allowed by the proxy...
Possibly other connection / HTTP issues.
--- Henrik Nordstrom Spare time Squid hacker
Date: Wed, 25 Nov 1998 01:40:53 +0100
From: Henrik Nordstrom <hno@hem.passagen.se>
To: Doug Nazar <nazard@man-assoc.on.ca>
Cc: Squid Users <squid-users@ircache.net>
Subject: Re: squid 1.15b OS/2 - dnsserver won't start
Message-ID: <365B5215.1FFCBFA7@hem.passagen.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Doug Nazar wrote:
> One of the other main issues is that's you can't rename (or unlink)
> open files. Unfortuanatly I'm having a little trouble following the
> code paths for handling the file handle closing.
This is not unique to the emx library. The same applies to CygWin on
Windows. Search for _SQUID_MSWIN_ in store_dir.c (no idea why Duane
insists on renaming open files when writing the clean log..)
--- Henrik Nordstrom Spare time Squid hacker
Date: Tue, 24 Nov 1998 16:47:44 -0800 (PST)
From: Les Higger <lhigger@lausd.k12.ca.us>
To: squid-users@ircache.net
Subject: stop squid logs?
Message-ID: <Pine.A32.3.93.981124164528.87348B-100000@lausd.k12.ca.us>
Content-Type: TEXT/PLAIN; charset=US-ASCII
since i am having a bit of trouble getting logs to roll with 0.35. is
there a way to stop the loging?
I dont really need em.
*++++++++++++++++++++++++++++++++++++++*
* Les Higger Student Information Systems
* Local Area Network Coord.
* lhigger@lausd.k12.ca.us
* Francisco Bravo Medical Magnet High School
* Los Angeles Unified School District
---> Old men can give flawless advice, for they nolonger can set bad
examples <---
Date: Tue, 24 Nov 1998 19:57:37 -0600
From: "Doug Nazar" <nazard@man-assoc.on.ca>
To: "Henrik Nordstrom" <hno@hem.passagen.se>
Cc: "Squid Users" <squid-users@ircache.net>
Subject: Re: squid 1.15b OS/2 - dnsserver won't start
Message-Id: <199811250057.TAA11649@smartmail.idirect.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
On Wed, 25 Nov 1998 01:40:53 +0100, Henrik Nordstrom wrote:
>Doug Nazar wrote:
>
>> One of the other main issues is that's you can't rename (or unlink)
>> open files. Unfortuanatly I'm having a little trouble following the
>> code paths for handling the file handle closing.
>
>This is not unique to the emx library. The same applies to CygWin on
>Windows. Search for _SQUID_MSWIN_ in store_dir.c (no idea why Duane
>insists on renaming open files when writing the clean log..)
I got that one. I changed the code to as follows
#if defined(_SQUID_MSWIN_) || defined(_SQUID_OS2_)
/*
* You can't rename open files on Microsoft "operating systems"
* so we close before renaming.
*/
storeDirCloseSwapLogs();
#endif
/* rename */
for (dirn = 0; dirn < N; dirn++) {
if (fd[dirn] < 0)
continue;
#ifdef _SQUID_OS2_
file_close(fd[dirn]);
fd[dirn] = -1;
if (unlink(cur[dirn]) < 0) {
debug(50, 0) ("storeDirWriteCleanLogs: unlinkd failed: %s,
%s\n",
xstrerror(), cur[dirn]);
}
#endif
if (rename(new[dirn], cur[dirn]) < 0) {
debug(50, 0) ("storeDirWriteCleanLogs: rename failed: %s,
%s -> %s\n",
xstrerror(), new[dirn], cur[dirn]);
}
}
#if !defined(_SQUID_MSWIN_) && !defined(_SQUID_OS2_)
storeDirCloseSwapLogs();
#endif
The current problem shows up in storeDirCloseTmpSwapLog(). The
file_close() doesn't always really close the file, and hence the unlink
fails (I have to unlink before the rename).
Doug Nazar
Phone: (416) 708-1578
Fax: (416) 708-8081
Date: Tue, 24 Nov 1998 18:04:02 -0700
From: Duane Wessels <wessels@ircache.net>
To: "Doug Nazar" <nazard@man-assoc.on.ca>
cc: "squid-users@ircache.net" <squid-users@ircache.net>
Subject: Re: squid 1.15b OS/2 - dnsserver won't start
Message-Id: <199811250104.SAA04180@surf.ircache.net>
"Doug Nazar" writes:
>On Tue, 17 Nov 1998 17:50:09 -0600 (CST), Timur Tabi wrote:
>
>>Interest?!?!!?!? I'll name my first born after you, even if it's
>>a girl! (she'll understand)
>
>Sorry, for taking so long to get back to you but I'm just now starting
>to recover from a cold or something. I've also got most of my stuff
>packed up to move this Sunday.
>
>>>I'm not sure if I want to merge the changes back into the mainstream
>>>since it's mainly working around bugs in emx.
>>
>>I think it would be nice if you did - that would improve the change of
>>version parity between Linux and OS/2.
>
>After spending some time with the squid & emx code, I'm starting to
>wonder if my time won't be better spent improving the emx library. Most
>notably, sockets aren't inherited across exec*() calls.
>
>One of the other main issues is that's you can't rename (or unlink)
>open files. Unfortuanatly I'm having a little trouble following the
>code paths for handling the file handle closing.
>
>If I call file_close() and flags.write_daemon is set, then the close
>will be delayed but I'm not sure what to call to force the close
>properly. This is causing a race condition on startup & shutdown for
>the cache logs (swap.state, swap.state.new, swap.state.clean,
>swap.state.last-clean). Anybody?
If flags.write_daemon is set then there is more data to write
to the file. You probably don't want to close it before
all has been written.
If you must, I guess you could do something ugly like
call fd_table[fd].write_handler(fd, fd_table[fd].write_data);
I'm not sure what will happen next though.
Duane W.
Date: Tue, 24 Nov 1998 22:17:05 -0300
From: "Daniel Valfre" <dvalfre@ubp.edu.ar>
To: squid <squid-users@ircache.net>
Subject: redireccion with transproxy
Message-ID: <365B5A8C.AB1DAFA8@ubp.edu.ar>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
hello
I recently upgraded from 1.1.21 to 2.0.PATCH2 to 2.1.PATCH1 on linux
2.0.36 with libc5
The problem I'm facing is that I'm getting a lot of BAD REQUEST errors
that weren't there before.
I'm running transproxy 0.4 in conjunction with the transproxy feature in
the kernel to redirect to squid.
I didn't change anything in the configuration except the translation to
the new format.
Any ideas/thoughts?
Thanks in advance
greetings
daniel
Date: Wed, 25 Nov 1998 02:16:51 +0100
From: Oreste Dimaggio <oreste@mediatec.it>
To: Henrik Nordstrom <hno@hem.passagen.se>
Cc: squid-users@ircache.net
Subject: Re: Digital Unix - Squid dies
Message-Id: <199811250208.DAA01468@dns.mediatec.it>
Content-Type: text/plain; charset="us-ascii"
At 01.12 25/11/98 +0100, Henrik Nordstrom wrote:
>Parent Squid
> |
> \-- Main Squid
> |
> \-- dnsservers
> |
> \-- redirectors
> ..
>
>This is unless you start Squid with the -N option. If you use the -N
>option then the parent Squid step is skipped (the first process is the
>main Squid process).
MMhh... the problem is that I didn't start squid with -N option
So there is something wrong on my system... can you help me to discover
the problem ?
Date: Wed, 25 Nov 1998 09:26:37 +0800
From: fakhri <fakhri@mimos.my>
To: squid <squid-users@ircache.net>
Subject: question
Message-ID: <365B5CCD.5B785950@mimos.my>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
can somebody please tell me why objects do not get cached? I read about
the responses with cache control which will not be cachable. but can
somebody tell me more in details.
thank you.
fakhri
Date: Wed, 25 Nov 1998 15:46:31 +1000
From: Toby Chamberlain <toby@peoplesearch.com.au>
To: squid-users@ircache.net
Subject: Virtual hosts problems
Message-ID: <365B99B7.175C768E@peoplesearch.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi there,
I'm trying to set up Squid as an accelerating proxy for a web server
behind a firewall using virtual hosts, but I keep getting "WARNING:
Forwarding loop... for 'www.company.com.au' -> proxy.company.com.au
I have read the FAQ and the mailing list archives and did everything I
thought I was supposed to.... (but obviously missed something)
http_port 80
httpd_accel_port 80
httpd_accel_host realserver.company.com.au
httpd_accel_uses_host_header on
'realserver.company.com.au' has a valid entry in /etc/hosts and can be
pinged etc. The virtual URL's (www.company1.com.au, www.company2.com.au
etc) have been CNAME'd as the computer with squid running (which is also
aliased as mail, proxy etc.). The interesting thing is that when I turn
_uses_host_header off it gets through fine, with no forwarding loops, I
just get the same homepage regardless of which of the virtual URL's I
use (as you would expect)...
I'm running Squid/2.0.PATCH2 on Debian Linux 2.0.34, anybody know what's
going wrong??
Thanks
Toby
Date: Wed, 25 Nov 1998 17:19:26 +1000 (EST)
From: Q <q@fan.net.au>
To: Toby Chamberlain <toby@peoplesearch.com.au>
cc: squid-users@ircache.net
Subject: Re: Virtual hosts problems
Message-ID: <Pine.BSF.4.02.9811251639560.4982-100000@gromit.fan.net.au>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 25 Nov 1998, Toby Chamberlain wrote:
> Hi there,
>
> I'm trying to set up Squid as an accelerating proxy for a web server
> behind a firewall using virtual hosts, but I keep getting "WARNING:
> Forwarding loop... for 'www.company.com.au' -> proxy.company.com.au
>
> I have read the FAQ and the mailing list archives and did everything I
> thought I was supposed to.... (but obviously missed something)
>
> http_port 80
> httpd_accel_port 80
> httpd_accel_host realserver.company.com.au
> httpd_accel_uses_host_header on
>
> 'realserver.company.com.au' has a valid entry in /etc/hosts and can be
> pinged etc. The virtual URL's (www.company1.com.au, www.company2.com.au
> etc) have been CNAME'd as the computer with squid running (which is also
> aliased as mail, proxy etc.). The interesting thing is that when I turn
> _uses_host_header off it gets through fine, with no forwarding loops, I
> just get the same homepage regardless of which of the virtual URL's I
> use (as you would expect)...
The problem you are having here is that in your setup squid will use a
host_header name over the httpd_accel_host if a host header is
specified (this is what httpd_accel_uses_host_header means, hence the
warning in the sample config).
Therefore, a request to http://www1.company.com.au/ with a host header of
www1.company.com.au (as most browsers do) will cause squid to fetch
http://www1.company.com.au/ instead of http://realserver.company.com.au/
which is itself (thus causing the loop). You should only need to use
httpd_accel_uses_host_header when doing transparent proxying, or when
accelerating multiple virtual servers that use different IP addresses
(this usually employs an internal/external DNS setup).
All you should need to do is disable httpd_accel_uses_host_header. Squid
should forward the specified Host: header with the accelerated request to
realserver.company.com.au.
Note that if realserver.company.com.au doesn't resolve to the IP address
of your named virtual host address, then you will always be returned the
same page.
Try telnetting to realserver.company.com.au:80 and typing this:
GET / HTTP/1.1
Host: www1.company.com.au
Do you get what you expected?
Seeya...Q
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_____ / Quinton Dolan - q@fan.net.au
__ __/ / / __/ / / Systems Administrator
/ __ / _/ / / Fast Access Network
__/ __/ __/ ____/ / - / Gold Coast, QLD, Australia
_______ / Ph: +61 7 5574 1050
\_\ SAGE-AU Member
Date: Wed, 25 Nov 1998 18:10:09 +1000 (EST)
From: Bruce Campbell <bc@thehub.com.au>
To: Allen Smith <easmith@beatrice.rutgers.edu>
cc: Alex Rousskov <rousskov@nlanr.net>, squid-users@ircache.net
Subject: Re: digest only peering?
Message-ID: <Pine.BSF.3.96.981125171154.5459M-100000@zerlargal.humbug.org.au>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 24 Nov 1998, Allen Smith wrote:
> On Nov 23, 11:30pm, Alex Rousskov (possibly) wrote:
> > On Fri, 20 Nov 1998, Allen Smith wrote:
> > Perhaps you want to do something like this:
(line 332 of forward.c squid 2.0p2)
answer = aclCheckFast(Config.accessList.miss, &ch);
> > +#if USE_CACHE_DIGESTS
> > + if (answer == 0 && store_digest) {
> > + answer = cacheDigestTest(store_digest, e->key);
> > + }
> > +#endif
>
> Oh. Oops... this sort of thing is why I requested for someone in the
> situation of needing this to check this out.
I'll be applying it to my main proxy tomorrow, however I won't see
anything until other ISPs which peer with us turn cache-digests back on.
> > Even that is not bullet-proof, but should work in most [reasonable] cases.
>
> Hmm... if the cache digest changed between the peer's loading of it
> and the reception by one's cache of the request, yes, unless I have
> yet again misunderstood the inner workings of squid. What other cases can
> people think of in which this wouldn't work?
It seems to cover the case of fulfilling a request which would otherwise
be denied if we've got a false hit in the (current) cache-digest.
It also covers the case of if a peer retrieves a cache-digest, we discard
an object, the peer then requests the object.
That still leaves a window of up to an hour between when we discard an
object/generate cache-digest without said object, and a when peer
retrieves the latest cache-digest without the object in it, possibly
longer if the peer is disconnected, during which time the peer's client
will get our 'Bugger off, not letting you have this object'.
Hmmm... its starting to get too much effort to keep the previous (X) cache
digests around to deal with that aspect.
Skimming store_digest.c, around line 190 says "this object won't be added
to the digest as we're going to toss it out before the next rebuild", so
that seems to cover most cases, although I'd be inclined to trust in the
Note there and increase that amount of time, ie:
--- squid-2.0.PATCH2/src/store_digest.c.19980920 Wed Nov 25
17:44:40 1998
+++ squid-2.0.PATCH2/src/store_digest.c Wed Nov 25 17:54:41 1998
@@ -74,6 +74,8 @@
static const int StoreDigestBitsPerEntry = 5;
/* how often we want to rebuild the digest, in seconds */
static const time_t StoreDigestRebuildPeriod = 60 * 60;
+/* How much grace time do we want to give objects about to expire? must be larger than StoreDigestRebuild/Rewrite */
+static const time_t StoreDigestGracePeriod = 180 * 60;
/* how often we want to rewrite the digest after rebuild, in seconds */
static const int StoreDigestRewritePeriod = 60 * 60;
/* how many bytes to swap out at a time */
@@ -194,7 +196,7 @@
(int) (refresh - squid_curtime));
/* if expires too soon, ignore */
/* Note: We should use the time of the next rebuild, not cur_time @?@ */
- if (refresh <= squid_curtime + StoreDigestRebuildPeriod) {
+ if (refresh <= squid_curtime + StoreDigestGracePeriod) {
debug(71, 6) ("storeDigestAdd: entry expires too early, ignoring\n");
} else {
good_entry = 1;
--==--
Bruce.
Sysadmin, TheHub.
Date: Wed, 25 Nov 1998 09:24:51 +0100
From: Marc van Selm <marc.van.selm@nc3a.nato.int>
To: squid-users@ircache.net
Subject: Re: illigal character in hostname
Message-Id: <199811250820.JAA00220@nms.nc3a.nato.int>
Content-Type: text/plain; charset="us-ascii"
At 01:17 PM 11/24/98 +0100, Robin Breyl wrote:
>Hello,
>
>Squid compiled fine, but... I get two major problems.
>First it is complaining about the hostname of the machine
>it runs on:
>
>> urlParse: Illegal character in hostname 'mymachine1_0'
>
>Changing the hostname is not an option in our environment here,
>so I wonder if this check for the own hostname can be disabled
>either in the config file, or in the source code.
RFC952:
1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
sign (-), and period (.). Note that periods are only allowed when
they serve to delimit components of "domain style names". (See
RFC-921, "Domain Name System Implementation Schedule", for
background). No blank or space characters are permitted as part of a
name. No distinction is made between upper and lower case. The first
character must be an alpha character. The last character must not be
a minus sign or period. A host which serves as a GATEWAY should have
"-GATEWAY" or "-GW" as part of its name. Hosts which do not serve as
Internet gateways should not use "-GATEWAY" and "-GW" as part of
their names. A host which is a TAC should have "-TAC" as the last
part of its host name, if it is a DoD host. Single character names
or nicknames are not allowed.
>Any help welcome.
Sorry, but you will have to change the hostname if you think standards are
useful. Squid can be configured to cheat but also DNS-servers might reject
this. Bind8.x rejects this (normally) if you have this in your configuration.
Bind will not accept this zone. Also a secondary bind8.x will not accept this
behaviour from the "master" so in fact you are not doing yourself a vafour if
you don't change the name.
(I admit this is not easy to find in the stack of RFC's but now you know...)
Marc
>
> Robin Breyl
>--
> _________________________________________________________________
> / \
> | Robin Breyl Geno RZ |
> | ------------- |
> | Friedrich-Ebert-Anlage 2-14 |
> | 60325 Frankfurt am Main |
> | |
> | E-Mail (Office): robin.breyl@gis-online.de |
> | E-Mail (Home): robin.breyl@frankfurt.netsurf.de |
> | |
> | Tel.: +49 69 / 75690-369 Fax.: +49 69 / 75690-925 |
> \_________________________________________________________________/
>
Marc van Selm
NATO C3 Agency
Communication Systems Division, A-Branch
Tel: +31 70 3142454
---------------------------------------------------------------------
Private: selm@cistron.nl, selm@het.net, http://www.cistron.nl/~selm
------------------------------
Date: Wed, 25 Nov 1998 01:36:31 -0700 (MST)
From: Alex Rousskov <rousskov@nlanr.net>
To: Bruce Campbell <bc@thehub.com.au>
cc: squid-users@ircache.net
Subject: Re: digest only peering?
Message-ID: <Pine.SGI.3.96.981125012228.862B-100000@Meta-Bug>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 25 Nov 1998, Bruce Campbell wrote:
> It seems to cover the case of fulfilling a request which would otherwise
> be denied if we've got a false hit in the (current) cache-digest.
>
> It also covers the case of if a peer retrieves a cache-digest, we discard
> an object, the peer then requests the object.
Yes. Both cases are false hits, just two different reasons for "false":
digest collisions and refresh algorithm.
> That still leaves a window of up to an hour between when we discard an
> object/generate cache-digest without said object, and a when peer
> retrieves the latest cache-digest without the object in it,
(a) The window between digest rebuilt and other caches asking for a new
digest should be small in most cases (several minutes, not an hour)
(b) New digest in most cases is more than 90% the same as the old one so the
rebuild itself will not cause a lot of false hits.
> possibly
> longer if the peer is disconnected, during which time the peer's client
> will get our 'Bugger off, not letting you have this object'.
If a peer is disconnected, Squid will detect that and will not use the digest
from that peer until the peer is back. Meantime, Squid will try to re-fresh
the peer digest and is likely to fail (since the peer is disconnected) and
disable the digest.
> Hmmm... its starting to get too much effort to keep the previous (X) cache
> digests around to deal with that aspect.
I do not think there is any good reason to start keeping old digests (except
during the rebuild process).
> Skimming store_digest.c, around line 190 says "this object won't be added
> to the digest as we're going to toss it out before the next rebuild", so
> that seems to cover most cases, although I'd be inclined to trust in the
> Note there and increase that amount of time, ie:
You sure can do that. Just note that it will cause more false hits (handled
correctly or not). Also, you probably do not have to patch Squid to achieve
similar effect. Try using the default "." refresh pattern for that (not
exactly the same, but probably close). Refresh statistics in cache manager
will show you how many objects (%) you have digested.
Alex.
------------------------------
Date: Wed, 25 Nov 1998 09:41:58 +0100
From: Robin Breyl <robin.breyl@produktion.gis-online.de>
To: squid-users@ircache.net
Subject: Failed to select source
Message-ID: <365BC2D6.7C5CD8D0@produktion.gis-online.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
thanks for all the replies on my previous questions. Both
problems are solved now.
And, yes, I know about the RFC952 and the illegal undescore.
But the machine is only inside our firewall and no DNS servers
will ever know it's there.
But now I ran into another problem. I still have two proxies
in a hierarchy.
When I open an URL in a browser connected to the "inner" proxy
sometimes not all images on the opened page are loaded.
The logfile (of the inner proxy) show this after accessing the CNN
homepage:
> 1998/11/25 09:31:51| Failed to select source for 'http://images.cnn.com/ads/advertiser/cnn/9805/promos/horoscopes120.gif'
> 1998/11/25 09:31:51| always_direct = -1
> 1998/11/25 09:31:51| never_direct = 1
> 1998/11/25 09:31:51| timedout = 1
> 1998/11/25 09:31:51| Failed to select source for 'http://cnn.com/images/1998/05/homepage/cnn.website.gif'
> 1998/11/25 09:31:51| always_direct = -1
> 1998/11/25 09:31:51| never_direct = 1
> 1998/11/25 09:31:51| timedout = 0
Note, that the html file itself is loaded, only some of the
embedded pictures are not.
Since this is not happening always, but only in about 60% of all
requests, I'm not sure what it is about.
I tried to fiddle around with several timeout settings, but it
didn't changed this behaviour.
Again, any help welcome.
Robin Breyl
-- _________________________________________________________________ / \ | Robin Breyl Geno RZ | | ------------- | | Friedrich-Ebert-Anlage 2-14 | | 60325 Frankfurt am Main | | | | E-Mail (Office): robin.breyl@gis-online.de | | E-Mail (Home): robin.breyl@frankfurt.netsurf.de | | | | Tel.: +49 69 / 75690-369 Fax.: +49 69 / 75690-925 | \_________________________________________________________________/ ------------------------------ Date: Wed, 25 Nov 1998 01:15:25 -0800 From: "Paykar Chamani" <paykar@pacbell.net> To: "Bruce Komito" <brucek@mustang.bagel.com>, <squid-users@ircache.net> Subject: Re: problem reaching home.netscape.com Message-ID: <004b01be1854$2466f800$6500a8c0@paykar.chamani.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Yes, I have the same problem. -----Original Message----- From: Bruce Komito <brucek@mustang.bagel.com> To: squid-users@ircache.net <squid-users@ircache.net> Date: Tuesday, November 24, 1998 1:06 PM Subject: problem reaching home.netscape.com >I've installed squid 2.0 on FreeBSD 3.0 (current) and everything >(apparently) works as advertised except for one thing. I am unable to >reach home.netscape.com through squid. When I either request >home.netscape.com or, from Netscape, click on the "N", the request times >out. The access.log does not show the request. All other sites I have >tried work, including www.netscape.com . When I turn off proxy mode in >the browser (Netscape or IE), I can load home.netscape.com . > >Has anyone ever seen this or a simimlar problem? > >TIA > >Bruce Komito >Sierra Lakes Internet >Voice: (702) 831-8711 Fax: (702) 831-3970 >http://www.slinternet.com > ------------------------------ Date: Wed, 25 Nov 1998 11:44:12 +0100 From: Peter Polkinghorne <Peter.Polkinghorne@brunel.ac.uk> To: squid-users-digest@ircache.net cc: Peter.Polkinghorne@brunel.ac.uk Subject: Re: FAQ request Message-Id: <20312.199811251144@dione.brunel.ac.uk> Content-Type: text/plain; charset=us-ascii Michael T. Babcock said: > Henrik Nordstrom wrote: > > You aren't keeping your log files on the cache disks are you? If > you are then you should defenitely look into moving them to separate > disk(s) both form performance and reliability reasons. > Squid can > cope gracefully with a cache disk that fills up, but not if it can't > write to a log. This applies both to the normal logs, and the > metadata log files. > I haven't checked recently, as my copy's running well, but shouldn't > this be an advisory in the FAQ? It seems common-sense'ish ... I keep > my logs in /var.... and my cache is its own partition, so it can't > over-fill :) ... wouldn't it be a good idea to recommend to new Squid > users to put the cache on its own drive, or at least its own > partition in case, for some reason, it overflows? And to keep the > log files in a seperate partition? > I know one admin who keeps the logs in /home/squid ... because /home > is seperated ... whatever works. To throw another point of view: We keep the logs on the same set of discs as the cache. Rationale: a) system disc is too small to keep logs on (old Suns with 0.5Gb discs) b) with ICP logging off the load on a disc with logging << cache discs, c) so better to smear everything out on striped set of discs (I know there is a reliability trade off here ...) using Online DiscSuite. Comes down to what discs you have and what is the best use of their bandwidth. -- ----------------------------------------------------------------------------- | Peter Polkinghorne, Computer Centre, Brunel University, Uxbridge, UB8 3PH,| | Peter.Polkinghorne@brunel.ac.uk +44 1895 274000 x2561 UK | ----------------------------------------------------------------------------- -------------------------------- End of squid-users-digest Digest V98 Issue #314 ***********************************************Received on Wed Nov 25 1998 - 09:19:25 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:43:21 MST
