[squid-users] (113) no route to host please help

2004-11-25 Thread Bonnici Daniel 
hi all,
I m having a problem with squid 2.5 stable1. Often it gives an error '(113) no
route to host' but if I restart squid it works fine for about 15 to 30 mins.
squid is accepting connection on port 3128. I have also few iptables to accept
connection from the internet and nat to another server (on the internal
network). The ports I am accepting from the internet are 80, 8000, 25 and 110.
does any one have an idea of what is the problem. if any one needs more info
please tell me.
below is a piece from the cache log while trying to access hotmail and the
error occurs.

207.68.171.233
2004/11/17 11:21:19| cbdataValid: 0x8537410
2004/11/17 11:21:19| ipcache_nbgethostbyname: Name 'www.hotmail.com'.
2004/11/17 11:21:19| ipcache_nbgethostbyname: HIT for 'www.hotmail.com'
2004/11/17 11:21:19| cbdataLock: 0x85400e0
2004/11/17 11:21:19| cbdataValid: 0x85400e0
2004/11/17 11:21:19| ipcacheCycleAddr: www.hotmail.com now at 207.68.171.233
2004/11/17 11:21:19| connect FD 18: (115) Operation now in progress
2004/11/17 11:21:19| commConnectHandle: FD 18: COMM_INPROGRESS
2004/11/17 11:21:19| commSetSelect: FD 18 type 2
2004/11/17 11:21:19| cbdataUnlock: 0x85400e0
2004/11/17 11:21:19| comm_poll: 1+0 FDs ready
2004/11/17 11:21:19| comm_poll: FD 18 ready for reading
2004/11/17 11:21:19| comm_poll: FD 18 ready for writing
2004/11/17 11:21:19| ipcacheCycleAddr: www.hotmail.com now at 207.68.171.233
2004/11/17 11:21:19| comm_remove_close_handler: FD 18, handler=0x80669d0,
data=0x85400e0
2004/11/17 11:21:19| cbdataUnlock: 0x85400e0
2004/11/17 11:21:19| commSetTimeout: FD 18 timeout -1
2004/11/17 11:21:19| commConnectFree: FD 18
2004/11/17 11:21:19| cbdataFree: 0x85400e0
2004/11/17 11:21:19| cbdataFree: Freeing 0x85400e0
2004/11/17 11:21:19| cbdataValid: 0x8537410
2004/11/17 11:21:19| fwdFail: ERR_CONNECT_FAIL Service Unavailable
   http://www.hotmail.com/
