Date: Tue, 20 Feb 2001 09:28:31 -0800 From: "Renaud Waldura" <renaud@waldura.org> To: <freebsd-hackers@freebsd.org>, "Len Conrad" <LConrad@Go2France.com> Subject: Re: postfix: No buffer space available Message-ID: <005501c09b62$8bd9c920$3902010a@zerog.int> References: <5.0.0.25.0.20010220140218.02df9c10@mail.Go2France.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <LConrad@Go2France.com> To: <freebsd-hackers@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005501c09b62$8bd9c920$3902010a>