Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Nov 2003 23:21:44 +0000
From:      Daniela <dgw@liwest.at>
To:        "Jack L. Stone" <jacks@sage-american.com>, freebsd-questions@freebsd.org
Subject:   Re: Help! Runaway NATD
Message-ID:  <200311102321.44756.dgw@liwest.at>
In-Reply-To: <3.0.5.32.20031110160157.0142b020@10.0.0.15>
References:  <3.0.5.32.20031110151819.01431468@10.0.0.15> <3.0.5.32.20031110160157.0142b020@10.0.0.15>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 10 November 2003 22:01, Jack L. Stone wrote:
> At 10:42 PM 11.10.2003 +0000, Daniela wrote:
> >On Monday 10 November 2003 21:18, Jack L. Stone wrote:
> >> FreeBSD 4.8-RELEASE-p13 - GW/router/NAT/FW/Caching DNS - Bind-8.3x +
> >> IPFW(8)
> >>
> >> Have just setup the above to route mainly for a LAN (in place of
> >> hardware router), but natd runs non-stop as per TOP(1) and keeps eating
> >> up the CPU until it crashes. Takes about 1/2 hour to eat up the
> >> resources and requires a reboot -- then the problem just starts over
> >> again.
> >
> >Have you tried to attach to the process with gdb(1) or truss(1)?
> >Also please show us what `ps ax` says about natd.
> >Can you get a core dump?
> >
> >Good luck!
> >Daniela
>
> Thanks for the quick reply. No, haven't had chance to redo the kernel for
> gdb, etc. But, here's some more info from the "ps -ax" and log. The tcp
> start out very small and keep growing in big leaps as below -- this is just
> before running out of CPU....

I'd definitely need at least the output of truss(1) to tell what's wrong.
The commands would be:

# killall natd
# truss /sbin/natd -f /etc/natd.conf -n rl0




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311102321.44756.dgw>