From owner-freebsd-hackers Tue Feb 20 9:28:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ebola.biohz.net (ebola.biohz.net [206.80.1.35]) by hub.freebsd.org (Postfix) with ESMTP id ACC8237B65D for ; Tue, 20 Feb 2001 09:28:33 -0800 (PST) (envelope-from renaud@waldura.org) Received: from renaud (localhost [127.0.0.1]) by ebola.biohz.net (Postfix) with SMTP id 01B4A3A4D8; Tue, 20 Feb 2001 09:28:32 -0800 (PST) Message-ID: <005501c09b62$8bd9c920$3902010a@zerog.int> From: "Renaud Waldura" To: , "Len Conrad" References: <5.0.0.25.0.20010220140218.02df9c10@mail.Go2France.com> Subject: Re: postfix: No buffer space available Date: Tue, 20 Feb 2001 09:28:31 -0800 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you tried playing with: kern.ipc.maxsockbuf: 262144 kern.ipc.sockbuf_waste_factor: 8 kern.ipc.maxsockets: 4136 The first one looks particularly interesting. --Renaud ----- Original Message ----- From: "Len Conrad" To: Sent: Tuesday, February 20, 2001 6:28 AM Subject: postfix: No buffer space available > Sorry to bother you hackers again, but two submissions to -questions > got no response so it looks like another scaleability issue on you > people can handle : > > ================ > > On a very busy postfix relay hub, we're seeing this: > > Feb 19 15:00:16 imgate2 postfix/smtpd[323]: fatal: socket: No buffer > space available > > Feb 19 15:00:17 imgate2 postfix/smtp[684]: fatal: socket: No buffer > space available > > Can we fix this with a systcl write? > > The server already has: > > # sysctl -a | grep maxfile > kern.maxfiles: 16384 > kern.maxfilesperproc: 16384 > > ... which fixed "fatal: too many files open" pb for this client last > November. > > btw, Wietse Venema himself asked me to be informed of how I manage to > tweak FreeBSD to handle this apparent scaleability issue. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message