Date: Wed, 08 Nov 2000 22:32:55 +0100 From: Len Conrad <lconrad@Go2France.com> To: freebsd-hackers@freebsd.org Cc: Ian Dowse <iedowse@maths.tcd.ie> Subject: Re: post-install of kernal sources, maxusers max? Message-ID: <5.0.0.25.0.20001108222155.0252ceb0@mail.Go2France.com> In-Reply-To: <200011082116.aa66725@salmon.maths.tcd.ie> References: <Your message of "Wed, 08 Nov 2000 21:29:03 %2B0100." <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>In message <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com>,=20
>Len Conrad
>writes:
>
> >All I need to change, I think, is maxusers since we're getting this
> >error from postfix:
>
>You may be able to increase these limits without recompiling the
>kernel, by using kernel environment variables set in /boot/loader.rc.
>
>First of all you need to find out exactly what resource is getting
>exhausted. I suspect it is the socket space memory zone, but you can
>verify this with the commands:
>
> vmstat -z |grep ^socket
# vmstat -z
ZONE used total mem-use
PIPE 36 102 5/15K
SWAPMETA 8 50 1/7K
tcpcb 179 350 95/185K
unpcb 418 896 26/56K
ripcb 0 42 0/7K
tcpcb 0 0 0/0K
udpcb 10 168 1/31K
socket 607 1050 113/196K
KNOTE 6 256 0/16K
NFSNODE 0 0 0/0K
NFSMOUNT 0 0 0/0K
VNODE 4006 4028 751/755K
NAMEI 0 40 0/40K
VMSPACE 260 384 48/72K
PROC 264 343 107/139K
DP fakepg 0 0 0/0K
PV ENTRY 53272 79979 1456/2186K
MAP ENTRY 3117 3953 146/185K
KMAP ENTRY 804 978 37/45K
MAP 7 10 0/1K
VM OBJECT 4907 5464 460/512K
------------------------------------------
TOTAL 3252/4455K
Do you see anything else up there that looks bad or =FCber limit?
> sysctl kern.ipc.maxsockets
# sysctl kern.ipc.maxsockets
kern.ipc.maxsockets: 1064
>If the 'max' column in the vmstat output matches the number returned
>by sysctl, then the kernel has hit this limit at some stage.
doesn't look like it to me.
>To increase the limit, pick a new larger value, and add a line to
>/boot/loader.rc e.g.
>
> set kern.ipc.maxsockets=3D5000
>
>You will need to reboot for this setting to take effect, and it is not
>possible to dynamically increase the limit in a running kernel.
>
>Other settings worth investigating are nmbclusters and nmbufs. These
>are viewable via 'netstat -m', and can be set as above.
# netstat -m
358/960/4096 mbufs in use (current/peak/max):
198 mbufs allocated to data
160 mbufs allocated to packet headers
185/504/1024 mbuf clusters in use (current/peak/max)
1248 Kbytes allocated to network (36% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
So what do you think postfix is complaining about, more precisely,=20
how to fix it:
Fatal Errors (postfix)
------------
bounce
1 socket: No buffer space available
qmgr
7 socket: No buffer space available
script
1 usage: postfix start (or stop, reload, abort, flush, or check)
smtp
5 socket: No buffer space available
3 inet_addr_local: socket: No buffer space available
smtpd
6 socket: No buffer space available
Thanks,
Len
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?5.0.0.25.0.20001108222155.0252ceb0>