From owner-freebsd-stable@FreeBSD.ORG Wed Nov 26 06:16:46 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F8C516A4CE for ; Wed, 26 Nov 2003 06:16:46 -0800 (PST) Received: from unix18.sihope.com (unix18.sihope.com [207.195.195.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B97A43FCB for ; Wed, 26 Nov 2003 06:16:44 -0800 (PST) (envelope-from adam@whee.org) Received: from adammxp (pc6.sihope.com [207.195.195.65]) by unix18.sihope.com (8.12.9p2/8.12.9) with SMTP id hAQEGhKT006147 for ; Wed, 26 Nov 2003 08:16:43 -0600 (CST) (envelope-from adam@whee.org) Message-ID: <004f01c3b427$eaea8c70$41c3c3cf@office.sihope.com> From: "Adam Maloney" To: Date: Wed, 26 Nov 2003 08:16:43 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: NFS/Sendmail issue since upgrading to 4.9-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2003 14:16:46 -0000 Hi all, I have 3 servers accepting mail, with sendmail in Queue-only mode dropping mail into an NFS queue (mounted from a 4th machine.) All 4 machines involved are running FreeBSD. I upgraded the 3 NFS clients from 4.8 to 4.9-STABLE on Monday, and started seeing this sendmail message: Nov 26 06:51:29 unix20 sm-mta[48069]: (real-message-id): SYSERR(root): queueup: cannot create queue file ./qf(real-message-id), euid=0: Resource temporarily unavailable The df(message-id) file is created and appears to be complete, however the qf file is 0 bytes. This happens sporadically, a few times a day on each machine (together doing about 150,000 messages/day). I upgraded the NFS server from 4.8 to 4.9 yesterday, thinking that might help, but the problem is still there. Any ideas how to troubleshoot this one?