Re: socketpair: No buffer space available
On Fri, 23 Mar 2007, Marc G. Fournier wrote: I've checked nmbclusters between the two machines, and both are at 25600, but not sure what sysctl to look at for how much is actually used out of that 25600 ... netstat -mb nmbclusters directly affects the number of clusters available in the network stack; it also indirectly affects the scaling of other settings, such as resource limits on the number of sockets. vmstat -z is also generally useful. There are a few paths to ENOBUFS in the socket allocation code--one path is if you are over-committed on socket buffer resources with respect to the resource limits of the user. Check the output of limits and the socket buffer size limit. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: socketpair: No buffer space available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thanks ... just rebooted it yesterday again, so it has another 48 hours before it starts up again, so will save that output before next reboot ... - --On Tuesday, March 27, 2007 21:03:55 +0100 Robert Watson [EMAIL PROTECTED] wrote: On Fri, 23 Mar 2007, Marc G. Fournier wrote: I've checked nmbclusters between the two machines, and both are at 25600, but not sure what sysctl to look at for how much is actually used out of that 25600 ... netstat -mb nmbclusters directly affects the number of clusters available in the network stack; it also indirectly affects the scaling of other settings, such as resource limits on the number of sockets. vmstat -z is also generally useful. There are a few paths to ENOBUFS in the socket allocation code--one path is if you are over-committed on socket buffer resources with respect to the resource limits of the user. Check the output of limits and the socket buffer size limit. Robert N M Watson Computer Laboratory University of Cambridge - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCYJ24QvfyHIvDvMRAlPjAJ9zbGNDlGxTO/TFuoAQAw2zUsmj/wCgmPlG 9yyzoZWGu3B55xoAZ0iLjhg= =8QWr -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: socketpair: No buffer space available
Marc G. Fournier wrote: Mar 20 07:59:26 mars sshd[717]: error: reexec socketpair: No buffer space available If I have a login session on the machine, I can easily do a reboot of the machine, and it seems to come up clean every time (ie. no fsck's need to be run) ... Does anyone have any ideas of what I can look at? How odd. The re-exec feature is not documented in the man page. It appears that it can be turned off with the -r switch according to sshd.c. Can you give that a try and see if that offers symptomatic relief? It would be somewhat less secure as sshd will fork rather than fork..exec. The code does indeed appear to use socketpair. FreeBSD implements socketpair as a system call. Only AF_UNIX, SOCK_STREAM sockets are accepted. A quick look in KScope suggests the first place where this can fail with ENOBUFS is soalloc() from socreate(). Is this machine under heavy memory load in any way? soalloc() uses a zone allocator. I'm not sure how to track that from userland, vmstat -m only deals with kernel malloc() stats. BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: socketpair: No buffer space available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Monday, March 26, 2007 00:08:07 +0100 Bruce M. Simpson [EMAIL PROTECTED] wrote: Marc G. Fournier wrote: Mar 20 07:59:26 mars sshd[717]: error: reexec socketpair: No buffer space available If I have a login session on the machine, I can easily do a reboot of the machine, and it seems to come up clean every time (ie. no fsck's need to be run) ... Does anyone have any ideas of what I can look at? How odd. The re-exec feature is not documented in the man page. It appears that it can be turned off with the -r switch according to sshd.c. Can you give that a try and see if that offers symptomatic relief? It would be somewhat less secure as sshd will fork rather than fork..exec. That was actually just one example ... I get more of: sendmail[82066]: l2NEA1Ht082066: SYSERR(root): makeconnection: cannot create socket: No buffer space available then I do the sshd errors ... in another 15 hours or so, they will all start up again, like clock work :( - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGBxZ84QvfyHIvDvMRAoNTAKDBkGZL7aCOXEW22QibCCpnJJJnEgCfafMa ex0pM7sKPgCjVdURJ9nwfH0= =egaO -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
