samba - Jun 2006 - 3.0.22 on solaris10 socket error.

Hi all,

I've built samba 3.0.22 on solaris10 sparc with ldap support using thes
config parameters :
./configure --prefix=/opt/samba \
--localstatedir=/var/lib/samba \
--enable-socket-wrapper \
--disable-cups \
--with-privatedir=/etc/samba/private \
--with-piddir=/var/run \
--with-configdir=/etc/samba \
--with-logfilebase=/var/log/samba \
--with-ldap \
--with-ads=no \
--with-automount \
--with-ldapsam \
--with-acl-support \
--with-included-popt

When I start samba deamons, everything seems to work.
But when I connect to a share on solaris 10 from a windows client, I see
the message in log.smb file (log level 0) :

[2006/06/09 18:52:08, 0] lib/util_sock.c:set_socket_options(261)
  Failed to set socket option SO_KEEPALIVE (Error Invalid argument)

What does it means ?
I've tried to unset all socket options parameters, but i receive the
same message.

In the config.log generated by configure, socket.h from solaris includes
is found and used.
And if I run samba whith log level 3, I see these messages in log.smb :

[2006/06/09 18:55:48, 0] lib/util_sock.c:get_peer_addr(1225)
  getpeername failed. Error was Invalid argument
[2006/06/09 18:55:48, 0] lib/util_sock.c:set_socket_options(261)
  Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option SO_KEEPALIVE = 8
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option SO_REUSEADDR = 4
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option SO_BROADCAST = 0
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option TCP_NODELAY = 0
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option IPTOS_LOWDELAY = 0
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option IPTOS_THROUGHPUT = 0
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option SO_SNDBUF = 49152
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)
  socket option SO_RCVBUF = 49152
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(204)
  Could not test socket option SO_SNDLOWAT.
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(204)
  Could not test socket option SO_RCVLOWAT.
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(204)
  Could not test socket option SO_SNDTIMEO.
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(204)
  Could not test socket option SO_RCVTIMEO.
[2006/06/09 18:55:48, 5] lib/util_sock.c:print_socket_options(206)

What's wrong ?
Thanks for your help.

-- 
Pierre MARC

Hi !!


I have already sent this message to the list, but, as I have not received
any replies, I am trying again !!


I have Samba 3.0.22 running as PDC on solaris10.

Each time a windows client (XP SP2 or W2003) opens an explorer to access
a share, I see in the log.smbd :

[2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225)
  getpeername failed. Error was Invalid argument
[2006/06/15 01:28:08, 0] lib/util_sock.c:set_socket_options(261)
  Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2006/06/15 01:28:08, 0] lib/util_sock.c:set_socket_options(261)
  Failed to set socket option TCP_NODELAY (Error Invalid argument)
[2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225)
  getpeername failed. Error was Invalid argument

And in same time in the log.%R :

[2006/06/15 01:28:08, 0] lib/util_sock.c:write_data(557)
  write_data: write failure in writing to client 192.168.202.5. Error
Broken pipe
[2006/06/15 01:28:08, 0] lib/util_sock.c:send_smb(765)
  Error writing 4 bytes to client. -1. (Broken pipe)

And it seems the windows explorer freezes in the same time, with
sometime an mrxsmb event message.

I've seen that the getpeername message is not a problem. OK for that.

But I haven't seen any answer about the set socket option (Error invalid
argument).
What does it means ?
Is it a real problem ?
Is it particular to solaris ?
I have found similar questions in the samba list, since Jan-2005, but
... no answer.

Please, help !


-- 
Pierre MARC <pierre.marc@id3.eu>
id3 Semiconductors