Hi:
I am running Samba 1.9.17 at SUN Solaris 2.6 and it works well.
After I upgrade Samba 2.0.3 or 2.0.5a, my Excel spreadsheets got
trouble. In the Samba log file I got:
[1999/08/23 10:45:32, 0] lib/util_sock.c:write_socket_data(570)
write_socket_data: write failure. Error = Broken pipe
Anybody has an idea what is the problem?
I am very appreciated if you can reply it to yang@cibc.ca.
TIA
-Adam
ccelso@embraer.com.br
2001-Sep-21 06:22 UTC
write_socket_data: write failure. Error = Broken pipe
Do you know this problems!?
[2001/09/20 16:10:54, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:15:55, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:20:56, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:25:58, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:44:52, 0] param/loadparm.c:(1923)
Unknown parameter encountered: "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(2549)
Ignoring unknown parameter "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(1923)
Unknown parameter encountered: "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(2549)
Ignoring unknown parameter "revalidate"
How to fix !?
My smb.conf is:
##START-OF-SMB.CONF
#
[global]
workgroup = Samba
server string = FileServer
domain master = yes
preferred master = yes
os level = 65
log file = /opt/samba/var/log.%U
max log size = 32
security = server
password server = sambapwd
socket options = TCP_NODELAY
dns proxy = no
deadtime = 120
wins server = wintwins
include = /opt/samba/lib/U.%U
[homes]
public = no
printable = no
browseable = yes
guest ok = yes
#
##END-OF-SMB.CONF
att.
Carlos Celso de Almeida
ccelso@embraer.com.br
2001-Sep-21 06:22 UTC
write_socket_data: write failure. Error = Broken pipe
===================================================Carlos Celso de Almeida
EMBRAER - GTT - Divis?o de Inform?tica
012-345-1254
----- Forwarded by Carlos Celso de Almeida/INFORMAT/SJK/EMBRAER on
21/09/2001 10:23 -----
Carlos Celso
de Almeida To: samba@samba.org
/INFORMAT/SJK cc:
/EMBRAER Subject: write_socket_data: write
failure. Error = Broken
pipe
21/09/2001
10:19
Do you know this problems!?
[2001/09/20 16:10:54, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:15:55, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:20:56, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:25:58, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:44:52, 0] param/loadparm.c:(1923)
Unknown parameter encountered: "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(2549)
Ignoring unknown parameter "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(1923)
Unknown parameter encountered: "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(2549)
Ignoring unknown parameter "revalidate"
How to fix !?
My smb.conf is:
##START-OF-SMB.CONF
#
[global]
workgroup = Samba
server string = FileServer
domain master = yes
preferred master = yes
os level = 65
log file = /opt/samba/var/log.%U
max log size = 32
security = server
password server = sambapwd
socket options = TCP_NODELAY
dns proxy = no
deadtime = 120
wins server = wintwins
include = /opt/samba/lib/U.%U
[homes]
public = no
printable = no
browseable = yes
guest ok = yes
#
##END-OF-SMB.CONF
att.
Carlos Celso de Almeida
MCCALL,DON (HP-USA,ex1)
2001-Sep-21 07:01 UTC
write_socket_data: write failure. Error = Broken pipe
Hi Carlos,
Since you are in Security=server mode, the problem COULD be that the broken
pipe
messages are indicating that you lost your connection from this smbd to the
password
server; every time a smbd sends a keepalive packet to a client, it
'piggybacks' a
keepalive to the password server, and if that connection is broken, you get
this
message. This is fixed in the latest Samba 2.2.x; and can be avoided by
explicitly
adding the "keepalive = 0" parameter to the global section of smb.conf
and
restarting
samba.
This is just one possibility - I mention it because of the spacing of the
broken pipe
messages - almost exactly 5 minutes apart - some of the Samba packages out
there have
a default of 300sec. for keepalive (like HP-UX), in contradiction to what
most of the
man pages will say. You can check this by running testparm and grepping for
keepalive
to see what the default on your samba installation is.
Hope this helps,
Don
-----Original Message-----
From: ccelso@embraer.com.br [mailto:ccelso@embraer.com.br]
Sent: Friday, September 21, 2001 9:19 AM
To: samba@samba.org
Subject: write_socket_data: write failure. Error = Broken pipe
Do you know this problems!?
[2001/09/20 16:10:54, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:15:55, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:20:56, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:25:58, 0] lib/util_sock.c:(541)
write_socket_data: write failure. Error = Broken pipe
[2001/09/20 16:44:52, 0] param/loadparm.c:(1923)
Unknown parameter encountered: "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(2549)
Ignoring unknown parameter "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(1923)
Unknown parameter encountered: "revalidate"
[2001/09/20 16:44:52, 0] param/loadparm.c:(2549)
Ignoring unknown parameter "revalidate"
How to fix !?
My smb.conf is:
##START-OF-SMB.CONF
#
[global]
workgroup = Samba
server string = FileServer
domain master = yes
preferred master = yes
os level = 65
log file = /opt/samba/var/log.%U
max log size = 32
security = server
password server = sambapwd
socket options = TCP_NODELAY
dns proxy = no
deadtime = 120
wins server = wintwins
include = /opt/samba/lib/U.%U
[homes]
public = no
printable = no
browseable = yes
guest ok = yes
#
##END-OF-SMB.CONF
att.
Carlos Celso de Almeida
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
ccelso@embraer.com.br
2001-Sep-21 07:11 UTC
write_socket_data: write failure. Error = Broken pipe
I Don,
thanks, but my samba version is 2.2.1a...
regards
carlos celso
MCCALL,DON (HP-USA,ex1)
2001-Sep-21 07:20 UTC
write_socket_data: write failure. Error = Broken pipe
Hi,
The fix for this wasn't applied till 9 August 2001, so it would not BE
in Samba 2.2.1a...
Hope this helps,
Don
-----Original Message-----
From: ccelso@embraer.com.br [mailto:ccelso@embraer.com.br]
Sent: Friday, September 21, 2001 10:10 AM
To: MCCALL,DON (HP-USA,ex1)
Cc: samba@samba.org
Subject: RE: write_socket_data: write failure. Error = Broken pipe
I Don,
thanks, but my samba version is 2.2.1a...
regards
carlos celso
Elias Gerber
2002-Feb-19 13:22 UTC
[Samba] write_socket_data: write failure. Error = Broken pipe
hello everybody.
i'm a newbie in linux and therefor in samba too, but already got some sort
of problem: my machine is running perfectly, samba is working perfectly,
but always in a period of about 10 days "samba" (or what else?)
doesn't
work anymore. if i try to connect to the shares on the linux-machine i get
a timeout error in windows. in the /var/log/samba -file i've seen this
error: "write_socket_data: write failure. Error = Broken pipe" (more
of the
log is at the bottom of the message). now someone told me that this error
(broken pipe) is a clear signal that the ethernet device is out of order
(or another hardware defect; hub, cable).... can you confirm this ? or
might it be something else ? the (little bit more detailed) symptoms are:
- periodically the shares can't be reached (timeout error in windows). this
happens every 10 - 15 days
- pinging the machine is no problem
- trying to log on to the machine via ssh gets a lot of timeout errors, but
if i can log in once, everything works fine (no broken connections, no lag)
- restarting samba (using './samba restart') doesn't help
- rebooting the server helps (but is a very "nasty" solution)
- everything is on a 100mbit lan
i hope i've included the important information, if you need more infos
please tell me.
greetz
elias gerber
[sorry for my bad english - i hope you understand what i tried to tell you ;( ]
little bit more from the log file comes here ('/var/log/samba'):
[2002/02/19 19:09:32, 1] lib/util_sock.c:client_name(1007)
Gethostbyaddr failed for 192.168.0.20
[2002/02/19 19:09:32, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2002/02/19 19:09:32, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2002/02/19 19:09:32, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
[2002/02/19 19:09:42, 1] lib/util_sock.c:client_name(1007)
Gethostbyaddr failed for 192.168.0.20
[2002/02/19 19:09:42, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2002/02/19 19:09:42, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2002/02/19 19:09:42, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
[2002/02/19 19:10:36, 1] lib/util_sock.c:client_name(1007)
Gethostbyaddr failed for 192.168.0.20
[2002/02/19 19:10:36, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2002/02/19 19:10:36, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2002/02/19 19:10:36, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
[2002/02/19 19:10:46, 1] lib/util_sock.c:client_name(1007)
Gethostbyaddr failed for 192.168.0.20
[2002/02/19 19:10:46, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2002/02/19 19:10:46, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2002/02/19 19:10:46, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
Elias Gerber
Sonnenbergrain 2
CH - 3013 Bern
egerber@gmx.net
+41 (0)76 382 63 47