2010/9/9 Martin Pelikan <[email protected]>: Hello Martin,
> I thought the same when I played with TCP buffers set to 1M and after > some heavy load tests I went out of RAM quite soon :-) The machine had > 2G. Well, the machine has 6Gb of RAM and is only pushing 10Mbit/s of traffic at peak. It does need to maintain a largeish state table, as it is predominatly web traffic, but I've run much much larger and busier sites behind much smaller hardware with the same configs before. > I assume ping doesn't work either. Have you raised the recv/send > space? Have you tried entering ddb? (you need to set the sysctl before > start) No, both machines don't ping and they completely hardlock. I can only think it is an issue with pfsync, which causes both to lock up at the same time, but that is a guess. I guess I'll just upgrade them to 4.7 speculatively and hope it doesn't happen again. recv/send: net.inet.tcp.recvspace=16384 net.inet.udp.recvspace=41600 j...@f1:/home/joe> sysctl -a |grep send net.inet.tcp.sendspace=16384 net.inet.udp.sendspace=9216 Too low? What is a good value for them? Thanks for your assistance. -- joe.
