From owner-freebsd-questions@FreeBSD.ORG Wed Jun 15 17:27:24 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66D1416A421 for ; Wed, 15 Jun 2005 17:27:24 +0000 (GMT) (envelope-from greg@grokking.org) Received: from herbert.sohotech.ca (herbert.sohotech.ca [206.116.63.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3604F43D49 for ; Wed, 15 Jun 2005 17:27:23 +0000 (GMT) (envelope-from greg@grokking.org) Received: from localhost (unknown [127.0.0.1]) by herbert.sohotech.ca (Postfix) with ESMTP id 192E2180B2A for ; Wed, 15 Jun 2005 10:27:19 -0700 (PDT) Received: from herbert.sohotech.ca ([127.0.0.1]) by localhost (herbert.sohotech.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87932-05 for ; Wed, 15 Jun 2005 10:27:17 -0700 (PDT) Received: from [192.168.1.4] (niven.sohotech.ca [192.168.1.4]) by herbert.sohotech.ca (Postfix) with ESMTP id 7AFF2180992 for ; Wed, 15 Jun 2005 10:27:17 -0700 (PDT) Message-ID: <42B064F5.8020500@grokking.org> Date: Wed, 15 Jun 2005 10:27:17 -0700 From: Greg Maruszeczka User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20050615120621.S85701@neptune.atopia.net> In-Reply-To: <20050615120621.S85701@neptune.atopia.net> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at sohotech.ca Subject: Re: procmail keeps dieing on freebsd 5.4 with postfix 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: Wed, 15 Jun 2005 17:27:24 -0000 Matt Juszczak wrote: > Hi all, > > We had a mail server running with FreeBSD 5.4, about 3,000 accounts, and > postfix. Recently, I turned procmail on in postfix > (mailbox_command=/usr/....procmail) and the machine has been locking up > weekly ever since. And when this machines crashes, it crashes hard ... > and "procmail" is always on the screen as the error causer when it happens. > Patient: Doctor, my arm hurts when I do this. Doctor: Then stop doing that. Seriously though, you need to provide some more detailed information if you want anyone here to be able to help you. Start with explaining why you decided to change MDAs in the first place since I'm sure I'm not the only one thinking you must be nuts to make such a major change on a production system with a potential 3000-user lynch mob waiting in the wings. What were you using for local delivery before this? Was there a problem with it or were you looking for new features, etc.? > I know you all want messages, but I never seem to be here and my co > workers reboot the box on me to fix it. Both times; however, we've had > to run fsck from single user mode and also refresh the postfix queue. > If you're not around to see the console messages how do you know "procmail is always the error causer"? Perhaps this is conveyed to you by your co-workers but if so, why don't they tell you the complete error message so you can convey it to us? Leaving that aside, however, what about the logs? Certainly /var/log/maillog should provide some clues if the problem is really your MDA (more on this below). Also we'd need to know something about your configuration (i.e. contents of main.cf and master.cf for starters) to help you with a MTA/MDA problem. > Does anyone have any ideas why procmail could be causing my system to > completely hard lock every other couple of days? I disabled procmail > for now and I know (knock on wood) the machine should be fine like it > used to be ... but all these hard locks could eventually drive the > freebsd box mad, and I wouldn't want to do a reinstall. > FWIW this doesn't sound like a software issue (except maybe a massive memory leak(??)) but then again, I'm saying this with very little useful information provided by you. Have you done any basic hardware checks (e.g. memtest, case and cpu cooling, power supply integrity, etc.)? You've stated that these lock-ups occur every week at the beginning of your post then you say later it's every couple of days. Which is it? Also, please try to precisely define "locking up" and "crashes". It's unclear to me based on your description and the (possibly misleading) subject line what portions of the system are affected. Precision matters IMHO. Cheers, G