[Samba] samba errors - "No buffer space available"

Ryan Novosielski novosirj at umdnj.edu
Fri May 12 15:45:33 GMT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

eric roseme wrote:
> Ryan Novosielski wrote:
>> Allen, Bill wrote:
>>
>>> I am new to Samba, having just taken over management of a HPUX system in
>>> a mainly Windows environment.  The system is running Samba 3.0.7.  I am
>>> getting the following errors, repeatedly, in my log.smbd.  What does it
>>> mean?  Is this actually a problem or normal chatter for Samba?  If it is
>>> a problem, what should I do to correct it?
>>>
>>>  
>>> [2006/05/03 07:41:38, 0] lib/util_sock.c:set_socket_options(202)
>>>   Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
>>> [2006/05/03 07:41:38, 0] lib/util_sock.c:set_socket_options(202)
>>>   Failed to set socket option TCP_NODELAY (Error Invalid argument)
>>> [2006/05/03 07:41:38, 0] lib/util_sock.c:get_peer_addr(1000)
>>>   getpeername failed. Error was Invalid argument
>>> [2006/05/03 07:41:39, 0] smbd/server.c:open_sockets_smbd(382)
>>>   open_sockets_smbd: accept: No buffer space available
>>>
>>>  Thanks for any help or advice,
>>>
>>> Bill
>>>
>>>  
>>>   
>>
>> When you find out, let me know. :) It's been that way for ages on my
>> system. The two socket option messages are related to header related
>> problems, if I'm not mistaken, but it's really not a big deal. Do you
>> have either of those defined in smb.conf?
>>
>> As far as the buffer thing... this concerned me for along time. I
>> can't remember whether this got any better or worse, but there's a lot
>> wrong with 3.0.7 on HP-UX. I would not run anything earlier than
>> 3.0.14 on an HP-UX system.
>>
> Are you running Opensource Samba or HP CIFS Server?  For HP CIFS, you
> should not see the socket option errors, but the buffer space log entry
> could be any number of things.  Ryan is correct - you should be up on
> 3.0.14 (HP CIFS Server A.02.02.01).

Eric,

How are you getting rid of the TCP_NODELAY message? I have this message
on my machines still, even though I'm using a configure script that was
adapted from the CIFS Server build, if I'm not mistaken. Are you
patching the source as well?

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - User Support Spec. III
 |$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFEZK2dmb+gadEcsb4RAq1fAJsEpXoYXxlivVJbHuwEieHNioaHBACfaLE6
qgHVwMaT0AnF8ysCgXUuPQE=
=p1V2
-----END PGP SIGNATURE-----



More information about the samba mailing list