Hi list, I experience a strange problem last couple of days with Squid. I found a lot of entries in cache.log showing this:
2006/04/04 22:38:55| commBind: Cannot bind socket FD 37 to *:0: (98) Address already in use This results in showing blank page (most of times) in client browser. I googled for a while and i've found this in squid's FAQs: "11.11 Cannot bind socket FD NN to *:8080 (125) Address already in use This means that another processes is already listening on port 8080 (or whatever you're using). It could mean that you have a Squid process already running, or it could be from another program." But netstat gave me nothing unexpected and unusual... Box is Celeron 1,2GHz 128MB RAM, running TSL 2.2, squid-2.5.STABLE13-1tr as transparent proxy with 2GB swap space and DansGuardian on top and is a GW for LAN with about 30 users. Last time i've upgraded squid was 20. march 2006. First time the problem showed up was 28. march 2006. No problems in the past. A have another box Athlon 1GHz, 256MB RAM, running TSL 3.0 configured and working in almost the same fasion for about 60 users in LAN. Same versions of squid and DansGuardian. No problems here for months. A workaround was to rastart DansGuardian service and everything seemed to be OK for some time, but problem showed up again. Does anyone experience the same problem ? Is it a squid's bug ? Can someone help me solve this ? Thanks in advance -- Jaroslav Vrbicky _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
