Re: syslogd not draining
- From: "Michael W. Lucas" <mwlucas@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Mar 2006 12:08:02 -0500
On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote:
I've got a machine running syslogd, DNS, DHCP, flow-capture, and other
assorted UDP-loving programs. Occasionally, they all stop working.
The machine has been up for a couple of hours now, and I see:
ns1/etc;netstat -s | grep full
Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory
122066 dropped due to full socket buffers
ns1/etc;
I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it
still happens.
After some help from questions@, I'm pretty sure that the culprit is
syslogd.
udp4 0 0 *.67 *.*
udp4 43414 0 *.514 *.*
udp4 0 0 *.49661 *.*
Are you using a serial console? I had similar problems in the past
due to the serial port flow control.
Yes, I am.
So, if I disable syslogd writing to the console, it might clear this up?
Thanks,
==ml
--
Michael W. Lucas mwlucas@xxxxxxxxxxx, mwlucas@xxxxxxxxxxxxxxxxxxxx
http://www.BlackHelicopters.org/~mwlucas/
"The cloak of anonymity protects me from the nuisance of caring." -Non Sequitur
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- References:
- syslogd not draining
- From: Michael W. Lucas
- Re: syslogd not draining
- From: Borja Marcos
- syslogd not draining
- Prev by Date: Re: Programs not accepting input?
- Next by Date: Re: syslogd not draining
- Previous by thread: Re: syslogd not draining
- Next by thread: Re: syslogd not draining
- Index(es):