Q:Problems with samba 2.2.3a

[Dr. Peer-Joachim Koch]

Hi,

we have installed the current release of samba from HP.
It's based on samba 2.2.3a (B8725-1.0.8)
We installed the software and used the same config file and started the samba stuff and
run into the following problems.

1) The machine was only reachable under one netbios alias. (normaly hostname+2 aliases!)

2) Only some pc could connect (~15 out of 150), but those could
also only see the toplevel of a share
3) The following error messages were written into smbd.log.(see below).

I tried to disable all kind of lock's, but without any luck.
Has anybody some ideas what#s going on here ?
(We switched back to the previous release, which worked fine - only
the acl stuff will not work perfect.)

Thanks for your help!

Bye, Peer

[2002/08/12 13:25:09, 0] tdb/tdbutil.c:(475)
tdb((NULL)): tdb_open_ex: failed to get global lock on /var/opt/samba/locks/brlock.tdb: No locks available
[2002/08/12 13:25:09, 0] locking/brlock.c:(233)
Failed to open byte range locking database
[2002/08/12 13:25:09, 0] tdb/tdbutil.c:(475)
tdb((NULL)): tdb_open_ex: failed to get global lock on /var/opt/samba/locks/locking.tdb: No locks available
[2002/08/12 13:25:09, 0] locking/locking.c:(354)
ERROR: Failed to initialise locking database
[2002/08/12 13:25:09, 0] tdb/tdbutil.c:(475)
tdb((NULL)): tdb_open_ex: failed to get global lock on /var/opt/samba/locks/brlock.tdb: No locks available
[2002/08/12 13:25:09, 0] locking/brlock.c:(233)
Failed to open byte range locking database
[2002/08/12 13:25:09, 0] tdb/tdbutil.c:(475)
tdb((NULL)): tdb_open_ex: failed to get global lock on /var/opt/samba/locks/locking.tdb: No locks available
[2002/08/12 13:25:09, 0] locking/locking.c:(354)
ERROR: Failed to initialise locking databaseb

[U.SivaKumar_2]

Hi.
please attach your smb.conf file.

regards,
U.SivaKumar

[Rainer von Bongartz]

check out your smb.conf and make sure the value of the "lock directory" directory exists.

Regards
Rainer

[Dr. Peer-Joachim Koch]

Hi,

I've attached the config part of the smb.conf.
The problem seems to be related to some kernal parameters as John Cheney
posted to me (nflocks).
I will check it out (the value is nflocks=200, as John pointed out), if a increase will solve the problem..

Bye, Peer

bash-2.03# more /etc/opt/samba/smb.conf
#
[global]
workgroup = BGC
netbios name = ORCA
netbios aliases = ATLAS RHEA BONITA
# server string = HPUX_Samba FILE/PRINT Server
server string = DVA.b024.HPUX_Samba.File_Server.141.5.16.x
interfaces = lan1
log file = /var/adm/samba/%m.log
# keepalive = 90
socket options = TCP_NODELAY
local master = no
read only = no
case sensitive = no
preserve case = yes
short preserve case = yes
dos filetime resolution = yes
syslog = 0
read prediction = Yes
read size = 65535
password server = andorra manta
security = server
printing = cups
acl schemes = hpux_posix unix

[homes]
comment = Homedirectories %U
path = /mnt/Local/Homes/%U
writeable = Yes
create mask = 0750
guest ok = Yes
browseable = No

[U.SivaKumar_2]

Hi,
Does the /var/opt/samba/locks directory exists?.
lock directory = /var/opt/samba/locks (default if not defined)
If that directory does not exists do this.
As root do this
Stop all samba processes
#mkdir -p /var/opt/samba/locks
Start the samba and look for any errors.

regards,
U.SivaKumar

[Dr. Peer-Joachim Koch]

Hi,

the folder was allready there. We change the permission without any luck. I will try the NFLOCKS parameter.

Bye, Peer

[Stefan Pendl]

Hi Peer,
have had the same problem, read the documentation and found the kernel parameters section. Changed nflocks to the following:

10*maxusers/2

maxusers is set to 256 so that there will about 100 clients able to connect since there is one smbd process for each client which uses 10 locks ;-)

Steve