Skip site navigation (1)Skip section navigation (2)
Date:      24 Nov 2002 02:25:31 +0000
From:      Stacey Roberts <stacey@vickiandstacey.com>
To:        David Smithson <david@customfilmeffects.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: Network connection dropping during file transfers
Message-ID:  <1038104729.43256.96.camel@localhost>
In-Reply-To: <00fa01c2935a$e4565cc0$0801a8c0@customfilmeffects.com>
References:  <007101c2934a$8bad2b40$0801a8c0@customfilmeffects.com> <00a101c2934d$bfb43b60$0801a8c0@customfilmeffects.com> <1038097743.43256.45.camel@localhost> <00bf01c29351$c649baf0$0801a8c0@customfilmeffects.com> <00dd01c29354$e40c4320$0801a8c0@customfilmeffects.com> <1038100610.43256.56.camel@localhost> <00fa01c2935a$e4565cc0$0801a8c0@customfilmeffects.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi David,
   Just got to this one here.

On Sun, 2002-11-24 at 01:43, David Smithson wrote:
> Hi Stacey.
> 
> > See how this affects your situation. I recall that this was (might still
> > be) an issue with samba and windows machines using heavy load transfers.
> > I think on Win9x this appeared as "Network Busy" errors, but what do you
> > see in the Event Logs on Win2K?
> 
> The event logs show nothing significant.

I'd have to ask for some specifics here - If you mean nothing related
the problem domain, then I apologize. But one thing Win2K does a lot of
is reports, so please have another look:-)

> The render manager for the aformentioned Digital Fusion shows:
> 
> The semaphore timeout period has expired

The lock on some atomic process has gone past the specified period for
which it is able to hold a lock - results in dropped connections (for
network code)

> The network name is no longer available

The app is has now seen that its previously cache network resource is no
longer there.

> The network path was not found

The app realises that it is unable to locate the network resources.

This all (granted from fuzzy Win2K reporting) that from a loss of
connectivity has occured. The trick is if its hardware / media related,
or DNS timeout related.

Have you got tcpdump facilities? Might be an idea to get a trace on
this. A simple (visual) way could also be to install ethereal / trafshow
on the FBSD box and watch packet exxchanges during transfers.

