similar to: "Oplock" error messages with samba on Linux

Displaying 20 results from an estimated 1000 matches similar to: ""Oplock" error messages with samba on Linux"

2003 Jul 31
1
oplock_break: client failure in oplock break in file ...
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)
2002 Oct 15
0
What is "client failure in oplock break"?
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
2000 May 03
2
2.0.7: unsolicited oplock break reply
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
2002 Jun 05
1
oplock break failures
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
2005 Feb 02
1
Oplock errors in 2.2.8a
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
2000 Feb 14
3
File Locking Issues/Oplock problems
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
2004 Apr 03
1
oplock windows XP client
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
2002 Mar 15
1
2 Samba problems (oplock & hosts allow)
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
2004 Oct 19
0
Oplock errors
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]
1999 Mar 23
0
Oplock break (again) End of file from client
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
2002 Oct 10
1
Problem with oplock
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
2003 Mar 24
0
oplock problems with samba 2.2.7a
Hi , Before I copy and paste the oplock message(s), here is the setup I have. I have samba server (on Solaris 2.8) which shares out the NFS mounted directories to the windows world. All was working fine till today morning when users complained of extreme slow performance , looks like there is problems with oplocks accessing some files. Below is the snippet to the error log. [2003/03/24
2003 Jul 29
0
oplock problem on NTUSER.DAT
Hi, I'm on a network with a Samba 2.2.8a fileserver + PDC (Mandrake Linux 9.0) and various Win2000 Pro clients. Very often, when I log off from one client and log on a different one soon after, I get an error message telling me that the remote profile cannot be loaded, and the local one will be used, as if the profile was still locked by the previous session. One peculiar thing to notice is
2003 Jul 29
1
oplock problem on NTUSER.DAT (fwd)
---------- Forwarded message ---------- Date: Tue, 29 Jul 2003 19:40:48 -0400 (EDT) From: Rashkae <rashkae@tigershaunt.com> To: Marco De Vitis <starless@despammed.com> Subject: Re: [Samba] oplock problem on NTUSER.DAT Hi Marco Try to veto oplocks for that file. In the global section of your smb.conf, add the following veto oplock files = /NTUSER.DAT/ Let us know if that changes
1999 Jan 15
1
Oplock question
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
1999 Mar 24
0
Oplock break (again) End of file from client (PR#15037)
btenison@dibbs.net wrote: > > 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? > > 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
2001 Mar 15
0
OpLock timeout errors on Samba v2.0.6
We see the following errors that cause the NT 4.0 workstation Word file saves to fail. I have been tweeking the oplock parameters for awhile now. Can't seem to get the right mix. Does anyone see this same problem with older versions or the v2.0.7 version. [2001/03/13 10:43:26, 0] smbd/oplock.c:(973) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file
2005 Jul 29
0
incoherent oplock request/reply
Hello, I'm running a samba 3.0.14a server in production on a fedora core 3 (kernel 2.6.9-1.667smp) with a least 250 clients (XP Pro SP2) (up to 400 sometimes). A few days ago, a problem appeared with a soft that we are using for a long time. (Petit Robert, a french dictionnary). When someone launch the dictionnary, many clients are freezed when they try to access to the "start
2002 Jan 15
1
Oplock problems under high load
Hello, all. I'm using Samba 2.2.2 at my FreeBSD 4.4-STABLE server, and have next problems: There is pool of W2K machines, each starting compilation job (usually 2 at one dual CPU machine). Then these jobs trying to simultaneously access sources, located at Samba server, appear problems. Then I running 2 compilation threads from single machine - there is no problems. For jobs error seems
1999 Jan 25
0
URGENT!!!! Oplock doesn't work in 2.x!!! [Re: Oplock problem with (PR#12995)
mjt@tls.msk.ru wrote: > > I posted some messages about this, but there is still NO RESPONCE AT ALL!! > As I see, more and more users encountered this problem -- > oplocks code in 2.x (starting from all betas and now in 2.0) DOES NOT WORK!!! > > David! You can place "oplocks = no" into your [global] section and all > will be fine. But problem is opened! > There