* Pete Vickers <[email protected]> [2010-03-01 12:28]: > okay, sounds reasonable. I've also 'fiddled with other knobs' too, so I hope > my kern.maxclusters at 8192 should not cause exhaustion conjunction with: > > > net.inet.ip.ifq.maxlen=512 > net.inet.tcp.recvspace=262144 > net.inet.tcp.sendspace=262144 > kern.maxfiles=8192 > kern.maxclusters=8192 > > > BTW, when the system runs out of (these?) resources, it sometimes prevents SSH > access or squid use, but still keeps a CARP peering alive, preventing failover > to it's backup partner, which is somewhat frustrating (I know I could script > around this).
this is perfectly sane and the intended bahaviour. no mbufs / clusters available -> packet dropped. > On other occasions, it drops into ddb> , which at least allows > the CARP backup to take over duties. (I know I should file a bug report for > this) yes, in an idea world that doesn't happen and the system copes with the ressource shortage. -- Henning Brauer, [email protected], [email protected] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
