From owner-freebsd-isp@FreeBSD.ORG Thu Feb 15 23:09:17 2007 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8F3C16A400 for ; Thu, 15 Feb 2007 23:09:17 +0000 (UTC) (envelope-from duane@dwlabs.ca) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.freebsd.org (Postfix) with ESMTP id 7129713C4A5 for ; Thu, 15 Feb 2007 23:09:17 +0000 (UTC) (envelope-from duane@dwlabs.ca) Received: from ip03.eastlink.ca ([24.222.10.15]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JDJ00J0I1NFVWE0@mta01.eastlink.ca> for freebsd-isp@freebsd.org; Thu, 15 Feb 2007 19:09:15 -0400 (AST) Received: from blk-224-199-230.eastlink.ca (HELO dwpc.dwlabs.ca) ([24.224.199.230]) by ip03.eastlink.ca with ESMTP; Thu, 15 Feb 2007 19:09:16 -0400 Received: from dwpc.dwlabs.ca (mail.dwlabs.ca [192.168.0.10]) by dwpc.dwlabs.ca (8.13.8/8.13.8) with ESMTP id l1FN7Okv028395; Thu, 15 Feb 2007 19:07:30 -0400 (AST envelope-from duane@dwpc.dwlabs.ca) Received: (from duane@localhost) by dwpc.dwlabs.ca (8.13.8/8.13.8/Submit) id l1FN7Nhq028394; Thu, 15 Feb 2007 19:07:23 -0400 (AST envelope-from duane) Date: Thu, 15 Feb 2007 19:07:22 -0400 From: Duane Whitty In-reply-to: <001701c75133$e1cb0870$dd64000a@transnet.cu> To: Roldan Vallejo Olivera Message-id: <20070215230722.GA27427@dwpc.dwlabs.ca> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CANt21EUY4MfmdGdsb2JhbACiEgEBAQ X-IronPort-AV: i="4.14,178,1170648000"; d="scan'208"; a="414978595:sNHT25526634" X-Virus-Scanned: ClamAV 0.88.6/2573/Thu Feb 15 07:37:08 2007 on dwpc.dwlabs.ca X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on dwpc.dwlabs.ca References: <001701c75133$e1cb0870$dd64000a@transnet.cu> User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00, UNPARSEABLE_RELAY autolearn=ham version=3.1.4 Cc: freebsd-isp@freebsd.org Subject: Re: problems with KAV for FreeBSD 6.0 X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duane@dwlabs.ca List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 23:09:17 -0000 On Thu, Feb 15, 2007 at 02:02:47PM -0500, Roldan Vallejo Olivera wrote: > hello list: > I have a FreeBSD 6.0 running in an HP Proliant GL 370, Dual Xeon 3.2 GHz, > 1GB RAM, and RAID-5 75 GB, in this system we have a BIND DNS service and a > Sendmail as a mail relay-only server, processing an average of 3GB messages > daily, we have purchased a KAV license for 4 GB traffic daily, but we are > having problems: sometimes our server runs out of resources and issues the > following message error: > "maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5) > ns1 sendmail[545] syserr (root): openmailer > (smtpscanner): cannot fork: resource temporarily unavailable no queue: > syserr(root): daemon: cannot fork" > > at this moment when I try to login at the server i receive this error: > "login: login: fork: resource temporarily unavailable" > > the server replies at ping command, but doesn't allow telnet neither ssh, > and stops processing messages. we have noticed this scenario runs out of > free memory as we read the output of top command: > > "last pid: 26888; load averages: 1.02, 0.91, 0.54 up 3+19:06:18 > 03:10:00 > 615 processes: 4 starting, 2 running, 608 sleeping, 1 lock > > Mem: 698M Active, 58M Inact, 188M Wired, 48M Cache, 111M Buf, 3532K Free > Swap: 4096M Total, 24M Used, 4071M Free" > Free memory seems adequate here. You have very little swap space used. FreeBSD uses the philosophy that free memory is wasted memory. > As soon as I reboot the system everything works fine for the next 3 or 4 > days... I don't know what's exactly the problem and of course, I have no > idea of the solution, can anybody help me, please? > thanks in advance > roldan > What does sysctl kern.maxusers show? Depending on what the current value of this is you may want to increase it. Below is my current value for kern.maxusers dwpc@ /etc>sysctl kern.maxusers kern.maxusers: 250 kern.maxusers sets many kernel parameters and does not actually specify the number of users which can use the system. This and other tuning options can be found in tuning(7). --Duane