Date: Sat, 19 Mar 2011 17:47:29 -0500 From: Gary Gatten <Ggatten@waddell.com> To: "'LConrad@Go2France.com'" <LConrad@Go2France.com>, "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: Re: tcp/ip failures with fbsd 8.2 386 on ESX 4.1 Message-ID: <22687_1300574850_4D853282_22687_4818_1_D9B37353831173459FDAA836D3B43499BD354B91@WADPMBXV0.waddell.com> In-Reply-To: <201103192340697.SM06140@W500.Go2France.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Maybe try disabling dns lookups within syslog-ng?
----- Original Message -----
From: Len Conrad [mailto:LConrad@Go2France.com]
Sent: Saturday, March 19, 2011 05:40 PM
To: freebsd-questions@freebsd.org <freebsd-questions@freebsd.org>
Subject: tcp/ip failures with fbsd 8.2 386 on ESX 4.1
FreeBSD 8.2 32-bit
ESXi 4.1
em0 driver to the ESXi Intel emulation
syslog-ng 2.0.10
em0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 =
mtu 1500
options=3D9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:50:56:90:00:01
inet a.b.c.85 netmask 0xffffffe0 broadcast a.b.c.95
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
We've be running FreeBSD 7.x for a couple of years on ESXi 4.0 and 4.1 with=
no problems.
We're having tcp/ip failures with 8.2 as syslog-ng server. trafshow shows =
aggregate port 514 traffic hitting peaks of about 25K char/sec.
After sometimes many hours of the syslog-ng VM server running well,=20
monit from other machines signals port 514 is down, up, down, up.
this is confirmed by other machines with
nmap a.b.c.d -p 514 -sU
... showing closed, open, closed, etc.
syslog-ng logging for all syslog clients stops more or less simultaneously.
trafshow filtered for port 514 shows udp packets arriving, but instead of s=
howing the source and destinations by PTR domain name, it switches to showi=
ng their IPs.
to test the external DNS, on the syslog-ng VM, we try
dig @recursive.server -x a.b.c.d
and get no response. Other machines query the recursive server successfull=
y.
Without rebooting the FreeBSD VM, we do
/etc/rc.d/netif restart
/etc/rc.d/routing restart
which allows full operation.
dmesg and messages show no errors.
Suggestions?
Len
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
<font size=3D"1">
<div style=3D'border:none;border-bottom:double windowtext 2.25pt;padding:0i=
n 0in 1.0pt 0in'>
</div>
"This email is intended to be reviewed by only the intended recipient
and may contain information that is privileged and/or confidential.
If you are not the intended recipient, you are hereby notified that
any review, use, dissemination, disclosure or copying of this email
and its attachments, if any, is strictly prohibited. If you have
received this email in error, please immediately notify the sender by
return email and delete this email from your system."
</font>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22687_1300574850_4D853282_22687_4818_1_D9B37353831173459FDAA836D3B43499BD354B91>