Same error once again.
Thomas Cameron
archimage at linux-magic.com
Wed May 2 03:53:55 GMT 2001
Sorry, I should have made clear - I installed on Solaris 8/Sparc.
However, I just got done installing on Red Hat 7, compiling from source.
I ran:
tar zxvf samba-latest.tar.gz
cd samba-2.2.0/source
./configre --prefix=/opt/samba
make
make install
export PATH=$PATH:/opt/samba/bin:/opt/samba/sbin
smbpasswd -a [username]
Then I made sure that the following line was in /etc/services:
swat 901/tcp # Samba Web Administration Tool
Also, made sure that the file /etc/xinetd.d/swat looks like this:
# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901 with your favorite web browser.
service swat
{
disable = no
port = 901
socket_type = stream
wait = no
only_from = 127.0.0.1
user = root
server = /opt/samba/sbin/swat
log_on_failure += USERID
}
I restarted xinetd by issuing the command:
service xinetd restart
Then I used Netscape to access SWAT:
netscape http://localhost:901
I then set up the workgroup info, WINS server address, and so on.
Finally, I created a quick start/stop script in /etc/rc.d/init.d:
#!/bin/bash
# smb - script to start/stop Samba
# chkconfig: 235 89 15
# description: Samba daemon
case $1 in
start)
/opt/samba/sbin/nmbd -D
/opt/samba/sbin/smbd -D
;;
stop)
# OK, this is a little brutal, but it works
killall nmbd smbd &> /dev/null
killall -9 nmbd smbd &> /dev/null
;;
restart)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart}"
esac
I then ran chkconfig smb reset to set the symlinks in the various
/etc/rc.d directories.
Voila! When I run /etc/rc.d/init.d/smb start (or just "service smb
start"), a quick ps command gives me:
[root at conjurer /root]# ps ax | grep mb
2604 ? S 0:00 /opt/samba/sbin/nmbd -D
2606 ? S 0:00 /opt/samba/sbin/smbd -D
Hope this helps.
Thomas
Trevor Benson wrote:
>
> 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
More information about the samba
mailing list