Hi all,
yesterday we had some strange problems running our reverse-proxy squid cluster.
During some high-traffic sports event, squid starts to emit messages
like:
commBind: Cannot bind socket FD 98 to *:0: (98) Address already in use
In front of every squid resides an apache2 (on the same hardware, to handle
redirects and that stuff) that logs messages like:
(99)Cannot assign requested address: proxy: HTTP: attempt to connect to 127.0.0.2:80 (*) failed
When the traffic came back to normal, the problems vanished.
What's that supposed to mean? Any ideas?
Thank you for your help
Stefan
Received on Fri Feb 02 2007 - 06:12:01 MST
This archive was generated by hypermail pre-2.1.9 : Thu Mar 01 2007 - 12:00:01 MST