I've just upgraded the distribution on my main machine to SuSE 7.0 (I know,
I know - I've more to be doing than living on the bleeding edge) and squid
is dying. Whenever I tried to access a URL by name in Netscape, I got a
"Document contains no data." alert and there was an entry like
2001/05/09 09:52:40| assertion failed: dns_internal.c:212: "nns > 0"
in cache.log, immediately followed by
2001/05/09 09:52:43| Starting Squid Cache version 2.3.STABLE3 . . .
which I presume means that Squid has restarted.
My resolv.conf had no nameserver entries (they get inserted on the fly by
wvdial) so I put in a couple. This stops squid from crashing, but instead I
see a lot of entries in cache.log about squid being unable to reach the
2001/05/09 10:20:11| comm_udp_sendto: FD 2, 184.108.40.206, port 53: (101)
Network is unreachable
2001/05/09 10:20:11| idnsSendQuery: FD 2: sendto: (101) Network is unreachable
These are unsurprising as I was offline at the the time :-)
The strange thing is that squid should not have tried to do a DNS lookup for
the requested address - it's on my local LAN, nsswitch.conf is configured
correctly (I can ping the relevant address by name) so why is squid trying
to do a DNS lookup and how do I stop it ?
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!