similar to: locking database

I am getting this error message when I type smbstatus.The message does not offer a lot of assistance. Is there any one with a good reason for this message?? Thx in advance Glenn Samba version 2.2.0a Service uid gid pid machine ---------------------------------------------- Failed to open byte range locking database ERROR: Failed to initialise

Greetings! After successfully setting up the printer using my RedHat Linux 7.2 (using command-line interface), and after installing my ethernet card (again, using command-line interface), I've tried to setup my linux server to share the printer with Windows-based machines. I thought I pretty much did everything right, but when I type a "smbstatus", I get the following: >Samba

i have taken a default intel redhat 7.2 machine which came with samba 2.2.1a and removed samba, samba-common, samba-client and samba-swat. i also removed /etc/samba and /var/lock/samba and all samba log files i then installed the samba RPM for samba 2.2.5 from: http://se.samba.org/samba/ftp/Binary_Packages/redhat/RPMS/7.2/samba-2.2.5- 1.i386.rpm i then installed this with rpm -ivh

I have installed Samba 2.2.2 on Solaris 8 Sun Blade. Samba starts but I can not see any workgroup and when "smbstatus" is started I get the following error: Samba version 2.2.2 Service uid gid pid machine ---------------------------------------------- Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise

This was a PITA to fix. I finally came up with this solution. Don't know why it works because none of this is referenced in the Makefile. I'm guessing it's screwed up because I used the stock samba RPM on the Red Hat 7.1 iso CD. Put these two symbolic links in your /etc/samba directory. codepages -> /usr/local/samba/lib/codepages smb.conf ->

Hi, I have been trying to get Samba 2.2.2 to run on HP-UX 11.00 64 bit, but seem to be running into problems with the locking databases. (Note : this is running the smb.conf file from the examples directory in SAMBA 2.2.2). I have tried to two different servers and both of them generate the same result described below. The problem I have hit is after compiling samba and starting up the system

Afternoon, I'm running OpenBSD 3.1, and since being informed that since 2.2.3a contains a bug I should upgrade to 2.3.4 - which I've done. I've installed this from source, and havn't seen any reason to believe the build process didn't work properly (Other than having duplicated binaries in /usr/local/samba/bin/ and in /usr/source_distributions/samba-2.2.4/source/bin/smbd

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

I am running RH8 with Samba 2.2.6. I am attempting to connect a Win2k box to my Linux box. I "see" Linux in Network Neighborhood, I can ping the Win2k BIOS name, and I can ping the Linux box BIOS name. However When I click on accessing linux I get resource not available. And when I run smbstatus I get the following: Samba version 2.2.6 Service uid gid pid machine

Well I seem to have everything working now, I started up the daemons and the ran smbclient -L localhost and then smbstatus and everything looks good!Strange.. Thanks, -Dusty > -----Original Message----- > From: Dusty Hall [mailto:draper7@ziplip.com] > Sent: Friday, February 15, 2002, 8:01 AM > To: samba@lists.samba.org > Subject: [Samba] Locking Module? > > Hello everyone,

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)): tdb_open_ex: could not

Hi! I've been fighting with Samba for over a week now and I can't seem to work it out. It all started when I installed the standard samba (2.2.1a-4) which came with RH7.2. I ran "smbstatus" and got the following error: Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting. I've tried the

Hi, I am upgrading my linux server to samba 2.2.4 and I compiled it as the following : ./configure --prefix=/usr/samba-2.2.4 --exec-prefix=/usr/samba-2.2.4 --with-configdir=/etc/samba --sysconfdir=/etc/samba --with-lockdir=/var/lock/samba --with-piddir=/var/lock/samba --with-codepagedir=/lib/codepages --with-logfilebase=/var/log/samba --with-privatedir=/etc/samba/private make make install Now,

Freebsd 5.4 smbstatus output #smbstatus Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting ??????? ----- Original Message ----- From: "Jeremy Allison" <jra@samba.org> To: "Konstantin Getman" <getman@junik.lv> Sent: Tuesday, August 16, 2005 8:06 PM Subject: Re: your mail

Hi all, i am trying to run Samba 2.2.3a under a RedHat 7.2 i386 machine. After i compiled and installed the packages, i made a smb.conf up. Just some standard stuff nothing special. Now, when i start smbd and then check it with smbstatus it gives me this error : Samba version 2.2.3a Service uid gid pid machine ---------------------------------------------- tdb((null)):

I have successfully implemented Samba in the past but I am now perplexed by a new installation which fails smbstatus with the message: "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/brlock.tdb: No such file or directory Failed to open byte range locking database "tdb((null)): tdb_open_ex: could not open file /var/cache/samba/locking.tdb: No such file or directory ERROR:

Odd, I just noticed that smbstatus does not work, either: >[root@xxxxx /root]# smbstatus > >Samba version 2.2.2 >Service uid gid pid machine >---------------------------------------------- > >Failed to open byte range locking database >ERROR: Failed to initialise locking database >Can't initialise locking module - exiting Is it possible that

Hello All, I am facing some problems with the samba 3.0.14a + Cups 1.1.12 and Solaris 10 combination. I am using the printing services on Samba. Whenever I give a smbstatus command I get the following error. The clients are able to connect and access the printers, but still this error occurs, which is really weird. Error: sessionid.tdb not initialised

Dear Members, I have install samba 3.0.10 d # ./smbstatus Sessionid.tdb not initialised /usr/local/samba/var/locks/connections.tdb not initialised This is normal if an SMB client has never connected to your server. Failed to open byte range locking database ERROR: Failed to initialise locking database Can't initialise locking module - exiting # But the var/locks directory

> "Moving tdb files in /var/lock/samba/*.tdb to /var/cache/samba/*.tdb", Nothing to worry about > Now, the smbstatus command produces the message: > > "/var/cache/samba/connections.tdb not initialised > This is normal if an SMB client has never connected to your server. > Failed to open byte range locking database > ERROR: Failed to initialise locking