Looks like it's because your cache peer is not available at your boottime.
Remove the cache_peer or take squid off your boot time scripts and only run
it after you establish teh connection.
-----Original Message-----
From: Joao Clemente [mailto:jpcl@rnl.ist.utl.pt]
Sent: 29 July 2001 17:59
To: squid-users@squid-cache.org
Subject: [squid-users] How can I prevent squid from checking dns server
at startup?
Hello.
I've been having the following problem:
I have a dialup/NAT machine on wich I want to set squid to do proxy for a
local network...
When I boot the machine (no connection to the internet as it ias a dial up
connection) I startup squid
from one of the boot scripts..
The problem is that ( I think ) squid tries to do some dns queries to do
some checking and then I have in my logs:
Jul 29 14:36:34 squid[64]: Squid Parent: child process 66 started
Jul 29 14:36:44 (squid): ipcache_init: DNS name lookup tests failed.
Jul 29 14:36:44 squid[64]: Squid Parent: child process 66 exited with status
1
................................................
Jul 29 14:37:00 squid[64]: Squid Parent: child process 79 started
Jul 29 14:37:00 (squid): ipcache_init: DNS name lookup tests failed.
Jul 29 14:37:00 squid[64]: Squid Parent: child process 79 exited with status
1
Jul 29 14:37:00 squid[64]: Exiting due to repeated, frequent failures
So, what can I place and where to prevent this?
I'm using squid 2.4 stable 1
(I'm thinking that If I knew WHAT is squid trying to lookup I could place
that in my /etc/resolv.conf... what do you think?)
Thank you
Received on Mon Jul 30 2001 - 08:07:24 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:20 MST