Date: Wed, 14 Nov 2001 09:01:16 -0600 From: Eric Anderson <anderson@centtech.com> To: freebsd-security@freebsd.org Subject: Re: listrl0: no memory for tx Message-ID: <3BF2873C.4E47BBFE@centtech.com> References: <NFEFKFLOLCMOGLIMEBEOGEPCCNAA.listas@esnx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I actually did this, jacking those nmbclusters way up, buteven then, they would top out and the box would quit responding. So in essence, I jacked those up AND tweaked other stuff, and it's been fine since. Not 100% what Sven's problem is, but I'm with you on the "not hardware" thing. Hardware could suck, but I think you can tweak around it. Eric Marcos Martinelli wrote: > > This means that your network memory buffer is not enough to your network > traffic. > > if you are using FreeBSD, put in your /boot/loader.conf : > > kern.ipc.nmbclusters="8192" > kern.ipc.nmbufs="32768" > > you can see if the problem is it with the command: netstat -m > > > [root@pituba root]# netstat -m > > 1650/2000/4096 mbufs in use (current/peak/max): > > 1469 mbufs allocated to data > > 124 mbufs allocated to packet headers > > 57 mbufs allocated to socket names and addresses > > 1024/1024/1024 mbuf clusters in use (current/peak/max) > > 2548 Kbytes allocated to network (82% of mb_map in use) > > 8436 requests for memory denied > > 71 requests for memory delayed > > 0 calls to protocol drain routines > > Its nothing related to hardware problem > > -----Original Message----- > From: owner-freebsd-security@FreeBSD.ORG > [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Eric Anderson > Sent: Wednesday, November 14, 2001 11:16 AM > To: Sven Giersig > Cc: freebsd-security > Subject: Re: listrl0: no memory for tx > > I have seen similar messages on an NFS server that was > extremely overloaded. I did a few sysctl tweaks to the tcp > window sizes and such, and a few other things, so the > machine could keep up with the hundreds of P4's beating the > crud out of it. If it's your firewall, I'd be looking at it > with a fine toothed comb right now. > > Eric > > Sven Giersig wrote: > > > > Hello List, > > since the last night I have entries in my syslog like > > listrl0: no memory for tx ... (repeated) > > rl0 is the internal interface on a fw-machine - and should have had less > traffic at night! > > > > does it mean > > - I have to add more memory? > > - my NIC is broken? > > - cable? > > > > thanks for any hints, > > Sven > > > > -- > > Sven Giersig | > > mailto: smg@weird.dnsalias.org | Unix Inter-Networking > > mobile: +49-172-8049514 | Directory Services > > https://weird.dnsalias.org/~smg | > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > -- > ------------------------------------------------------------- > Eric Anderson anderson@centtech.com Centaur Technology > No single raindrop believes it is to blame for the flood. > ------------------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- ------------------------------------------------------------- Eric Anderson anderson@centtech.com Centaur Technology No single raindrop believes it is to blame for the flood. ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BF2873C.4E47BBFE>