Ongoing Socket problems.

[Tristan Ball]

We are currently running Samba 2.2.1a, on solaris 2.8, and like a few
others, I'm seeing some socket errors in the logs, and some serious
problems with W2K clients.

Neither error is particularly new, and I saw similar socket errors with
Samba 2.0.x (I won't say exact because I didn't save the logs). The
socket errors don't appear to have been causing a problem. However we
are rolling out W2K, and I'm seeing some rather strange errors,
essentially users can't access network shares.

Some more details on our config:
Password = server
NT acls = off
Oplocks, Level 2 oplocks = off (we've had some real trouble with these!)

I checked our PDC (NT4, SP6a) today, and it was complaining of being out
of licenses (it's only PDC, no file shares). I had it configured with
1000 CAL's, and we have 400 users. I changed the server license to per
seat, and I haven't seen any more complaints on the PDC, but I'm still
seeing W2K problems.

User on PC is logged in, drives are mapped, everybodies happy.
User logs out, logs in (or reboots). The user can no longer access
network drives. Commented logs are below

[user logs out]

[2001/08/01 10:14:05, 1] smbd/service.c:close_cnum(646)
  rotten (172.22.2.36) closed connection to service MONITOR

[login here - login script maps samba shares]

[2001/08/01 10:16:23, 0] lib/util_sock.c:read_socket_with_timeout(300)
  read_socket_with_timeout: timeout read. read error = Connection reset
by peer.
[2001/08/01 10:16:23, 0] lib/util_sock.c:write_socket_data(541)
  write_socket_data: write failure. Error = Broken pipe
[2001/08/01 10:16:23, 0] lib/util_sock.c:write_socket(565)
  write_socket: Error writing 166 bytes to socket 20: ERRNO = Broken
pipe
[2001/08/01 10:16:26, 1]
libsmb/cliconnect.c:cli_establish_connection(754)
  failed session setup
[2001/08/01 10:16:26, 0] libsmb/clientgen.c:cli_send_smb(89)
  Error writing 166 bytes to client. -1

[this next one worries me, there is a double space between server and
rejected, implying to me
 there should be a server name in there!]

[2001/08/01 10:16:46, 1] smbd/password.c:server_validate(1236)
  password server  rejected the password
[2001/08/01 10:16:46, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)

[These others I'm not worried by, there is no smbpasswd]

  startsmbfilepwent_internal: unable to open file
/opt/local/apps/samba-2.2.1a/private/smbpasswd. Error was No such file
or directory
[2001/08/01 10:16:46, 0] passdb/smbpass.c:iterate_getsmbpwnam(1282)
  unable to open smb password database.
[2001/08/01 10:16:46, 1] smbd/password.c:pass_check_smb(554)
  Couldn't find user 'rlm' in smb_passwd file.
[2001/08/01 10:16:46, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)

  startsmbfilepwent_internal: unable to open file
/opt/local/apps/samba-2.2.1a/private/smbpasswd. Error was No such file
or directory
[2001/08/01 10:16:46, 0] passdb/smbpass.c:iterate_getsmbpwnam(1282)
  unable to open smb password database.
[2001/08/01 10:16:46, 1] smbd/password.c:pass_check_smb(554)
  Couldn't find user 'rlm' in smb_passwd file.


The socket errors we have been recieving, which don't appear to affect
anything, look like:

[2001/07/31 13:05:51, 0] lib/util_sock.c:write_socket_data(541)
  write_socket_data: write failure. Error = Broken pipe
[2001/07/31 13:11:07, 0] lib/util_sock.c:write_socket_data(541)
  write_socket_data: write failure. Error = Broken pipe
[2001/07/31 13:16:29, 0] lib/util_sock.c:write_socket_data(541)
  write_socket_data: write failure. Error = Broken pipe

541 is the errno as returned from send(), but I can't find any usefull
info on what 541 is, (it's not listed in errno.h)


I am willing to do whatever I can to help diagnose this...

T.

--
-=*=-=*=--=*=-=*=-=*=-
Tristan Ball
System Administrator
Vision Systems
ph 61 3 9211 7064
-=*=-=*=--=*=-=*=-=*=-

A legal disclaimer for this message can be found at
http://www.vsl.com.au/disclaimer.html, or by request.