Stacey
> >
> > Stacey
> >
> > On Sun, 2002-11-24 at 01:00, David Smithson wrote:
> > > Perhaps I should include more of the smbd.log file.  It follows:
> > >
> > > [2002/11/22 06:53:49, 5] smbd/oplock.c:process_local_message(362)
> > >   process_local_message: (exclusive) oplock break request from pid
> 11761,
> > > port 1601, dev = 2930c, inode = 12625652
> > > [2002/11/22 06:53:49, 3] smbd/oplock.c:process_local_message(418)
> > >   process_local_message: oplock break requested with no outstanding
> oplocks.
> > > Returning success.
> > > [2002/11/22 06:53:49, 5] smbd/oplock.c:process_local_message(447)
> > >   process_local_message: oplock break reply sent to pid 11761, port
> 1601,
> > > for file dev = 2930c, inode = 12625652
> > > [2002/11/22 06:53:49, 3] smbd/server.c:exit_server(493)
> > >   Server exit (caught signal)
> > > [2002/11/22 07:00:33, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:00:35, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:00:36, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 07:00:36, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 16: ERRNO = Broken
> pipe
> > > [2002/11/22 07:00:36, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 07:00:36, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:01:33, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:03:32, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:03:39, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:03:59, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:04:04, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:04:20, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 07:06:16, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:24:39, 0] lib/pidfile.c:pidfile_create(88)
> > >   ERROR: smbd is already running. File
> /usr/local/samba/var/locks/smbd.pid
> > > exists and process id 12272 is running.
> > > [2002/11/22 07:29:30, 0] lib/util_sock.c:read_socket_data(478)
> > > [2002/11/22 07:29:30, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > >   read_socket_data: recv failure for 44301. Error = Connection reset by
> peer
> > > [2002/11/22 07:29:31, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 17: ERRNO = Broken
> pipe
> > > [2002/11/22 07:29:31, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 07:29:31, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 07:29:31, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 17: ERRNO = Broken
> pipe
> > > [2002/11/22 07:29:31, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 07:32:23, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:32:27, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:32:28, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:49:36, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:49:42, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 07:49:42, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 10: ERRNO = Broken
> pipe
> > > [2002/11/22 07:49:42, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 07:49:52, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:49:52, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:51:21, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:53:38, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:54:09, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 10: ERRNO = Broken
> pipe
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 10: ERRNO = Broken
> pipe
> > > [2002/11/22 07:55:06, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 07:55:35, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:56:18, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:56:26, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:56:30, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 07:59:16, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 10:36:38, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 11:08:26, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 11:10:03, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 11:10:10, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 11:10:53, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 11:36:32, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 11:48:34, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 12:03:38, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:05:36, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:06:47, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 12:06:52, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:06:57, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 23199. Error = Connection reset by
> peer
> > > [2002/11/22 12:28:52, 0] lib/util_sock.c:write_socket_data(542)
> > > [2002/11/22 12:28:52, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 12:28:52, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 9: ERRNO = Broken
> pipe
> > > [2002/11/22 12:28:52, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 12:30:57, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:31:00, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:32:21, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:36:05, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:36:10, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:36:11, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:36:14, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:39:07, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 12:47:53, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 12:58:19, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 13:00:48, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 13:07:05, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 24659. Error = Connection reset by
> peer
> > > [2002/11/22 14:02:59, 0] lib/util_sock.c:read_socket_data(478)
> > > [2002/11/22 14:02:59, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 18021. Error = Connection reset by
> peer
> > >   read_socket_data: recv failure for 7139. Error = Connection reset by
> peer
> > > [2002/11/22 14:35:19, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 21739. Error = Connection reset by
> peer
> > > [2002/11/22 14:56:19, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 28241. Error = Connection reset by
> peer
> > > [2002/11/22 16:14:07, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 16:29:06, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 16:29:06, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 16: ERRNO = Broken
> pipe
> > > [2002/11/22 16:29:06, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 19:39:22, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 19:39:22, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 19:39:26, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 19:41:33, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 20:30:42, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 20:43:45, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 20:43:45, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 20:43:45, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 16: ERRNO = Broken
> pipe
> > > [2002/11/22 20:43:45, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/22 20:44:13, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 20:47:27, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:17:11, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:18:10, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:18:56, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:19:36, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:19:36, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:19:56, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:21:15, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:22:35, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:28:32, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 21:28:51, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:30:13, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:30:15, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:30:17, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:36:07, 0] lib/util_sock.c:read_socket_data(478)
> > > [2002/11/22 21:36:07, 0] lib/util_sock.c:read_socket_data(478)
> > > [2002/11/22 21:36:07, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:36:07, 0] lib/util_sock.c:write_socket_data(542)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/22 21:36:07, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 9: ERRNO = Broken
> pipe
> > > [2002/11/22 21:36:07, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:37:26, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:37:30, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:37:35, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:40:34, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 21:42:41, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 21:59:45, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 22:09:24, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 22:26:15, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/22 23:47:17, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 23:47:52, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 23:47:52, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 23:47:56, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/22 23:48:08, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 00:25:18, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/23 00:25:18, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 16: ERRNO = Broken
> pipe
> > > [2002/11/23 00:25:18, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/23 00:26:04, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:27:06, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:28:05, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:28:40, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:28:46, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:29:11, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:29:17, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 00:31:04, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 01:52:54, 0] lib/util_sock.c:read_socket_data(478)
> > > [2002/11/23 01:52:54, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 26119. Error = Operation timed out
> > >   read_socket_data: recv failure for 61159. Error = Operation timed out
> > > [2002/11/23 01:52:54, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 40719. Error = Operation timed out
> > > [2002/11/23 01:52:54, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 55319. Error = Operation timed out
> > > [2002/11/23 02:26:47, 0] lib/util_sock.c:read_socket_data(478)
> > > [2002/11/23 02:26:47, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 36339. Error = Operation timed out
> > >   read_socket_data: recv failure for 34879. Error = Operation timed out
> > > [2002/11/23 02:26:47, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 55319. Error = Operation timed out
> > > [2002/11/23 11:48:53, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 11:48:59, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/23 11:48:59, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 9: ERRNO = Broken
> pipe
> > > [2002/11/23 11:48:59, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/23 12:19:13, 0] lib/util_sock.c:write_socket_data(542)
> > > [2002/11/23 12:19:13, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/23 12:19:13, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 12: ERRNO = Broken
> pipe
> > > [2002/11/23 12:19:13, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/23 12:24:20, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/23 12:32:07, 0] lib/util_sock.c:open_socket_in(830)
> > >   bind failed on port 139 socket_addr = 192.168.1.24.
> > >   Error = Can't assign requested address
> > > [2002/11/23 13:05:23, 0] lib/util_sock.c:write_socket_data(542)
> > >   write_socket_data: write failure. Error = Broken pipe
> > > [2002/11/23 13:05:23, 0] lib/util_sock.c:write_socket(566)
> > >   write_socket: Error writing 65534 bytes to socket 12: ERRNO = Broken
> pipe
> > > [2002/11/23 13:05:23, 0] lib/util_sock.c:send_smb(730)
> > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > [2002/11/23 13:06:17, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 13:07:00, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 13:07:04, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 13:07:06, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:11:25, 0] lib/util_sock.c:read_socket_with_timeout(300)
> > >   read_socket_with_timeout: timeout read. read error = Connection reset
> by
> > > peer.
> > > [2002/11/23 15:11:26, 0] smbd/oplock.c:oplock_break(782)
> > >   oplock_break: receive_smb error (Connection reset by peer)
> > >   oplock_break failed for file Scans
> > > In/daredevil/dd_op34_02_c34c_3/dd_op34_02_c34c_3.0110.cin (dev = 29300,
> > > inode = 1063922).
> > > [2002/11/23 15:11:26, 0] smbd/oplock.c:oplock_break(870)
> > >   oplock_break: client failure in break - shutting down this smbd.
> > > [2002/11/23 15:11:55, 0] smbd/oplock.c:request_oplock_break(1026)
> > >   request_oplock_break: no response received to oplock break request to
> pid
> > > 1285 on port 1371 for dev = 29300, inode = 1063922
> > >   for dev = 29300, inode = 1063922, tv_sec = 3de00afe, tv_usec = 15342
> > > [2002/11/23 15:17:00, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:17:00, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:17:09, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:17:23, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:17:45, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:19:05, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:19:11, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:19:37, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Connection reset by peer
> > > [2002/11/23 15:27:34, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/23 15:38:01, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > > [2002/11/23 15:57:08, 0] lib/util_sock.c:read_socket_data(478)
> > >   read_socket_data: recv failure for 4. Error = Operation timed out
> > > [2002/11/23 16:32:14, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > >   call_nt_transact_ioctl: Currently not implemented.
> > >
> > >
> > > ----- Original Message -----
> > > From: "David Smithson" <david@customfilmeffects.com>
> > > To: <stacey@vickiandstacey.com>
> > > Cc: <questions@FreeBSD.ORG>
> > > Sent: Saturday, November 23, 2002 4:38 PM
> > > Subject: Re: Network connection dropping during file transfers
> > >
> > >
> > > > > Hi David,
> > > > >    By chance, is it possible for you to let the list know:-
> > > >
> > > > Yes.
> > > >
> > > > > 1]Client OS
> > > >
> > > > Clients are Windows 2000 Professional SP3 and Windows 2000 Server SP3.
> > > >
> > > > > 2] Are you using DHCP?
> > > >
> > > > Yes.  A Windows 2000 domain controller also provides DHCP services to
> the
> > > > Windows 2000 Pro clients.  All servers are static.
> > > >
> > > > > 3] Are you using a Wins Server for your domain?
> > > >
> > > > The domain controller currently provides WINS and DNS services.
> > > >
> > > > > 4] For how long does the connection stay off-line before coming
> back?
> > > >
> > > > This period seems to be indefinite based on unquantified observations.
> I
> > > > have not timed this period.  A few times it seemed never to come back
> up.
> > > I
> > > > even tried ifconfig nge0 down && ifconfig nge0 up to re-initialize the
> > > > interface.  This didn't help.  Rebooting the server fixed the
> interface in
> > > > these instances.
> > > >
> > > > > The reasoning behind the above is the fact that this might an issue
> of
> > > > > how (if this is so) MS Windows clients on dhcp maintain respective
> > > > > connections over the network during data transfer - You may well be
> > > > > seeing cases of timeouts on the client end here.
> > > >
> > > > I'll do whatever it takes to get this working.  Anything else I should
> > > look
> > > > into?
> > > >
> > > > > Stacey
> > > > >
> > > > >
> > > > > On Sun, 2002-11-24 at 00:09, David Smithson wrote:
> > > > > > P.S.  I'm using Samba 2.2.7.
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "David Smithson" <david@customfilmeffects.com>
> > > > > > To: <questions@FreeBSD.ORG>
> > > > > > Sent: Saturday, November 23, 2002 3:46 PM
> > > > > > Subject: Network connection dropping during file transfers
> > > > > >
> > > > > >
> > > > > > > Hi.  I'm having trouble with a mission-critical file-server.
> Server
> > > > is
> > > > > > > FreeBSD 4.5, exporting the filesystem with Samba over gigabit
> > > copper.
> > > > > > > Clients are Windows 2000.  During multiple read/write operations
> > > > between
> > > > > > the
> > > > > > > clients and the server, the network connection to the server
> will
> > > drop
> > > > out
> > > > > > > for an indefinite period of time and then somehow reconnect.
> This
> > > > > > obviously
> > > > > > > interrupts file transfers and foils all of the Windows clients'
> > > > > > > explorers.exe processes.  This also leads to incomplete files on
> the
> > > > > > server
> > > > > > > and frozen smbd processes.  Dmesg outputs nothing of interest.
> > > > Smbstatus
> > > > > > > outputs this:
> > > > > > >
> > > > > > > Samba version 2.2.2
> > > > > > > Service      uid      gid      pid     machine
> > > > > > > ----------------------------------------------
> > > > > > > W            nobody   wheel     1357   bunnicula (192.168.1.5)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:27:19 2002
> > > > > > > X            nobody   wheel     1357   bunnicula (192.168.1.5)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:27:19 2002
> > > > > > > W            nobody   wheel     1308   render-02 (192.168.1.12)
> Sat
> > > > Nov 23
> > > > > > > 15:17:00 2002
> > > > > > > W            nobody   wheel     1312   render-01 (192.168.1.10)
> Sat
> > > > Nov 23
> > > > > > > 15:17:09 2002
> > > > > > > W            nobody   wheel     1318   ethel    (192.168.1.8)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:17:36 2002
> > > > > > > W            shaina   wheel     1326   lucy     (192.168.1.15)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:18:09 2002
> > > > > > > W            amani    wheel     1283   bunnicula (192.168.1.5)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:10:26 2002
> > > > > > > X            amani    wheel     1283   bunnicula (192.168.1.5)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:10:30 2002
> > > > > > > X            shaina   wheel     1326   lucy     (192.168.1.15)
> Sat
> > > Nov
> > > > 23
> > > > > > > 15:21:09 2002
> > > > > > > W            nobody   wheel     1311   ricky-athlon
> (192.168.1.13)
> > > Sat
> > > > Nov
> > > > > > > 23 15:17:08 2002
> > > > > > > W            nobody   wheel     1309   render-03 (192.168.1.11)
> Sat
> > > > Nov 23
> > > > > > > 15:17:04 2002
> > > > > > > W            administrator wheel     1284   render-01
> (192.168.1.10)
> > > > Sat
> > > > > > Nov
> > > > > > > 23 15:10:26 2002
> > > > > > > X            administrator wheel     1284   render-01
> (192.168.1.10)
> > > > Sat
> > > > > > Nov
> > > > > > > 23 15:10:33 2002
> > > > > > >
> > > > > > > Locked files:
> > > > > > > Pid    DenyMode   R/W        Oplock           Name
> > > > > > > --------------------------------------------------
> > > > > > > 1284   DENY_ALL   WRONLY     EXCLUSIVE+BATCH
> > > > > > > /array1/renders/Daredevil/film/OP34-02/OP34-02_0118.cin   Sat
> Nov 23
> > > > > > > 15:10:53 2002
> > > > > > > 1283   DENY_ALL   WRONLY     EXCLUSIVE+BATCH
> > > > > > > /array1/renders/Daredevil/film/OP34-02/OP34-02_0119.cin   Sat
> Nov 23
> > > > > > > 15:10:54 2002
> > > > > > >
> > > > > > > The two processes above (1284 and 1283) don't release their
> locks
> > > > until
> > > > > > they
> > > > > > > are killed.
> > > > > > >
> > > > > > > log.smbd | tail -n 50 shows this:
> > > > > > >
> > > > > > >   write_socket_data: write failure. Error = Broken pipe
> > > > > > > [2002/11/23 12:19:13, 0] lib/util_sock.c:write_socket(566)
> > > > > > >   write_socket: Error writing 65534 bytes to socket 12: ERRNO =
> > > Broken
> > > > > > pipe
> > > > > > > [2002/11/23 12:19:13, 0] lib/util_sock.c:send_smb(730)
> > > > > > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > > > > > [2002/11/23 12:24:20, 0]
> smbd/nttrans.c:call_nt_transact_ioctl(1762)
> > > > > > >   call_nt_transact_ioctl: Currently not implemented.
> > > > > > > [2002/11/23 12:32:07, 0] lib/util_sock.c:open_socket_in(830)
> > > > > > >   bind failed on port 139 socket_addr = 192.168.1.24.
> > > > > > >   Error = Can't assign requested address
> > > > > > > [2002/11/23 13:05:23, 0] lib/util_sock.c:write_socket_data(542)
> > > > > > >   write_socket_data: write failure. Error = Broken pipe
> > > > > > > [2002/11/23 13:05:23, 0] lib/util_sock.c:write_socket(566)
> > > > > > >   write_socket: Error writing 65534 bytes to socket 12: ERRNO =
> > > Broken
> > > > > > pipe
> > > > > > > [2002/11/23 13:05:23, 0] lib/util_sock.c:send_smb(730)
> > > > > > >   Error writing 65534 bytes to client. -1. (Broken pipe)
> > > > > > > [2002/11/23 13:06:17, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 13:07:00, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 13:07:04, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 13:07:06, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:11:25, 0]
> > > lib/util_sock.c:read_socket_with_timeout(300)
> > > > > > >   read_socket_with_timeout: timeout read. read error =
> Connection
> > > > reset by
> > > > > > > peer.
> > > > > > > [2002/11/23 15:11:26, 0] smbd/oplock.c:oplock_break(782)
> > > > > > >   oplock_break: receive_smb error (Connection reset by peer)
> > > > > > >   oplock_break failed for file Scans
> > > > > > > In/daredevil/dd_op34_02_c34c_3/dd_op34_02_c34c_3.0110.cin (dev =
> > > > 29300,
> > > > > > > inode = 1063922).
> > > > > > > [2002/11/23 15:11:26, 0] smbd/oplock.c:oplock_break(870)
> > > > > > >   oplock_break: client failure in break - shutting down this
> smbd.
> > > > > > > [2002/11/23 15:11:55, 0]
> smbd/oplock.c:request_oplock_break(1026)
> > > > > > >   request_oplock_break: no response received to oplock break
> request
> > > > to
> > > > > > pid
> > > > > > > 1285 on port 1371 for dev = 29300, inode = 1063922
> > > > > > >   for dev = 29300, inode = 1063922, tv_sec = 3de00afe, tv_usec =
> > > 15342
> > > > > > > [2002/11/23 15:17:00, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:17:00, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:17:09, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:17:23, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:17:45, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:19:05, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:19:11, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > > [2002/11/23 15:19:37, 0] lib/util_sock.c:read_socket_data(478)
> > > > > > >   read_socket_data: recv failure for 4. Error = Connection reset
> by
> > > > peer
> > > > > > >
> > > > > > >
> > > > > > > What does this indicate?  Have I provided enough information
> here?
> > > > > > >
> > > > > > > By the way, the transfers that are taking place are initiated by
> a
> > > > visual
> > > > > > > effects / compositing program called Digital Fusion.  The
> clients
> > > are
> > > > > > render
> > > > > > > engines that are currently being used to render shots for the
> > > upcoming
> > > > > > > feature film "Chicago".  I must deliver these rendered frames
> > > tomorrow
> > > > by
> > > > > > 9
> > > > > > > p.m.  :(  Your help will be much appreciated.
> > > > > > >
> > > > > > > --
> > > > > > > David Smithson - Systems Administrator
> > > > > > > Custom Film Effects (http://www.customfilmeffects.com)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > > > > with "unsubscribe freebsd-questions" in the body of the message
> > > > > >
> > > > > >
> > > > > >
> > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > > > with "unsubscribe freebsd-questions" in the body of the message
> > > > > --
> > > > > Stacey Roberts
> > > > > B.Sc (HONS) Computer Science
> > > > >
> > > > > Web: www.vickiandstacey.com
> > > > >
> > > >
> > > >
> > > >
> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > with "unsubscribe freebsd-questions" in the body of the message
> > >
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-questions" in the body of the message
> > --
> > Stacey Roberts
> > B.Sc (HONS) Computer Science
> >
> > Web: www.vickiandstacey.com
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
-- 
Stacey Roberts
B.Sc (HONS) Computer Science

Web: www.vickiandstacey.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1038104729.43256.96.camel>