Lee Howard
2000-Oct-23 22:47 UTC
logon errors, write_socket_data: write failure. Error = Broken pipe
I'm having authentication (logon) errors occasionally. After trying to log on for a few minutes eventually it will succeed. I'm using samba-2.0.7 on RedHat 6.1 (updated). The samba logs look like: [2000/10/23 14:03:24, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2000/10/23 14:03:24, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2000/10/23 14:03:24, 0] lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting [2000/10/23 14:03:32, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2000/10/23 14:03:32, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2000/10/23 14:03:32, 0] lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) tomp (192.168.2.5) couldn't find service netlogon [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) tomp (192.168.2.5) couldn't find service netlogon [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) tomp (192.168.2.5) couldn't find service netlogon [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) Does anyone have a clue as to what could be wrong? thanks. Lee Howard
Gerald Carter
2000-Oct-24 14:31 UTC
logon errors, write_socket_data: write failure. Error = Brokenpipe
Lee Howard wrote:> > I'm having authentication (logon) errors occasionally. After > trying to log on for a few minutes eventually it will > succeed. I'm using samba-2.0.7 on RedHat 6.1 (updated). > The samba logs look like: ><snip...>> [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) > tomp (192.168.2.5) couldn't find service netlogonLee, I wonder if you have 'domain logons = yes' but have not defined a [netlogon] service. Cheers, jerry ---------------------------------------------------------------------- /\ Gerald (Jerry) Carter Professional Services \/ http://www.valinux.com/ VA Linux Systems gcarter@valinux.com http://www.samba.org/ SAMBA Team jerry@samba.org http://www.plainjoe.org/ jerry@plainjoe.org "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
Lee Howard
2000-Oct-24 20:13 UTC
logon errors, write_socket_data: write failure. Error = Brokenpipe
At 09:31 AM 10/24/00 -0500, Gerald Carter wrote:>Lee Howard wrote: >> >> I'm having authentication (logon) errors occasionally. After >> trying to log on for a few minutes eventually it will >> succeed. I'm using samba-2.0.7 on RedHat 6.1 (updated). >> The samba logs look like: >> ><snip...> >> [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) >> tomp (192.168.2.5) couldn't find service netlogon > >Lee, > >I wonder if you have 'domain logons = yes' but have not defined a >[netlogon] service.Quite right. I use the domain logon feature simply for network diagnostic purposes. (It's very useful over the phone to know that the system is or isn't "logging on" properly. It saves me in phone diagnostic time.) So, I don't need a logon script or a logon service, I just need Samba to authenticate the username and password for said diagnostic value. This configuration (no [netlogon] service) is identical to that of many other Samba servers that I have configured, and this seems the be the only problem case (write_socket_data: write failure). However, I have created a [netlogon] service and a logon script for the server that is having trouble, and I'll see how that goes. Lee.
Lee Howard
2000-Oct-25 19:59 UTC
logon errors, write_socket_data: write failure. Error = Brokenpipe
At 02:13 PM 10/24/00 -0600, Lee Howard wrote:>At 09:31 AM 10/24/00 -0500, Gerald Carter wrote: >>Lee Howard wrote: >>> >>> I'm having authentication (logon) errors occasionally. After >>> trying to log on for a few minutes eventually it will >>> succeed. I'm using samba-2.0.7 on RedHat 6.1 (updated). >>> The samba logs look like: >>> >><snip...> >>> [2000/10/23 14:03:34, 0] smbd/service.c:make_connection(214) >>> tomp (192.168.2.5) couldn't find service netlogon >> >>Lee, >> >>I wonder if you have 'domain logons = yes' but have not defined a >>[netlogon] service. > >This configuration (no [netlogon] service) is identical to that of many >other Samba servers that I have configured, and this seems the be the only >problem case (write_socket_data: write failure). However, I have created a >[netlogon] service and a logon script for the server that is having >trouble, and I'll see how that goes.I still get the same problems: [2000/10/25 13:45:19, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2000/10/25 13:45:19, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2000/10/25 13:45:19, 0] lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting [2000/10/25 13:45:28, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2000/10/25 13:45:28, 0] lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [2000/10/25 13:45:28, 0] lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting What is the problem? Thanks. Lee Howard