TCP connection failures to peer caches

I've seen this problem being tossed around a while ago, with no clear
solution. I have a squid cache with 3 round-robin parents, running on
HP9000(HP-UX 10.10). With an increase in the number of client requests,
The squid logs have started showing TCP connection failures to different
cache peers. The problem would persist until I reboot the machine, which hints
to an OS related issue. Knowing that this has occured on other platforms, I'm
really puzzeled.

As the logs below show, the connect() system call is failing with 227 return code,
"Can't assign requested address", I think the failure is at the bind() call.

I appreciate any help,

------------------------------ Debug ALL, 9 -----------------------------------
2000/03/07 13:54:05| peerSelect: ROUNDROBIN_PARENT/terra-proxy3
2000/03/07 13:54:05| peerAddFwdServer: adding terra-proxy3 ROUNDROBIN_PARENT
2000/03/07 13:54:05| cbdataLock: 40128fe8
2000/03/07 13:54:05| peerSelectCallback: http://chat.optichat.com/optichat.html?oc_id=ggpI&oc
_stage=5&oc_input=&oc_send_num=20&oc_con=2
2000/03/07 13:54:05| cbdataValid: 404a0818
2000/03/07 13:54:05| fwdStartComplete: http://chat.optichat.com/optichat.html?oc_id=ggpI&oc_s
tage=5&oc_input=&oc_send_num=20&oc_con=2
2000/03/07 13:54:05| fwdConnectStart: http://chat.optichat.com/optichat.html?oc_id=ggpI&oc_st
age=5&oc_input=&oc_send_num=20&oc_con=2
2000/03/07 13:54:05| comm_open: FD 108 is a new socket
2000/03/07 13:54:05| fd_open FD 108 http://chat.optichat.com/optichat.html?oc_id=ggpI&oc_stag
e=5&oc_input=&oc_send_num=20&oc_con=2
2000/03/07 13:54:05| comm_add_close_handler: FD 108, handler=400021da, data=404a0818
2000/03/07 13:54:05| cbdataLock: 404a0818
2000/03/07 13:54:05| commSetTimeout: FD 108 timeout 120
2000/03/07 13:54:05| commConnectStart: FD 108, terra-proxy3:8082
2000/03/07 13:54:05| cbdataAdd: 40518848
2000/03/07 13:54:05| cbdataLock: 404a0818
2000/03/07 13:54:05| comm_add_close_handler: FD 108, handler=40002182, data=40518848
2000/03/07 13:54:05| cbdataLock: 40518848
2000/03/07 13:54:05| ipcache_nbgethostbyname: Name 'terra-proxy3'.
2000/03/07 13:54:05| ipcache_nbgethostbyname: HIT for 'terra-proxy3'
2000/03/07 13:54:05| cbdataLock: 40518848
2000/03/07 13:54:05| cbdataValid: 40518848
2000/03/07 13:54:05| ipcacheCycleAddr: terra-proxy3 now at 212.98.130.38
2000/03/07 13:54:05| connect FD 108: (227) Can't assign requested address
2000/03/07 13:54:05| ipcacheMarkBadAddr: terra-proxy3 [212.98.130.38]
2000/03/07 13:54:05| ipcacheCycleAddr: Changing ALL terra-proxy3 addrs from BAD to OK
2000/03/07 13:54:05| ipcacheCycleAddr: terra-proxy3 now at 212.98.130.38
2000/03/07 13:54:05| cbdataValid: 404a0818
2000/03/07 13:54:05| ipcache_nbgethostbyname: Name 'terra-proxy3'.
2000/03/07 13:54:05| ipcache_nbgethostbyname: HIT for 'terra-proxy3'
2000/03/07 13:54:05| cbdataLock: 40518848
2000/03/07 13:54:05| cbdataValid: 40518848
2000/03/07 13:54:05| ipcacheCycleAddr: terra-proxy3 now at 212.98.130.38
2000/03/07 13:54:05| connect FD 108: (227) Can't assign requested address
2000/03/07 13:54:05| ipcacheMarkBadAddr: terra-proxy3 [212.98.130.38]
2000/03/07 13:54:05| ipcacheCycleAddr: Changing ALL terra-proxy3 addrs from BAD to OK
2000/03/07 13:54:05| ipcacheCycleAddr: terra-proxy3 now at 212.98.130.38
2000/03/07 13:54:05| cbdataValid: 404a0818
2000/03/07 13:54:05| ipcache_nbgethostbyname: Name 'terra-proxy3'.
2000/03/07 13:54:05| cbdataLock: 40518848
2000/03/07 13:54:05| cbdataValid: 40518848
2000/03/07 13:54:05| ipcacheCycleAddr: terra-proxy3 now at 212.98.130.38
2000/03/07 13:54:05| connect FD 108: (227) Can't assign requested address
2000/03/07 13:54:05| ipcacheMarkBadAddr: terra-proxy3 [212.98.130.38]
2000/03/07 13:54:05| ipcacheCycleAddr: Changing ALL terra-proxy3 addrs from BAD to OK
2000/03/07 13:54:05| ipcacheCycleAddr: terra-proxy3 now at 212.98.130.38
2000/03/07 13:54:05| comm_remove_close_handler: FD 108, handler=40002182, data=40518848
2000/03/07 13:54:05| cbdataUnlock: 40518848
2000/03/07 13:54:05| commSetTimeout: FD 108 timeout -1
2000/03/07 13:54:05| commConnectFree: FD 108
2000/03/07 13:54:05| cbdataFree: 40518848
2000/03/07 13:54:05| cbdataFree: 40518848 has 3 locks, not freeing
2000/03/07 13:54:05| cbdataValid: 404a0818
2000/03/07 13:54:05| fwdFail: ERR_CONNECT_FAIL "Service Unavailable"
        http://chat.optichat.com/optichat.html?oc_id=ggpI&oc_stage=5&oc_input=&oc_send_num=20
&oc_con=2
2000/03/07 13:54:05| TCP connection to terra-proxy3/8082 failed
2000/03/07 13:54:05| cbdataLock: 40128fe8
2000/03/07 13:54:05| eventAdd: Adding 'peerCheckConnect', in 30.000000 seconds
2000/03/07 13:54:05| comm_close: FD 108
2000/03/07 13:54:05| commCallCloseHandlers: FD 108
2000/03/07 13:54:05| commCallCloseHandlers: ch->handler=400021da
2000/03/07 13:54:05| cbdataValid: 404a0818
2000/03/07 13:54:05| fwdServerClosed: FD 108 http://chat.optichat.com/optichat.html?oc_id=ggp
I&oc_stage=5&oc_input=&oc_send_num=20&oc_con=2
2000/03/07 13:54:05| fwdServerClosed: re-forwarding (1 tries, 0 secs)
2000/03/07 13:54:05| cbdataLock: 404a0818
2000/03/07 13:54:05| eventAdd: Adding 'fwdConnectStart', in 0.000000 seconds
2000/03/07 13:54:05| cbdataUnlock: 404a0818
2000/03/07 13:54:05| fd_close FD 108 http://chat.optichat.com/optichat.html?oc_id=ggpI&oc_sta
ge=5&oc
---------------------------End of debug--------------------------------

------------------------------
Hassan Hassoun
hhassoun@aub.edu.lb
PCNS
American University of Beirut
hassoun@aub.edu.lb
Tel: +961 1 350000 ext. 2270
------------------------------
Received on Wed Mar 08 2000 - 05:44:01 MST