Same error once again.

Edward Muller emuller at learningpatterns.com
Wed May 2 12:33:08 GMT 2001


I've run smbstatus on my 2.2.0 box without problems. I usually run smbstatus
to see if there are users connected, not to check if it is up.

-----Original Message-----
From: Trevor Benson [mailto:Tbenson at associatedbp.com]
Sent: Tuesday, May 01, 2001 5:14 PM
To: 'Edward Muller'; 'Thomas Cameron'; Samba List (E-mail)
Subject: RE: Same error once again.


Not to sounds like a complete idiot, but im more familiar with compiling or
stock RPM files, I obviously have heard of SRPM's, but am not really sure
what you would do with one. Since I have compiled from source tar ball would
this be another good method? Or just another way to test the same sourcecode
I downloaded from samba.org?  I am going to blow out my conf file and try to
make the basic one the PDF has, just enough lines to get it to start.  Does
anyone else out there even try to run smbstatus? Or did I get hung up on a
triviality that might not be causing my system to not function?  Noone has
commented on the fact they run smbstatus or not once bringing up samba, so
maybe its just an erroneous error and my system is really fine?


Thanks,
Trevor

 -----Original Message-----
From: 	Edward Muller [mailto:emuller at learningpatterns.com]
Sent:	Tuesday, May 01, 2001 2:12 PM
To:	Trevor Benson; 'Thomas Cameron'; Samba List (E-mail)
Subject:	RE: Same error once again.

I've got an install of Samba 2.2.0 up on a stock RedHat 7.1 system. Although
I did compile the rpm from the srpm myself. I also did not use my old
smb.conf file, as I am playing around with PDC stuff on a test box.

The 'samba' command was replaced with 'smb' and it is in
/etc/rc.d/init.d/smb ... so /etc/rc.d/init.d/smb
(start|stop|status|restart|etc) should work, it does for me. This is more
like debain AFAIK, which I use at home.

-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of Trevor Benson
Sent: Tuesday, May 01, 2001 12:26 PM
To: 'Thomas Cameron'; Samba List (E-mail)
Subject: RE: Same error once again.


Tom,

   What linux did you install on? It seems Redhat is moving further and
further away from standard locations for their stuff :(., I am not sure
where the $SAMBAHOME directory is if its not /etc/samba, and that had no
var/lock, I added it from the data inside /var/lock/samba to see if it was
that, but still it appears to do nothing to resolve. Every other Samba
install I have done has pretty much been turn-key, and no problems at all,
2.0.5a 2.0.7 and whatever the version I used before 2.0.5 was.  I turned on
debug, and the messages that come across all seem to be fine, I don't see
anything that looks like it didn't work properly, and lots of adds and other
messages in the log itself.

   Has ANYONE done a Redhat install from the RPM? Does it work for you on a
stock Redhat 7 system? I figured moving my smb.conf in place that was
working with the older versions should just bring this up, since that always
worked before. So far this has been the toughest install of samba I have run
into, and its just because it doesn't appear anyone else has had these
problems.  Although I still havnt heard anything from anyone on Redhat
installs.  I am about to blow out the RH server again and rebuild and then
install from source this time with no previous samba on the system.  The
install instructions are not too tough but I did this once before on 6.1 and
6.2 and had the exact same errors.  Who builds the RPM's, and do they
customize their RH install when they put samba in?

   Also did the 'samba' command disappear? I used to be able to run samba
stop|start|status|restart (was this a redhat script or something? Just seems
to be gone now).


Thanks,
Trevor

 -----Original Message-----
From: 	Thomas Cameron [mailto:archimage at linux-magic.com]
Sent:	Monday, April 30, 2001 7:13 PM
To:	Samba List (E-mail)
Subject:	Re: Same error once again.

I dunno if this helps, but I have a $SAMBAHOME/var/locks directory.
Maybe this is missing?

Thomas

Trevor Benson wrote:
>
> I just built a brandnew Redhat 7.1 server. I installed the RPM package
from
> ftp.samba.org <ftp://ftp.samba.org>  and after I run the smbd and nmbd I
> still end up with this error below. I have checked this list, and gone
> through the Project Doc's and the FAQ's. Nothing seems to reference the
> locking database not initializing.  Has anyone else had this issue?  On a
> fresh system with the RPM I wouldn't expect to have this much trouble,
> that's why I left the old server as is and tried to move forward with a
test
> box to see if I couldn't resolve this. Any help or idea's would be
> appreciated. The log.smbd and nmbd have NOTHING in them at this point. Im
> not really sure what to do.
>
> Samba version 2.2.0
> Service      uid      gid      pid     machine
> ----------------------------------------------
>
> Failed to open byte range locking database
> ERROR: Failed to initialise locking database
> Can't initialise locking module - exiting
>
> Thanks,
> Trevor Benson
> Director of Information Technology
> Associated Business Products
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba





More information about the samba mailing list