Re: problems with 1.1.1

oskar@is.co.za writes:

>Hi there
>
>I am having a couple of problems with squid 1.1.1:
>I have been running this version for a few weeks without hassles on
>a linux machine, kernel 2.0.24
>
>Yesterday our second cache (we load balance between two cache machines
>just hung up (stopped accepting connections). An strace showed:
>
>read(898, "\345\360\3433\34!\226\267]h\362\227"..., 65535) = 1460
>gettimeofday({852886178, 207491}, NULL) = 0
>gettimeofday({852886178, 207842}, NULL) = 0
>oldselect(927, ..., ..., NULL, {1, 0}) = 4 (in [201 336 36 5]
>, out [843], left {0, 990000})
>gettimeofday({852886178, 222081}, NULL) = 0
>oldselect(21, [20], [], NULL, {0, 0}) = 0 (Timeout)
>gettimeofday({852886178, 223780}, NULL) = 0
>oldselect(21, [20], [], NULL, {0, 0}) = 0 (Timeout)
>gettimeofday({852886178, 225123}, NULL) = 0
>oldselect(21, [20], [], NULL, {0, 0}) = 0 (Timeout)
>gettimeofday({852886178, 226426}, NULL) = 0
>oldselect(21, [20], [], NULL, {0, 0}) = 0 (Timeout)
>write(843, "\345\360\3433\34!\226\267]h\362\227"..., 1460) = 1460
>gettimeofday({852886178, 229118}, NULL) = 0
>
>over and over again. (ie Select didn't seem to show that there was any activit
y on any open filehandles)

This looks perfectly normal. The four select() calls on FD 20 are
checking the ICP socket. Notice after that there is a write() on
FD 843.

My guess is that your cache stopped accepting connections because
it was close to the max number of descriptors. Squid waits for
current connections to go away before accepting more.

>Cache2 runs 1.1.1
>newt:~/squid/echoping> ./echoping -n 5 -h http://www.vodacom.co.za/ cache2:808
0
>Elapsed time: 3.242044 seconds
>Elapsed time: 3.804418 seconds
>Elapsed time: 3.010914 seconds
>Elapsed time: 3.101601 seconds
>Elapsed time: 3.144090 seconds
>---
>Minimum time: 3.010914 seconds (85 bytes per sec.)
>Maximum time: 3.804418 seconds (67 bytes per sec.)
>Average time: 3.260613 seconds (79 bytes per sec.)
>Median time: 3.144090 seconds (81 bytes per sec.)
>newt:~/squid/echoping>
>
>Clearly squid 1.1 is getting the page from the real site every time, with
>the logs showing
>852973763.314 3115 196.23.0.84 TCP_REFRESH_MISS/200 4716 GET http://www.voda
com.co.za/ - DIRECT/www.vodacom.co.za text/html
>
>But if I look at the headers there doesn't seem to be any "meta" info... and
>cache manager shows:
>17.http://www.vodacom.co.za/
> Verified 27Y ago, Used 3s ago, Modified 19s ago, Expires 27Y ago,
> 0 bytes, 1 accesses, 1 active clients,
> STORE_PENDING, NOT_IN_MEMORY, NO_SWAP, PING_NONE,
> 2 Locks, Flags: EC,KC,HT,ED,KP,HI

There is no last-modified time. For these Squid usually issues
IMS requests because it can't calculate the 'age factor'.
Doing so would result in a divide-by-zero.

Duane W.
Received on Mon Jan 13 1997 - 16:43:52 MST