Sorry for the few informations logs i gave you, but the squid servers runs
in a big production.
with 600+ sim connexions on load-balanced squid servers.

Here is the only information i could give you.

The downtime was between 08:30 and 11:30

In access.log, nothing special, it seems to works, but the problem is
different from the internet site where we have a 304 error like this..
[Wed Jul  2 10:54:42 2003].593     17 172.16.98.10 TCP_IMS_HIT/304 213 GET
http://eur.i1.yimg.com/eur.yimg.com/i/fr/msg/msgmm.gif - NONE/- image/gif

and in cache.log , some informations below .. the admin tries to restart
several time squid process that explain some shutting down infos.
-----------------------
2003/07/02 10:52:18| WARNING: Closing client 172.16.98.63 connection due to
lifetime timeout
2003/07/02 10:52:18|    http://fr.news.yahoo.com/

2003/07/02 09:43:13| idnsSendQuery: Can't send query, no DNS socket!
2003/07/02 09:43:17| idnsSendQuery: Can't send query, no DNS socket!
2003/07/02 09:43:37| Shutting down...

2003/07/02 10:52:18| WARNING: Closing client 172.16.98.63 connection due to
lifetime timeout
2003/07/02 10:52:18|    http://fr.news.yahoo.com/

FATAL: Could not find any nameservers.
       Please check your /etc/resolv.conf file
       or use the 'dns_nameservers' option in squid.conf.
Squid Cache (Version 2.5.STABLE1): Terminated abnormally.
-----------------

In access.log
----------------
[Wed Jul  2 10:43:42 2003].146   9487 172.16.85.63 TCP_MISS/200 277350
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:43:55 2003].065  10035 172.16.85.63 TCP_MISS/200 1513
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:05 2003].207  10044 172.16.85.63 TCP_MISS/200 9619
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:15 2003].315  10037 172.16.85.63 TCP_MISS/200 4755
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:25 2003].615  10088 172.16.85.63 TCP_MISS/200 2082
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:25 2003].628  10101 172.16.85.63 TCP_MISS/200 1962
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:25 2003].630  10059 172.16.85.63 TCP_MISS/200 542 CONNECT
karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:25 2003].632  10065 172.16.85.63 TCP_MISS/200 1408
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:35 2003].755  10070 172.16.85.63 TCP_MISS/200 542 CONNECT
karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:35 2003].761  10057 172.16.85.63 TCP_MISS/200 1321
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:35 2003].765  10062 172.16.85.63 TCP_MISS/200 1074
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:42 2003].866  10291 172.16.85.63 TCP_MISS/200 1968
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -
text/html
[Wed Jul  2 10:44:45 2003].964  10035 172.16.85.63 TCP_MISS/200 533 CONNECT
karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:45 2003].984  10032 172.16.85.63 TCP_MISS/200 533 CONNECT
karma.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 10:44:46 2003].473  10696 172.16.85.63 TCP_MISS/200 276030
CONNECT karma.devoteam.com:443 - DIRECT/172.16.2.10 -


[Wed Jul  2 09:17:18 2003].649   4901 172.16.98.29 TCP_MISS/000 0 GET
http://www.mistergooddeal.com/ - NONE/- -
[Wed Jul  2 09:17:33 2003].731    216 172.16.98.29 TCP_MISS/200 1130
CONNECT applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:33 2003].771     20 172.16.98.29 TCP_MISS/200 185 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
Wed Jul  2 09:17:35 2003].129    182 172.16.98.29 TCP_MISS/200 418 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:35 2003].145     58 172.16.98.29 TCP_MISS/200 418 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:35 2003].179     32 172.16.98.29 TCP_MISS/200 419 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:41 2003].059  16802 172.16.98.29 TCP_MISS/000 0 GET
http://www.pussy.org/ - NONE/- -
[Wed Jul  2 09:17:47 2003].941  75084 172.16.98.29 TCP_MISS/000 0 POST
http://bannerserver.gator.com/bannerserver/bannerserver.dll? - NONE/- -
[Wed Jul  2 09:17:50 2003].180  15033 172.16.98.29 TCP_MISS/200 419 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:50 2003].180  15025 172.16.98.29 TCP_MISS/200 417 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:50 2003].260  15041 172.16.98.29 TCP_MISS/200 418 CONNECT
applis.devoteam.com:443 - DIRECT/172.16.2.10 -
[Wed Jul  2 09:17:51 2003].106   3100 172.16.98.29 TCP_MISS/000 0 GET
http://www.pussy.org/ - NONE/- -
[Wed Jul  2 09:18:01 2003].367   4399 172.16.98.29 TCP_MISS/000 0 GET
http://www.cowlist.com/ - NONE/- -
--

On the Reverse proxy logs, i have no informations, when client 172.16.2.10
tries to connect to applis.devoteam.com or karma.devoteam.com (my internal
web services, which /etc/hosts file returns for the fqdn 172.16.2.10).
Then, if i have no log informations in the downtime period at all, it
explains the non-communication between squid and the local web service on
the reverse proxy (running on the same host). No ?

Problem is a DNS tiemout problem, and on the client the request timeouts
serveral minutes laters.

On the client, if i try to contact directly the local web service
applis.devoteam.com without passing through the squid proxy, it works
prefectly and get a result page in 0.1 seconds.

Can't help you more... i m sorry but it s a strange problem to my eyes and
quite hard to trace.

Tony



                                                                                       
                                                
                      Henrik Nordstrom                                                 
                                                
                      <[EMAIL PROTECTED]        Pour :    [EMAIL PROTECTED], [EMAIL 
PROTECTED]                           
                      org>                     cc :                                    
                                                
                                               Objet :   Re: [squid-users] Problems 
when DNS queries timeout                           
                      04/07/2003 19:57                                                 
                                                
                                                                                       
                                                
                                                                                       
                                                




On Friday 04 July 2003 17.31, [EMAIL PROTECTED] wrote:

> when we ask the proxy for applis.toto.com (when internet line is
> down and then dns query unavailable) it doesn't  work as if it was
> always doing DNS queries
> although it should look up first my /etc/hosts file to get the IP.

And what result do you get?

a) Is there an error message returned to the client? In such case,
what error message?

b) What is logged in access.log?

c) Anything in the logs of the contacted server (reverse proxy)?

Regards
Henrik

--
Donations welcome if you consider my Free Squid support helpful.
https://www.paypal.com/xclick/business=hno%40squid-cache.org

If you need commercial Squid support or cost effective Squid or
firewall appliances please refer to MARA Systems AB, Sweden
http://www.marasystems.com/, [EMAIL PROTECTED]





+--------------------------------------------------------------------------+
About the DEVOTEAM GROUP
                        
Devoteam is a leading European IT Consulting Group. We help our customers
build corporate results from innovative information technology solutions.
The group recorded 2002 turnover of 136 Meuros with 1700 employees in 7
european countries (Austria, Belgium, Denmark, France, Spain, Netherlands, UK).
Listed on Euronext Nouveau Marche since October 28, 1999 (Euroclear 7379)
Member of Euronext Paris index: Nexteconomy, IT CAC 50, SBF 250.
Web site : http://www.devoteam.com
+--------------------------------------------------------------------------+

Reply via email to