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

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

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]

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

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

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

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

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

I would really appreciate some help figuring out why one of my students has "disappeared" from the user list, and what to do about it. I'm using Samba3 on Fedora; the client machines are running WinXP. The system has been up and running since the beginning of September. Today one of my 4th-graders was unable to log on; she didn't read the error message carefully, so she

Hi all, I have a problem opening file on a samba share with Word 6.0. We use samba 2.0.5a running on a HP9000/800 (HP-UX 10.20). Often when try to open file, Word stop responding for some minutes (generally from 2 to 5) and then word succed to open it. In the sambadir/var the corresponding log file is like this : [1999/09/20 17:10:52, 1] smbd/service.c:make_connection(521) pc000320

2.0.4b, RH60 (2.2.6+raid1, non root-raid), accessed from win98/ie5. Intermittently ie5 takes very long to load an html page from samba; at the same time it loads another html page ok from another linux/samba1.9.x At 10:47:34 I click on the html page and it is loaded at 10:48:18. [1999/06/23 10:47:34, 1] smbd/service.c:make_connection(488) go (10.0.0.115) connect to service go as user go

Hello everybody, I have a strange failure in my samba environment ( samba 2.2.3a ), when users try to open files on a samba share via the windows explorer. I see the following messages in the samba log file : hcnch049 (10.12.48.103) connect to service homedir as user pa015276 (uid=8065, gid=8048) (pid 19565) [2002/08/01 08:54:09, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb

Hello everybody, I have a strange failure in my samba environment ( samba 2.2.3a ), when users try to open files on a samba share via the windows explorer. I see the following messages in the samba log file : hcnch049 (10.12.48.103) connect to service homedir as user pa015276 (uid=8065, gid=8048) (pid 19565) [2002/08/01 08:54:09, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb

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

Can any one help me ? This has been bugging me for ages. I have been using different versions of samba for a while on different versions of Redhat (7.0, 7.2, 7.3). I regularly get erratic freezing (for about a minute) whenever I right click on files. This has happened on different computers on different sites on different networks, so I assume it's quite consistent This is what I get when

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)

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

Hi All, I am having a problem with Samba that seems to be a bug. I say this because I read the archives and they described a problem similar to mine and were told that it was a bug in older version of Samba and the latest version should have it fixed. I am running what is essentially a RH 7.3 on a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5 and am using the following

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]:

Hi there everyone! I'm using Samba 2.0.5a-19990721 on a RedHat 6.0 machine with Linux kernel 2.2.12. My system generally works fine, however recently I've had some complaints about some files being corrupted. The latest and best-handled to enable a debugging happened at around the same time. Both clients were using Windows95 OSR2 machines with Excel 97 SP-2. Two users reported the problem