similar to: Oplock break (again) End of file from client (PR#15037)

We recently tried the upgrade to 2.0 Beta series (just finished testing Beta 4) on our network. Everything works fine with 1.9.18pl10, but once we start 2.0 in its place we start getting the following in the log files: [1998/12/17 05:00:12, 1] smbd/files.c:file_init(219) file_init: Information only: requested 10000 open files, 246 are available. [1998/12/17 05:07:52, 1]

I keep getting the following in the log files now that we've upgraded to the latest cvs 2.0 branch. Any ideas what we can do to fix this? Thanks! Bruce Mar 23 08:45:34 gate smbd[22692]: [1999/03/23 08:45:34, 0] smbd/oplock.c:oplock_break(773) Mar 23 08:45:34 gate smbd[22692]: oplock_break: end of file from client Mar 23 08:45:34 gate smbd[22692]: oplock_break failed for file COMM.INF

Hi! After more work on the oplock_break problem, I've found the following in my tcpdump-smb logging. It seems that when ost5 (pid=26339 in the logs that follow) requests access to the oplocked file comm.inf from ost6 (pid=5872) the oplock_break failes (this is NOT isolated to any one or two systems on our network, just using these two as an example, and the server reports no dropped packets

Hi! Been having the same problem with oplocks for a while and have been trying to figure out what's going wrong. The FAQ says that we may have a networking (hardware?) problem, but according to the Linux box's ifconfig results, we have had no errors and no dropped packets on the internal network. I am able to reproduce the error pretty much at will on our network, and it is not isolated

I've been getting a lot of these recently in my samba-log ever since I downloaded the latest cvs SAMBA_2_0 branch code. Mar 6 18:13:06 gate smbd[11126]: cos5 (192.168.7.132) connect to service rsession as user rsession (uid=707, gid=100) (pid 11126) Mar 6 18:13:15 gate smbd[11126]: [2000/03/06 18:13:15, 0] lib/fault.c:fault_report(40) Mar 6 18:13:15 gate smbd[11126]:

fyi the way that this will be used is to have: encrypted passwords = no update encrypted = yes for a few days, have everyone log in with their clear-text password, and a private/smbpasswd file will automatically be generated. then switch to encrypted passwords = yes update encrypted = no and voila. if you were feeling _really_ adventurous you could have: include = smb.conf.%M and have one

TO THE SAMBA TEAM: MAY YOUR TRIBE BE HERE FOREVER! YOU' SIMPLY GREAT BUT i CAN'T AFFORD TO BUY YOU A PIZZA BUT OUR NATIVE PIE "BUKO (YOUNG COCONUT) PIE" IS BETTER! i HAVE BEEN USING SAMBA 1.9.16P9 AND STILL ALRIGHT. PERHAPS I'LL DO CHANGE TO SAMBA 2.0 AND THIS IS A LONG WAY! i DID TRIED SAMBA SINCE MY OFFICE CAN'T AFFORD TO BUY NFS TO SERVE AT LEAST 20 PCs AND

Below are a number of errors that appeared in a log file today. I am running Samba v2.2.5 on a Red Hat Linux v7.3 system. The client experiencing/causing the errors below is a WinXP(SP1) machine. The log entries below pertain to 2 errors, the first in handling file "6.zip" and the second in attempting to run file "DiskeeperWks413zssi.exe". I didn't see the first

Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success)

I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst

After upgrading from 2.0.10a to 2.2.4, I'm seeing many new messages being logged. What does this mean? Jun 5 09:42:50 files2 smbd[27585]: [2002/06/05 09:42:50, 0] smbd/oplock.c:oplock_break(788) Jun 5 09:42:50 files2 smbd[27585]: oplock_break: no break received from client within 30 seconds. Jun 5 09:42:50 files2 smbd[27585]: oplock_break failed for file

On Mon, 18 Jan 1999 samba@samba.org wrote: > Date: Sun, 17 Jan 1999 14:55:42 +0730 (SST) > From: Gregory Hosler <gregory.hosler@eno.ericsson.se> > To: samba@samba.org, samba-bugs@samba.org, btenison@dibbs.net > Subject: request_oplock_break - a clue - what does it mean ? > Message-ID: <XFMail.990117145542.gregory.hosler@eno.ericsson.se> > > Hi all, > > I

Hi everyone. With the latest cvs (as of this afternoon) we are getting the following in the logs: Apr 19 09:19:42 gate smbd[23055]: [2000/04/19 09:19:42, 0] smbd/service.c:make_connection(554) Apr 19 09:19:42 gate smbd[23055]: Can't change directory to /home//profile (No such file or directory) Apr 19 09:19:42 gate smbd[23055]: [2000/04/19 09:19:42, 0] smbd/service.c:make_connection(554)

Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store

Hi, We are having connection timeout issues in Excel and Word. Was this an issue that was resolved in post 3.0 versions? We are running 2.2.8a. Below is the samba log file and I have attached a netmon output. Thanks, Domenic [2005/01/24 09:13:48, 0] smbd/oplock.c:oplock_break(797) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file

Im running an accounting package (Sage Businessworks) and I'm running into issues with file locking with this program when I put the businessworks data files on a Samba file share. I'd like to get it off a NT file share if at all possible as Im about to decommission our NT server. Im running Samba 2.0.6 Im seeing errors from any machine accessing the Accounting data: ==> log.ryan

Hi, I use samba for 5 years in a small enterprise network. We have recently changed our windows client and migrate from windows 95 to windows XP :-). Samba is running on a debian woody. Since we are using windows XP home edition I can see the following log messages : [2004/04/02 15:27:50, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success) oplock_break failed for

Hello everybody, I have 2 questions about Samba operation: First, hostnames don't work in my "hosts allow" directive, although smb.conf(5) explicitly says "You can specify the hosts by name or IP number". If I specify a client by its name, that client is not allowed access, even though the server can do reverse DNS on the client's IP. The message I get in the

Hi ! I'm having some problems, where the user lose connection with Samba and the Windows98 Workstation crash. Looking at logs I found the follow messages: ---- [2004/10/15 11:36:49, 0] smbd/oplock.c:oplock_break(807) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file Notes.ini (dev = 904, inode = 18530507, file_id = 1). [2004/10/15 11:36:49, 0]

Well I'm having some trouble with samba, I had those troubles on a box for quite some time and not long ago I moved all the stuff to a new box to see if it'll work better but it doesn't. I'm monitoring one person in particular because she's the one who do most of the editing stuff in there. What happens is when she opens a document (.doc or .xls most of the time), when she