Sorry, this is way back in VAST 5.5.2, on a Windows box. That error message sure seems like a resource problem, but the machine seems healthy other than our headless service indicating the above or another error below. Is the problem just too many sockets in use, and is there any way to see the current socket usage other than by the likes of 'netstat -b', or what the maximum number of sockets is? [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters] contains no "TcpNumConnections" parameter.
The immediate problem is that on restarting our headless service after the above, is that we can't start an RMI naming service:
SstApplicationContext class>>#createRmiNamingServiceAt:
receiver = SstApplicationContext
arg1 = rmi://:1099
temp1 = SstLocalEndpoint(invalid,rmi://:1099)
temp2 = 'RMI Naming@rmi://:1099'
temp3 = SstInternalTransportError(EACCES (10013): Permission denied)
temp4 = rmi://:1099
Our usual advice worked - reboot the machine enough times and that latter problem will go away - though I forget the exact error we'd seen in the past when starting up an RMI naming service. But I just thought this might be related to the ENOBUFS which we never saw before.