search for: request_oplock_break

...Oktober 2001. Everything works fine. At the end of Februar 2002 i got a problem. Please see the logfile. [2002/02/25 09:02:15, 0] smbd/password.c:domain_client_validate(1563) domain_client_validate: could not fetch trust account password for domain NENN [2002/02/25 09:02:47, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response received to oplock break request to pid 626 on port 34350 for dev = 308, inode = 1163298 for dev = 308, inode = 1163298, tv_sec = 3c79ef1b, tv_usec = 746a1 [2002/02/25 09:03:00, 0] smbd/password.c:domain_client_validate(1563) domain_client_validate: cou...

I saw a little discussion about this a few weeks ago but nothing concrete. We're running samba-1.9.18p8 under Solaris 2.6x86. I am periodically getting the following in the logfiles, usually _many_ at a time: 1998/11/03 14:42:00 request_oplock_break: no response received to oplock break request to pid 5411 on port 40884 for dev = 1980040, inode = 33c4d When I look up the PID (in this case 5411) I get the following: ps -ef | grep 5411 root 5573 5411 0 0:00 <defunct> jwt001 5411 8126 0 14:13:37 ? 0:02...

...Samba 2.0.6 on a solaris 7 (intel) box. Users (about 270 at one time) connect to the home directories located on the samba server by NT 4 workstations . Problem is ..Some times they lose access suddenly .In the log files the following message appears ?------- [2000/08/22 08:28:09, 0] smbd/oplock.c:request_oplock_break(1202) request_oplock_break: no response received to oplock break request to pid 2077 2 on port 54910 for dev = 19801c3, inode = 4582438 for dev = 19801c3, inode = 4582438, tv_sec = 39a14793, tv_usec = 5e40c [2000/08/22 08:28:10, 0] smbd/oplock.c:request_oplock_break(1202) request_oplock_break...

Users are trying to cennect to their home dirs ... the request_oplock_break is failing: [1999/10/21 10:50:39, 1] smbd/service.c:make_connection(521) gpnte109i (137.94.128.183) connect to service s22350 as user s22350 (uid=22350, gid=34) (pid 27704) [1999/10/21 10:50:54, 0] smbd/oplock.c:request_oplock_break(1136) request_oplock_break: no response received to oplock br...

...Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:08, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break:...

...ms-word files. The smbd processes have always been running as root. But now the users with the problem own their smbd process. And they get errors like such in the log file: for dev = 8100000, inode = 17169, tv_sec = 3e22d418, tv_usec = 931fe [2003/01/13 12:46:27, 0] smbd/oplock.c:(1204) request_oplock_break: no response received to oplock break request to pid 5755 on port 1450 for dev = 8100000, inode = 144022 for dev = 8100000, inode = 144022, tv_sec = 3e22dc57, tv_usec = d9670 [2003/01/13 12:46:30, 0] smbd/oplock.c:(1204) request_oplock_break: no response received to oplock break request to...

...ive_smb error (Connection reset by peer) oplock_break failed for file eudora/data/eudora.log (dev = 303, inode = 621482, file_id = 3). [2002/08/04 21:17:59, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2002/08/04 21:18:31, 0] smbd/oplock.c:request_oplock_break(981) request_oplock_break: no response received to oplock break request to pid 366 on port 1028 for dev = 303, inode = 621482, file_id = 3 [2002/08/04 21:19:49, 0] smbd/oplock.c:request_oplock_break(981) request_oplock_break: no response received to oplock break request to pid 367 on port 1029...

...CH samba-tests/W97pure.doc Fri Jun 19 16:01:33 1998 Share mode memory usage (bytes): 101984(99%) free + 336(0%) used + 80(0%) overhead = 102400(100%) total serenity# ls locks log.nmb log.smb log.ukswi1000 log.ukswi3101 serenity# tail log.ukswi1000 1998/06/19 17:23:20 request_oplock_break: no response received to oplock break request to pid 25917 on port 3273 for dev = ff00061a, inode = 3b20d 1998/06/19 17:23:30 request_oplock_break: no response received to oplock break request to pid 25917 on port 3273 for dev = ff00061a, inode = 3b20d 1998/06/19 17:23:41 request_oplock_break: no r...

I hope someone can enlighten me on this. Situation: NT network, Samba PDC, about 20 NT 4.0 workstations. log(s).smbd are created per machine for easier analysis (as log.smbd.<NetBios Name>). Not often, but often enough to be of concern, are errors in request_oplock_break that seem to indicate that another smbd process that should be listening for break requests on a UDP socket isn't, or isn't responding. Some time ago, for some very strange reason, the system was configured with share modes off, which caused these errors to occur constantly. That was co...

Has anyone tried using Windows 2000 Professional with Samba? I'm checking it out now, and when I try to connect to a share, I get an error message similiar to the one you get with Win98 and NT4 with SP3+ with encrypted passwords. Does anyone know the equivelant registry path to set plain text passwords? The NT4 path doesn't seem to exist:

...-- the problematic behavior of a W2K client starts during a login because the files in use are related to connecting to the printers and reading the printerdrivers. In the logfile we see quite a lot of lock problems: Jun 30 10:31:54 ux-254 smbd[13838]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun 30 10:31:54 ux-254 smbd[13838]: request_oplock_break: no response received to oplock break request to pid 15915 on port 37496 for dev = 811, inode = 130892307, file_id = 252 Jun 30 10:31:54 ux-254 smbd[3002]: [2003/06/30 10:31:54, 0] smbd/oplock.c:request_oplock_break(1011) Jun...

....18p10 on a Sparc Solaris 2.5 system, things hang for a while and then a dialog box pops up saying "Cannot copy {filename}: The session was cancelled. I've tried setting "oplocks = no", but I still see a lot of this in the log file when the failure occurs: 1998/09/09 16:29:11 request_oplock_break: no response received to oplock break request to pid 10448 on port 62848 for dev = 800008, inode = f56e 1998/09/09 16:29:11 request_oplock_break: broke oplock. get_share_modes Read share mode 0x20 pid=10448 get_share_modes: file with dev 8388616 inode 62830 -> 1 entries open_file_shared:...

...75). Mar 13 11:42:59 server02 smbd[10062]: [2007/03/13 11:42:59, 0] smbd/oplock.c:oplock_break(911) Mar 13 11:42:59 server02 smbd[10062]: oplock_break: client failure in oplock break in file Apps/EXACT70/USR/BEDRYF.IX Mar 13 11:43:10 server02 smbd[9113]: [2007/03/13 11:43:10, 0] smbd/oplock.c:request_oplock_break(1055) Mar 13 11:43:10 server02 smbd[9113]: request_oplock_break: no response received to oplock break request to pid 10062 on port 33112 for dev = fd01, inode = 28264408, file_id = 68 Mar 13 11:43:10 server02 smbd[9113]: [2007/03/13 11:43:10, 0] smbd/open.c:open_mode_check(734) Mar 13 11:43:10...

