From owner-freebsd-ports@FreeBSD.ORG Thu Apr 26 16:17:26 2012 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D10E106566B; Thu, 26 Apr 2012 16:17:26 +0000 (UTC) (envelope-from dweimer@ORSCHELN.com) Received: from cluster-h.mailcontrol.com (cluster-h.mailcontrol.com [208.87.234.190]) by mx1.freebsd.org (Postfix) with ESMTP id B68278FC15; Thu, 26 Apr 2012 16:17:25 +0000 (UTC) Received: from rly33h.srv.mailcontrol.com (localhost.localdomain [127.0.0.1]) by rly33h.srv.mailcontrol.com (MailControl) with ESMTP id q3QGGIob019896; Thu, 26 Apr 2012 17:17:16 +0100 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by rly33h.srv.mailcontrol.com (MailControl) id q3QGGADO017314; Thu, 26 Apr 2012 17:16:11 +0100 Received: from proxy1.orscheln.com (proxy1.orscheln.com [216.106.0.236]) by rly33h-eth0.srv.mailcontrol.com (envelope-sender ) (MIMEDefang) with ESMTP id q3QGG9iL016728 (TLS bits=256 verify=NO); Thu, 26 Apr 2012 17:16:10 +0100 (BST) Received: from neuman.orscheln.oi.local (neuman.orscheln.com [10.20.10.160]) by proxy1.orscheln.com (8.14.5/8.14.5) with ESMTP id q3QGFdnq014031 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 26 Apr 2012 11:16:08 -0500 (CDT) (envelope-from dweimer@ORSCHELN.com) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 26 Apr 2012 11:15:33 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD Port: ntp-4.2.6p5 Thread-Index: Ac0jKqaTm9QH4UIyQXaUZdAcrApkAgAhHJaAAAVSLKA= References: Message from "Dean Weimer" of "Wed, 25 Apr 2012 09:54:28 CDT." <201204252130.q3PLUchS003768@slippy.cwsent.com> From: "Dean Weimer" To: "Cy Schubert" X-Scanned-By: MailControl 7.7.0.1 (www.mailcontrol.com) on 10.72.1.143 Cc: ports@FreeBSD.org, cy@FreeBSD.org Subject: RE: FreeBSD Port: ntp-4.2.6p5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2012 16:17:26 -0000 -----Original Message----- From: Dean Weimer=20 Sent: Thursday, April 26, 2012 8:37 AM To: 'Cy Schubert' Cc: cy@FreeBSD.org; ports@FreeBSD.org Subject: RE: FreeBSD Port: ntp-4.2.6p5 I have duplicated this problem on a second machine, both are running on identical physical hardware (Dell PowerEdge R310, purchased on same order), cannot duplicate it anywhere else. The version of Pearl had nothing to do with it, nor does it matter if openssl is selected during the build process. I have also discovered that the -d option isn't necessary, it will run fine just by using -n. I have worked around it for the time being by manually executing it use the daemon command to detach it from the terminal session. I have three other systems that are not experiencing the problem, first one is my test system where I test application updates first, its running in VMware workstation, one production system on older custom built hardware, and another on VMware ESX 4 server. The two PowerEdge servers are 4G memory and 4 core CPU. My other systems all had 2 cores/cpu emulation and 2G memory. So I modified the test system to match that in case that had anything to do with it. No dice, test system still worked fine. Oddly I wasn't having this problem prior to the opnessl-1.0.1_1 update coming out, and the recompile occurred via portmaster -r update to openssl. Removing openssl from the ntp options doesn't fix it; I find it hard to believe that the two servers suddenly have a memory issue at the same time, though they could very well have the same defect as they likely came out of the same lot of hardware. Here is the output of a sysctl -a from one of the systems. [...snip...] Further info, it's not actually syncing time when running in debug mode or with the -n on these systems. I created a package from one of the running systems and installed the package to the non-working systems no change, so it doesn't appear to be the compile process where the problem is originating. Thanks, Dean Weimer Network Administrator Orscheln Management Co