On 12/19/2011 02:05 PM, Jeremy Allison wrote:
On Fri, Dec 16, 2011 at 02:00:17PM -0500, Allen Chen wrote:

I have the same message in samba log file, even though I set up "log
level =  0".
My Samba 3.4.5 PDC is listening on both ports 139 and 445 under
CentOS 5.6 32bits.
Here is the message:
[2011/10/26 16:02:05,  0] lib/util_sock.c:539(read_fd_with_timeout)
[2011/10/26 16:02:05,  0] lib/util_sock.c:1491(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  read_fd_with_timeout: client 0.0.0.0 read error = Connection reset
by peer.
[2011/10/26 16:02:05,  0] lib/util_sock.c:1491(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
[2011/10/26 16:02:05,  0] lib/util_sock.c:1491(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
I have lots of the same messages in samba log file(exactly the same as above).
I use compiled samba 3.4.5 PDC on CentOS 5.6 32bit with 200 XP clients.
I googled and try to fix it without success.
The good thing is that nobody complains.
We're going to need debug level 10 log output to even begin
to look into this.

Jeremy.

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to