2004/11/17 11:21:19| cbdataFree: 0x8434a28
2004/11/17 11:21:19| cbdataFree: Freeing 0x8434a28
2004/11/17 11:21:19| comm_close: FD 18
2004/11/17 11:21:19| commCallCloseHandlers: FD 18
2004/11/17 11:21:19| commCallCloseHandlers: ch-handler=0x80718c0
2004/11/17 11:21:19| cbdataValid: 0x8537410
2004/11/17 11:21:19| fwdServerClosed: FD 18 http://www.hotmail.com/
2004/11/17 11:21:19| fwdServerClosed: re-forwarding (10 tries, 0 secs)
2004/11/17 11:21:19| cbdataLock: 0x8537410
2004/11/17 11:21:19| eventAdd: Adding 'fwdConnectStart', in 0.00 seconds
2004/11/17 11:21:19| cbdataUnlock: 0x8537410
2004/11/17 11:21:19| fd_close FD 18 http://www.hotmail.com/
2004/11/17 11:21:19| cbdataUnlock: 0x8537410
2004/11/17 11:21:19| eventRun: RUN ID 2491
2004/11/17 11:21:19| cbdataValid: 0x8537410
2004/11/17 11:21:19| cbdataUnlock: 0x8537410
2004/11/17 11:21:19| eventRun: Running 'fwdConnectStart', id 2490
2004/11/17 11:21:19| fwdConnectStart: http://www.hotmail.com/
2004/11/17 11:21:19| fwdConnectStart: got addr 0.0.0.0, tos 0
2004/11/17 11:21:19| comm_open: FD 18 is a new socket
2004/11/17 11:21:19| fd_open FD 18 http://www.hotmail.com/
2004/11/17 11:21:19| comm_add_close_handler: FD 18, handler=0x80718c0,
data=0x8537410
2004/11/17 11:21:19| cbdataLock: 0x8537410
2004/11/17 11:21:19| commSetTimeout: FD 18 timeout 120
2004/11/17 11:21:19| commConnectStart: FD 18, www.hotmail.com:80
2004/11/17 11:21:19| cbdataLock: 0x8537410
2004/11/17 11:21:19| comm_add_close_handler: FD 18, handler=0x80669d0,
data=0x85400e0
2004/11/17 11:21:19| cbdataLock: 0x85400e0
2004/11/17 11:21:19| ipcache_nbgethostbyname: Name 'www.hotmail.com'.
2004/11/17 11:21:19| ipcache_nbgethostbyname: HIT for 'www.hotmail.com'
2004/11/17 11:21:19| cbdataLock: 0x85400e0
2004/11/17 11:21:19| cbdataValid: 0x85400e0
2004/11/17 11:21:19| ipcacheCycleAddr: www.hotmail.com now at 207.68.171.233
2004/11/17 11:21:19| fqdncache_nbgethostbyaddr: Name '207.68.171.233'.
2004/11/17 11:21:19| fqdncache_nbgethostbyaddr: MISS for '207.68.171.233'
2004/11/17 11:21:19| idnsPTRLookup: buf is 45 bytes for 207.68.171.233, id =
0x47e
2004/11/17 11:21:19| cbdataLock: 0x8423660
2004/11/17 11:21:19| commSetSelect: FD 5 type 1
2004/11/17 11:21:19| connect FD 18: (115) Operation now in progress
2004/11/17 11:21:19| commConnectHandle: FD 18: COMM_INPROGRESS
2004/11/17 11:21:19| commSetSelect: FD 18 type 2
2004/11/17 11:21:19| cbdataUnlock: 0x85400e0
2004/11/17 11:21:19| comm_poll: 1+0 FDs ready
2004/11/17 11:21:19| comm_poll: FD 18 ready for reading
2004/11/17 11:21:19| comm_poll: FD 18 ready for writing
2004/11/17 11:21:19| ipcacheMarkBadAddr: www.hotmail.com [207.68.171.233]
2004/11/17 11:21:19| ipcacheCycleAddr: Changing ALL www.hotmail.com addrs from
BAD to OK
2004/11/17 11:21:19| ipcacheCycleAddr: www.hotmail.com now at 207.68.172.239
2004/11/17 11:21:19| cbdataValid: 0x8537410
2004/11/17 11:21:19| ipcache_nbgethostbyname: Name 'www.hotmail.com'.
2004/11/17 11:21:19| ipcache_nbgethostbyname: HIT for 'www.hotmail.com'
2004/11/17 11:21:19| cbdataLock: 0x85400e0
2004/11/17 11:21:19| cbdataValid: 0x85400e0
2004/11/17 11:21:19| ipcacheCycleAddr:

RE: [squid-users] (113) no route to host please help

2004-11-25 Thread Elsen Marc 

 
 
 hi all,
 I m having a problem with squid 2.5 stable1. Often it gives 
 an error '(113) no
 route to host' but if I restart squid it works fine for about 
 15 to 30 mins.
 squid is accepting connection on port 3128. I have also few 
 iptables to accept
 connection from the internet and nat to another server (on 
 the internal
 network). The ports I am accepting from the internet are 80, 
 8000, 25 and 110.
 does any one have an idea of what is the problem. if any one 
 needs more info
 please tell me.
 below is a piece from the cache log while trying to access 
 hotmail and the
 error occurs.
 
 
 Normally, 'no route to host' is returned  by the
ip stack and says what is says : a problemof network
routing when trying to reach www.hotmail.com.

Try , for instance :

 # traceroute www.hotmail.com

from the squid box at that time; see whether this works.

Also : upgrade to the latest stable release; 2.5.stable1 is way
old and in between tons and tons of bugs have been fixed.
Although this particular issue is not squid related
but comes from the networking layer.

M.