From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 11:41:58 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 753931065686 for ; Wed, 1 Oct 2008 11:41:58 +0000 (UTC) (envelope-from sclark46@earthlink.net) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by mx1.freebsd.org (Postfix) with ESMTP id 457958FC0A for ; Wed, 1 Oct 2008 11:41:58 +0000 (UTC) (envelope-from sclark46@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=WCoYbJbAJmQ/tWvufAkLa8WGNT4GNetYOe6fT4mGb/QXGEmWtkS6HjO+jH/08VIm; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [208.118.36.229] (helo=joker.seclark.com) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1Kl05d-0004Gl-GS for freebsd-stable@freebsd.org; Wed, 01 Oct 2008 07:41:57 -0400 Message-ID: <48E36204.5090108@earthlink.net> Date: Wed, 01 Oct 2008 07:41:56 -0400 From: Stephen Clark User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec796d0107e56c3ce7d14698431cbb638458350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 208.118.36.229 Subject: resource leak X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sclark46@earthlink.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2008 11:41:58 -0000 Hello List, I am running into a strange problem that points to a resource leak. The problem manifests itself after one of our remote systems has been up around 100 days. The symptom is that it appears no new processes can be spawned. If I try to ssh to the unit, I can see the 3-way tcp handshake and then no more traffic. Examining log files, like cron, etc show that when this happens no more entries are written into the cron log. The unit is acting as a firewall, router and vpn appliance these functions continue to work. We have a C application that is periodically started out of a shell script that reports various information about the system, it stops reporting, while vpns, ospf routing, and ipfilter firewalling continue to work and write into their logfiles. My question is how do I monitor the various resources in the system that could prevent the spawning of a new process? This is on FreeBSD 6.1, ipsec-tools-6.6, quagga-0.99.3 Any ideas or directions would be greatly appreciated. Thanks, Steve