ADSM-L

Re: errors

1998-05-29 12:13:12
Subject: Re: errors
From: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Fri, 29 May 1998 12:13:12 -0400
The errno=74 means "ENOBUFS - No buffer space available" (this is from the
errno.h file for your operating system). This usually happens when you've
specified a TCPWINDOWSIZE setting that is larger than your TCP/IP configuration
is set up to handle. On AIX you need to check the sb_max value (on AIX use the
command "no -a" to determine the current sb_max). sb_max is expressed in bytes,
so if you divide by 1,024, that will tell you the maximum setting you can use
for TCPWINDOWSIZE. For example, if sb_max is 65,536, then the maximum
TCPWINDOWSIZE value you can use is 64.

Try lowering TCPWINDOWSIZE so that it is less than or equal to sb_max, and the
messages should go away. Alternatively you can increase sb_max. IMPORTANT NOTE:
sb_max is a system-wide TCP/IP setting. You should be familiar with tuning
TCP/IP (or get help from someone who knows how to tune TCP/IP) before changing
sb_max or any other system-wide TCP/IP settings.

Andy




Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 05/29/98 08:31:36 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: errors


Does anyone knows what these erros mean?

05/29/1998 09:24:32 commtcp.c ( 901): TcpOpen(): setsockopt(SO_SNDBUF): errno =
74
05/29/1998 09:24:32 commtcp.c ( 912): TcpOpen(): setsockopt(SO_RCVBUF): errno =
74
05/29/1998 09:24:32 commtcp.c ( 945): TcpOpen(): setsockopt failed on one or
more options

Thanks,

*********************************
  CARLOS E. SILESKY JIMENEZ
         PH:(505) 277-7343
    EMAIL: silesky AT unm DOT edu
  <----------------------->
*********************************



<Prev in Thread] Current Thread [Next in Thread>