after discussing this with Yuri we have thinking is the problem in close-wait connections, i try to put half_closed_clients off but this didnt solve the problem some thing here make this assertion error since it not happen immediately , some times every 20 min and some times it need 5 hours to exist now i set /proc/sys/net/ipv4/tcp_keepalive_time = 900 since it is 7200 by default in linux but after watching netstat to close connection i got this Every 2.0s: netstat -antop | grep -iE --regexp="close" Thu Apr 23 00:42:07 2015 tcp 18382 0 192.168.50.4:37692 216.58.210.226:80 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 1 0 192.168.70.4:3127 192.168.70.11:60376 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 1 0 192.168.70.4:3128 192.168.70.5:1810 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 1 0 192.168.70.4:3127 192.168.70.11:60375 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 1 0 192.168.50.4:56114 205.185.208.26:80 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 1 0 192.168.70.4:3128 192.168.70.11:42139 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 27099 0 192.168.50.4:35004 216.58.210.226:80 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) tcp 42209 0 192.168.50.4:42235 68.232.34.189:80 CLOSE_WAIT 2619/(squid-1) off (0.00/0/0) and most of these ip's is in none ssl bump since no relation ... i dont know if this will be more helpfull ? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670726p4670870.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
