similar to: Write failure - broken pipe errors in logs

Hi there everyone! One of the users complained to me that yesterday, he suddenly couldn't access the network. He was online the whole day, then suddenly at around 6:45pm he couldn't write. A restart of his workstation rendered him completely disconnected from the Samba domain. Server is running Samba 2.0.6 on a RedHat 6.0 machine with Linux kernel 2.2.13. Client is running Windows95 OSR2

Bonjour, I'm running samba 2.0.4 on a Sparc Solaris 2.5.1 and I have some error logs when I'm trying to connect to a sharing directory from *some* NT4 WS (SP4 or SP5): pchp2 (194.xxx.xxx.xxx) connect to service centreAS as user truc (uid=1326, gid=1320) (pid 22939) [1999/08/26 15:52:57, 0] lib/util_sock.c:write_data(415) write_data: write failure. Error = Broken pipe [1999/08/26

Hi, The only reason I use Samba is I want to connect my linux desktop with my windows laptop and share the larger disk with the laptop. I got weird problem that I could only write to the samba server but I could not read from it with errors like: [2001/03/04 16:36:38, 0] lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe [2001/03/04 16:36:38, 6]

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

(Server :Mandrake 7, Samba 2.0.6) (Client : PC Win95 and Win 98) Samba's work fine since one year but yesterday We had a big problem in my college Lots of PC's client can't connect (invalid password). In the samba's log we read : > [2000/05/19 12:15:21, 1] smbd/service.c:close_cnum(568) > renoir (192.168.84.189) closed connection to service valancee > [2000/05/19

I run samba 2.0.6 on Sun ultra enterprise 2 server. Lately the logs have been filled with [1999/11/29 20:11:19, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [1999/11/29 20:19:31, 0]

Hi everybody, I'm writing for an any help. I tried some news groups about linux etc... nothing :-( On our normaly working network unexpectly starts this problem. Win clients don't see smb server. See logs below: log.nmb [2002/03/11 09:37:33, 1] nmbd/nmbd.c:main(757) Netbios nameserver version 2.0.10 started. Copyright Andrew Tridgell 1994-1998 [2002/03/11 09:37:33, 0]

Hi, I have inherited responsibility for a group of Samba servers and I am in the process of upgrading them all to run 2.0.6. I have come across a couple of things I am not sure about and would appreciate some advice. I have checked in the FAQ lists and the mailing list archives, but there seems to be no mention of these things in there. First Question ============== I have just upgraded a

Hello (again), I'm using samba 2.0.6-4mdk on a Linux Mandrake 7.1 (kernel 2.2.15). Client are Win95/98 machines. I set up several guest shares (no password) along with a printer share. There is a problem when the Win9x are connecting to the shares (just after the password window) : Sometimes (not on a regular basis), the connection to the share doesn't work (with an error message like

I am getting the following error from smbclient and am not sure as where the problem is. smb: \gcc\> dir write_socket_data: write failure. Error = broken pipe write_socket: Error writing 91 bytes to socket 3: ERRNO = broken pipe failed session setup Error writing 91 bytes to client. -1. Exiting This appears to be happening about a minute after I establish a session. Up until that time file

Hi Folks, I am running Samba 2.0.6 on Solaris 2.6 and I have a bunch of write errors showing up in my log.smb file. Here are some of them: ---------------------------------------------- [1999/12/16 14:25:42, 1] lib/util_sock.c:client_name(997) Gethostbyaddr failed for 10.41.0.184 [1999/12/16 14:25:42, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken

for months, we keep fighting issues with smbd (now at released 2.2.6), config is with spoolss, domain logon, and the client in question is an NT4 machine. server is a i386/linux 2.2.19 For a very long time, we thought it was related to oplocks, but now after having them disabled, it still is there. Level 3 Log is as follows: [2002/10/22 17:08:18, 3] smbd/ipc.c:reply_trans(480) trans

[2003-02-20 15:24:05] EROR playlist-script/playlist_script_get_filename Couldn't open pipe to program "/usr/local/icecast2/ices-ad.pm" Segmentation fault I'm running a perl script that apparently (rarely) kills ices for this reason. The error occurs approximately once per day for no apparent reason. For the rest of that period the script runs fine. In fact, after some

I'm running a fairly simple samba server on a sun V440, solaris 9 Samba version: 3.0.10 smbd daemon only In the server logs I'm getting: write_socket_data: write failure. Error = Broken pipe write_socket: Error writing 4 bytes to socket 5: ERRNO = Broken pipe Error writing 4 bytes to client. -1. (Broken pipe) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 Closing connections Yielding

> [2003-02-20 15:24:05] EROR playlist-script/playlist_script_get_filename > Couldn't open pipe to program "/usr/local/icecast2/ices-ad.pm" Segmentation > fault > > I'm running a perl script that apparently (rarely) kills ices for this reason. > The error occurs approximately once per day for no apparent reason. For the > rest of that period the script

Greetings, I use Icecast for the live airing of my open phones podcast, and we've recently had some trouble with malicious actors attempting to disrupt the production in various ways, most of which are beyond the scope of this inquiry. Today the Icecast feed kept disconnecting and resetting the listener count. This happens on rare occasions, and I usually accept this as a noisy neighbor

Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]

Okay, here's the background. Fedora Core 4, all recent updates. Using samba-3.0.14a-2. Trying to mount a remote shared folder, and sharing it for local users in my office. Using /etc/fstab to auto-mount it on bootup. Here is the /etc/fstab line that I use to do this: //share/ccc /gobo smbfs username=XXXXX,password=XXXXXX,uid=10395,gid=30038,fmask=770,dmask=770 0 0 I use winbind to

Hi. Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have added will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont

Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have add will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont understand: