Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 May 2001 16:20:48 -0400
From:      Nathan Vidican <webmaster@wmptl.com>
To:        questions@freebsd.org
Subject:   sm.statd overflow attempt kills named
Message-ID:  <3AF703A0.F186C453@wmptl.com>

next in thread | raw e-mail | index | archive | help
The sm.statd overflow attempt, which is reportedly a bug that effects
only Linux machines is apparently killing off named. For some reason I
keep having named quit on me, and no errors whatsoever are reported on
the console or otherwise with the exception of an attempt to create what
I believe is a buffer overflow using statd. I was told easlier not to
worry about said errors as they would have no effect on a FreeBSD box;
being sceptical I got a bit experimental with it. 
	I still do not know who is attempting these overflows, or why...
frankly I really don't care. I have recompiled the kernels of most of
the production machines, and included a local firewall to disallow such
attempts. However, two machines which I have not yet setup a firewall on
(ironically both happen to be the network DNS servers), keep closing off
named. I get no errors, and co complaints from named, not even a
quitting string in /var/log/messages. No core dumps, no performance
problems on said machines (other than the obvious happening with no
local DNS); yet named just stops. Up until most recently it has not been
an issue; I've been setting the machines up still, and occashionally
rebooting (thereby restarting named anyhow). Now I'm almost done, and
I'm basically ready to put these machines into service. I will be
running a local firewall on each of these machines as well, (currently
running, just wide-open 'pass all from any to any via any'), so I
anticipate the problem will no longer exist. 
	The reason I'm writting, is basically out of curiosity; how does the
sm.statd overflow error effect DNS services? Is there even a co-relation
between the two, (or am I soon to find out I just have an un-related
problem with named) ? Any ideas why this happens... or how one would be
able to stop it (assuming I didn't put a firewall in place, which will
happen out of practise anyhow)?

Nathan Vidican
Nathan@Vidican.com
http://Nathan.Vidican.com/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




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