From owner-freebsd-questions@FreeBSD.ORG Sat Mar 19 22:47:31 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A3AD106566C for ; Sat, 19 Mar 2011 22:47:31 +0000 (UTC) (envelope-from Ggatten@waddell.com) Received: from mailhost0.waddell.com (mailhost0.waddell.com [67.130.252.61]) by mx1.freebsd.org (Postfix) with ESMTP id EEBFC8FC17 for ; Sat, 19 Mar 2011 22:47:30 +0000 (UTC) Received: from mailhost3.waddell.com (mailhost3.waddell.com [10.1.10.28]) by mailhost0.waddell.com (Postfix) with ESMTP id 9512D5087C; Sat, 19 Mar 2011 17:47:30 -0500 (CDT) Received: from mailhost3.waddell.com (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 90D1B3C32F; Sat, 19 Mar 2011 17:47:30 -0500 (CDT) Received: from WADPHTCAS0.waddell.com (wadphtcas0.waddell.com [192.168.203.229]) by mailhost3.waddell.com (Postfix) with ESMTP id 86CA63C32D; Sat, 19 Mar 2011 17:47:30 -0500 (CDT) Received: from WADPMBXV0.waddell.com ([169.254.1.145]) by WADPHTCAS0.waddell.com ([192.168.203.229]) with mapi; Sat, 19 Mar 2011 17:47:30 -0500 From: Gary Gatten To: "'LConrad@Go2France.com'" , "'freebsd-questions@freebsd.org'" Date: Sat, 19 Mar 2011 17:47:29 -0500 Thread-Topic: tcp/ip failures with fbsd 8.2 386 on ESX 4.1 Thread-Index: Acvmhr1/XhnHiILUSMOwNOGlJK7S2QAAOLGz Message-ID: <22687_1300574850_4D853282_22687_4818_1_D9B37353831173459FDAA836D3B43499BD354B91@WADPMBXV0.waddell.com> In-Reply-To: <201103192340697.SM06140@W500.Go2France.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: Re: tcp/ip failures with fbsd 8.2 386 on ESX 4.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2011 22:47:31 -0000 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 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 metric 0 = mtu 1500 options=3D9b ether 00:50:56:90:00:01 inet a.b.c.85 netmask 0xffffffe0 broadcast a.b.c.95 media: Ethernet autoselect (1000baseT ) 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"
"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."