Search squid archive

no more data left in socket

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux