samba - Aug 2002 - Samba 2.2.5 - can't initialize locking module`

I have just upgraded a RedHat 6.2 box from Samba 2.0.10 to Samba 2.2.5
in one of our elementary school buildings because we now have some w2k
boxes that must log to the domain. I'm now getting an error on
initializing the locking modules when I run smbstatus. I did the upgrade
remotely so I don't know yet whether workstations work properly with the
upgrade.


[root@fvserver samba]# smbstatus

Samba version 2.2.5
Service      uid      gid      pid     machine
----------------------------------------------

Failed to open byte range locking database
ERROR: Failed to initialise locking database
Can't initialise locking module - exiting


Does anyone know what causes this and how to correct it?

Thanks.


-- 
Mike Rambo
mrambo@lsd.k12.mi.us

-----[ mrambo@lsd.k12.mi.us wrote on 08/01/02 12:20:06 PM -0400 ]-----

--> [root@fvserver samba]# smbstatus
-->
--> Samba version 2.2.5
--> Service      uid      gid      pid     machine
--> ----------------------------------------------
-->
--> Failed to open byte range locking database
--> ERROR: Failed to initialise locking database
--> Can't initialise locking module - exiting
-->
-->
--> Does anyone know what causes this and how to correct it?

I have seen this after upgrades as well. It seems to go away if I do:

	smbclient -L host -U user

This should return a list of the shares on the server. It usually seems to 
clear the locking error. If not, then actually connect to one of those 
shares:

	smbclient //server/share -U user

This should log you in, you can 'ls' and look at the contents. Then 
'quit'. This has always worked for me.

HTH

     --Ben--

-----------------------
Ben Griffith
bgriffit@email.unc.edu
-----------------------