similar to: Broken Pipe Errors

Hi there everyone, Again another slight thing I noticed since I upgraded to Samba 2.0.6 from 2.0.5a. I'm using RedHat Linux on a Celeron 400 with kernel 2.2.13. My socket options in smb.conf is set to "TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUF=8192 SO_RCVBUF=8192". However I've started getting the following everytime I SIGHUP to reload the configs and stop-start:

Hi, In the last a couple of weeks, Eric helped me fixed a couple of my new samba 3.0.5 running on HP-UX 11i hang issues. Right now, people still experience slowness when they run some applications on the samba shares OR recursive list directories on the samba shares. There was not a lot of errors in the individual log files. However,there are some errors in log.smbd and log.0.0.0.0 file. 1)

Greetings Experts! Sorry for my poor english, but I?m inside of a terrible nightmare!!! I?m using Samba+LDAP has about 2 months ago without problems, but in the last 4 hours, the system is absolutelly unstable. I couldn?t upgrade or patched anything. The problem simply has appeared. Principally system characteristics: - Sun Fire V880 running Solaris 9 - openldap-2.2.23 - nss_ldap-232 -

Dear All, we are experiencing severe problems with Samba 2.2.0 (with quota support) running on a dual processor (400MHz) Sun E450 running Solaris 2.7. This is used as a central file server for student diskspace, accessed by approx 1200 PCs running NT 4. Up until recently we experienced some, what we assume to be, loading issues with connections during the middle of the day being slow.

> I have a network that sporadically give 'network busy' errors. One morning > the workstations will all connect up fine and stay up throughout the days > work, yet the next day there is not one machine that can log on to the > network. It may run fine for two weeks, then bam, three days of no logins. > Yet the internet works fine. Could I copy my smb.conf file and rpm -e

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 Federico, many thanks to you. This patch helped me too. Do you know the intention of the original changes by the samba team in ipc.c. I don't think, it is a good idea to store all profiles in an separate directory and the user registry in the home path. Thanks again Rudolf Rudolf Kollien email: Rudolf.Kollien@medas.de Rudolf.Kollien@kollien.de

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

too. However, when I mount the share via smbfs (on a Linux box, of course), the same file is 2.0T as reported by du (ie: du -csh), 18446744072754680087 bytes as reported by ls, but is only 3340095767 bytes as reported by stat. Further comparison of stat results of the same file via smbfs and directly are intriguing. directly (ie: on the server): Size: 3340095767 Blocks: 6523640 IO Block: 4096

Hi everyone, Our system is a Debian GNU/Linux box running Linux kernel 2.4.17-xfs and Samba 2.2.3 (from the 2.2.3-5 package from Sid), built using gcc-3.0.3. With Samba 2.2.2 we hit certain tdb errors where make_connection would reject connections arbitrarily. Supposedly this was fixed using 2.2.3 so we upgraded right away (thankfully we do only have Windows 95, 98 and ME clients so we

Olaf, (cc XFS and Samba lists) On Mon, 4 Mar 2002 at 15:50, Olaf Fr?czyk wrote: > I have similar problems, (with doc and xls) but I don't have file > corruption (I hope :) We hope. I've turned off oplocks with my Samba completely just to be sure. Things haven't slowed down that drastically, but perhaps it's because the load isn't as high as with some other much larger

Hi everyone, Just today one of our users informed me that a file she was working on in Microsoft Excel 97 got corrupted. She was working on the file directly on our server, which is running Samba 2.2.3a compiled using gcc-3.0.4 on Linux kernel 2.4.17-xfs and XFS-based filesystems. I checked the Samba logs for her machine and found the following in a search for the filename of the Excel file she

Wolfgang, (cc Linux XFS list) (cc Samba list) Quoting wolfgang.glas@ev-i.at: > I just found you message in the samba mailing list archives and foiund > out, that we have a very similar problem. We are using samba-2.2.1a on a > kerenl-2.4.16 and we use reiserfs. > We also experience data corruption with messages like: > > [2002/03/14 15:15:26, 0] >

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]

Hello, I cannot login on a samba server. sambaserver (service): hans username: hans I use the command: net use s: \\hans\hans. At home everything works well but at work -when I am logged on in a NT network with username 'hare'- it did not work. The following message appear in the samba logfile. [2000/10/06 11:36:52, 1] smbd/reply.c:reply_sesssetup_and_X(925) Rejecting user

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

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]

Suddenly, today, my wife's Windows 95 machine can't print to the network printer on my Linux machine. It complains that "there was an error printing to \\posh\lp ... There was a problem printing to the port." The error 1st occurred (coincidentally?) after I had upgraded the kernel from 2.4.18 to 2.4.19. But rebooting to 2.4.18 has made no difference. We're running smbd

Hi there everyone, I recently upgraded to 2.0.6 from 2.0.5a in a hope to improve data integrity (I was having oplock_break problems that would affect the integrity of a lot of Excel files). So far so good with the oplock_breaks (even with oplocks reenabled). :-) However, I've started having problems with the clients' Windows profiles not being placed in my defined logon path.

Dear friends, I receive the error "Error Bad file descriptor" when samba start, the socket option in smb.conf have the line: "socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=4096" My distribuition is Red Hat 6.2 and the Samba version is 2.0.69. This is the error log /var/log/samba.smb: [2000/08/31 14:07:06, 0] lib/util_sock.c:set_socket_options(148) Failed to set