[Samba] after 3.0.9 upgrade windows wants to sync home drive

greg greg at fqdn.com
Tue Nov 23 23:54:00 GMT 2004


Hi, 

This is more of a FYI than a request for help.  thanks.  8)
   
    I upgraded our 3.0.x servers to 3.0.9 due to bugs which we were 
running across.  This happened at about 7AM,  a few hours before anyone 
starts arriving at work.  The mornings are one of the most taxing times 
on our servers as everyone is loading profiles,  and they review what 
lastnights image / video rendering farm output looks like over the 
network, amongst other things.

    Late in the afternoon we started getting calls about windows wanting 
to sync the N drive,  (N is the users home dir on the linux server) from 
a few clients.   A quick look at the logs shows quite a few errors.  I 
rolled back to 3.0.8 and things seem to be to normal;  but it is night 
time and everyone has gone home. 

    There is no IP connectivity issues between the clients and machine.

greg

here is a bit of the log...


 [2004/11/23 18:31:00, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/11/23 18:31:00, 1] smbd/service.c:close_cnum(836)
  wk127 (10.0.1.127) closed connection to service profile
[2004/11/23 18:31:54, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/11/23 18:31:54, 1] smbd/service.c:close_cnum(836)
  wk82 (10.0.1.82) closed connection to service profile
[2004/11/23 18:33:55, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = No route to host
[2004/11/23 18:33:55, 1] smbd/service.c:close_cnum(836)
  wk27 (10.0.1.27) closed connection to service profile
[2004/11/23 18:34:18, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/11/23 18:34:18, 1] smbd/service.c:close_cnum(836)
  hutch (10.0.0.176) closed connection to service profile
[2004/11/23 18:39:08, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Transport endpoint is not connected
[2004/11/23 18:39:08, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2004/11/23 18:39:08, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection 
reset by peer
[2004/11/23 18:39:08, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2004/11/23 18:39:09, 1] smbd/service.c:make_connection_snum(648)
  wk42 (10.0.1.42) connect to service profile initially as user lchoi 
(uid=615, gid=100) (pid 7273)
[2004/11/23 18:40:15, 1] smbd/service.c:close_cnum(836)
  wk42 (10.0.1.42) closed connection to service profile
[2004/11/23 18:40:50, 1] smbd/service.c:make_connection_snum(648)
  wk90 (10.0.1.90) connect to service profile initially as user jonah 
(uid=627, gid=100) (pid 7288)
[2004/11/23 18:40:54, 1] smbd/service.c:make_connection_snum(648)
  wk04 (10.0.1.4) connect to service profile initially as user mikeg 
(uid=7013, gid=100) (pid 7289)
[2004/11/23 18:41:28, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = No route to host
[2004/11/23 18:41:28, 1] smbd/service.c:close_cnum(836)
  wk85 (10.0.1.85) closed connection to service profile
[2004/11/23 18:42:31, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Transport endpoint is not connected
[2004/11/23 18:42:31, 0] lib/util_sock.c:get_peer_addr(1000)
  getpeername failed. Error was Transport endpoint is not connected
[2004/11/23 18:42:31, 0] lib/util_sock.c:write_socket_data(430)
  write_socket_data: write failure. Error = Connection reset by peer
[2004/11/23 18:42:31, 0] lib/util_sock.c:write_socket(455)
  write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection 
reset by peer
[2004/11/23 18:42:31, 0] lib/util_sock.c:send_smb(647)
  Error writing 4 bytes to client. -1. (Connection reset by peer)


More information about the samba mailing list