Sorry, forgot the details: Squid Cache: Version 2.7.STABLE9 configure options: '--prefix=/squid2' '--enable-async-io' '--enable-icmp' '--enable-useragent-log' '--enable-snmp' '--enable-cache-digests' '--enable-follow-x-forwarded-for' '--enable-storeio=null,aufs' '--enable-removal-policies=heap,lru' '--with-maxfd=16384' '--enable-poll' '--disable-ident-lookups' '--enable-truncate' '--with-pthreads' 'CFLAGS=-DNUMS=60 -march=nocona -O3 -pipe -fomit-frame-pointer -funroll-loops -ffast-math -fno-exceptions' Linux server.domain.com 2.6.18-8.1.10.el5 #1 SMP Thu Aug 30 20:43:28 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux On Thu, Oct 7, 2010 at 10:52 AM, david robertson <dr@xxxxxxxxxxxx> wrote: > Hello, I know this isn't specifically a squid thing, but I think it > might be semi-related. > > I've currently got a Dell 6850 (16gb ram, 16 logical processors) > server set up, based on the 'one frontend, two backends' example on > squid-cache.org. Everything will be fine, but once the cache starts > getting 170+ inbound hits/sec, I get this in dmesg, and the load > shoots up on the server, causing squid to grind to a halt. > > Out of socket memory > printk: 29 messages suppressed. > Out of socket memory > printk: 48 messages suppressed. > TCP: too many of orphaned sockets > printk: 53 messages suppressed. > Out of socket memory > printk: 53 messages suppressed. > TCP: too many of orphaned sockets > printk: 101 messages suppressed. > TCP: too many of orphaned sockets > printk: 328 messages suppressed. > > > Any ideas on what I can do to alleviate this? >