...inode = 53164, file_id = 1056). Jan 14 14:51:54 linux smbd[17789]: [2003/01/14 14:51:54, 0] smbd/oplock.c:oplock_break(878) Jan 14 14:51:54 linux smbd[17789]: oplock_break: client failure in break - shutting down this smbd. Jan 14 14:52:26 linux smbd[18488]: [2003/01/14 14:52:26, 0] smbd/oplock.c:request_oplock_break(1008) Jan 14 14:52:26 linux smbd[18488]: request_oplock_break: no response received to oplock break request to pid 17789 on port 33470 for dev = 302, inode = 53164, file_id = 1056 Jan 14 15:00:40 linux smbd[18335]: [2003/01/14 15:00:40, 0] smbd/password.c:domain_client_validate(1549) Jan 14 15:00...

...03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/locking.tdb): tdb_lock failed on list 80 ltype=0 (Resource deadlock avoided) [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/locking.tdb): tdb_unlock: count is 0 [2005/03/04 12:25:05, 0] smbd/oplock.c:request_oplock_break(977) request_oplock_break: PANIC : breaking our own oplock requested for dev = fe00, inode = 745870013, file_id = 1471 a nd no fsp found ! [2005/03/04 12:25:05, 0] lib/util.c:smb_panic2(1482) PANIC: request_oplock_break: no fsp found for our own oplock [2005/03/04 12:25:05, 0] lib/util.c:sm...

...o go zombie. I'll check w/ my solaris support tomorrow to learn why this is. Note that the very 1st smbs to go after /net/desktop.ini has registered an oplock, and because teh stat hangs the process, and never returns, the oplock is never released. Hence all future sbmds will report a request_oplock_break: no response received to oplock break request to pid (the pid of the 1st smbd) I would have thought that the solution would be to add /net to the list of "dont descend", so I did. That didn't work so I added "net", that still didn't work so I added "./net&q...

.../16 11:15:45, 0] smbd/open.c:open_mode_check(555) open_mode_check: Existent process 20445 left active oplock. [2002/11/16 11:15:45, 0] tdb/tdbutil.c:tdb_log(475) tdb(/var/cache/samba/locking.tdb): tdb_lock failed on list 54 ltype=0 (Interrupted system call) [2002/11/16 11:22:09, 0] smbd/oplock.c:request_oplock_break(981) request_oplock_break: no response received to oplock break request to pid 20445 on port 32964 for dev = 805, inode = 3326030, file_id = 95 [2002/11/16 11:22:09, 0] smbd/open.c:open_mode_check(551) open_mode_check: exlusive oplock left by process 20445 after break ! For file PROSYST/PRO02/S...

...gateway to a Pervasive SQL database (via a named pipe). Usually after a few days of perfect function (just over two weeks at the last occurrence of the problem), all Samba services lock up completely. The log is filled with messages like the follow- ing: [2000/08/14 09:49:14, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 5060 on port 3708 for dev = 3a01, inode = 16484 for dev = 3a01, inode = 16484, tv_sec = 3997a286, tv_usec = c5bf0 [2000/08/14 09:49:46, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no respon...

...an't kill smbd processes......) This is what happens in the log file: any ideas ? [2001/11/29 16:13:00, 1] smbd/service.c:make_connection(610) pc08ust (10.21.1.8) connect to service exchangejg99 as user exchangequota99 (uid=15056, gid=100) (pid 11777) [2001/11/29 16:13:02, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 11766 on port 37084 for dev = 3001, i for dev = 3001, inode = 14319625, tv_sec = 3c064fe6, tv_usec = 3e1d3 [2001/11/29 16:13:02, 0] smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock left by process...

Hello All, this morning, after rebooting our samba-testserver to activate some patches, we continuously got this error: [1999/02/18 09:53:29, 0] smbd/oplock.c:(943) request_oplock_break: no response received to oplock break request to pid 1650 on port 1230 for dev = ff000009, inode = 53134 [1999/02/18 09:53:40, 0] smbd/oplock.c:(943) request_oplock_break: no response received to oplock break request to pid 1650 on port 1230 for dev = ff000009, inode = 53134 [1999/02/18 09:53:50,...