[squid-users] no more data left in socket

From: Nathan Ridge <ridgey_at_matilda.net.au>
Date: Mon, 04 Jul 2011 11:00:42 +1000

Hi,

I wonder if someone could assist me with an issue im having.

Since last week, pretty much all of a sudden im seeing these errors in
my cache.log

2011/07/04 10:29:39| clientEatRequestBodyHandler: FD 119: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:39| clientEatRequestBodyHandler: FD 119: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:39| clientEatRequestBodyHandler: FD 440: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:39| clientEatRequestBodyHandler: FD 636: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:39| clientEatRequestBodyHandler: FD 636: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:39| clientEatRequestBodyHandler: FD 119: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:40| clientEatRequestBodyHandler: FD 179: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:40| clientEatRequestBodyHandler: FD 179: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:40| clientEatRequestBodyHandler: FD 179: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:40| clientEatRequestBodyHandler: FD 1100: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:41| clientEatRequestBodyHandler: FD 1100: no more data
left in socket; but request header says there should be; aborting for now
2011/07/04 10:29:41| clientEatRequestBodyHandler: FD 1426: no more data
left in socket; but request header says there should be; aborting for now

thousands of them.

from what i read its a ram issue but its been working fine with the 12GB
of ram it has for years, i have 2 identical boxes, configs etc and the
other is not showing the same error.

Any help appreciated.

Regards
Nathan
Received on Mon Jul 04 2011 - 01:01:06 MDT

This archive was generated by hypermail 2.2.0 : Mon Jul 04 2011 - 12:00:02 MDT