"connect-fail-limit=" will not help with re-enabling peers. It only determines how many tries are needed to detect when one goes dead.
This behaviour is known to appear when ICP, HTCP and ICMP are all disabled on the peer link. Squid uses them to do background checks for recovered peers. If any one of these protocols is usable the peer will be detected live as soon as one request to it succeeds. Squid-3 does not yet have the background HTTP support needed to monitor the peer without causing disruption to the clients. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/591365 Title: Squid3.0 provides no option for re-enabling a cache peer -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
