Oplock problem in 2.0.7 locks up Samba completely

David Collier-Brown David.Collier-Brown at canada.sun.com
Wed Aug 16 13:42:04 GMT 2000

Dr Andreas F Muller <afm at othello.ch> wrote: 
| 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 =
| inode = 16484, tv_sec = 3997a286, tv_usec = c5bf0 

As a pallitive, I'd put in 
		keepalive  = 60
to make samba check for failed clients every minute or so.

  This should make the smbd for the client that isn't responding
to clean up and exit.
  Note that this is not a fix: it's an avoidance procedure.

  The problem is probably at one of the clients: look for log messages
indicating which processes exited, and grep for those in the logs
to see which clients disconnected.
  Then make a client-specific conf file (with include = something.%m
see http://www.oreilly.com/catalog/samba/chapter/book/ch09_01.html)
and turn the client log level up to 3, log that to a seperate
file and look to see if anything obviously wrong shows up.

David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb at canada.sun.com

More information about the samba mailing list