samba accept only 2 users

[Attila Horváth_1]

Hi,

I have samba version: 2.2.3a on hp-ux B.11.22 A ia64 (ta). The samba does not accept more then 2 connections at the same time. If there are 2 connections and I kill a connection, an another user can connect then.

Is there a licence limit on this version? :-o

[Robert-Jan Goossens]

Hi,

Could you check what option you use in the smb.conf file "max connections =" ?

Regards,
Robert-Jan

[Peter Godron]

Hi,
what is your nflocks kernel parameter set to?
You may not have enough resources there to allow extra connections.
Regards

[Peter Godron]

Hi,
also have a look at:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=661481
Regards

[Attila Horváth_1]

max smbd processes=0
max connections= 0

[Attila Horváth_1]

nflocks kernel = 200

[Robert-Jan Goossens]

how about maxusers ?

[Attila Horváth_1]

There is no maxusers in samba config.

[Attila Horváth_1]

maxusers in kernel is 512

[Robert-Jan Goossens]

In the kernel :-)

# kmtune -q maxusers

[Attila Horváth_1]

# kmtune -q maxusers
Parameter Current Dyn Planned Module
===================================================================
maxusers 512 - 512

[Mobeen_1]

Attila,
In addition to the kernel params suggested by other folks, please check and make sure that you samba.conf has the following

max connections = ???

regards
Mobeen

[Darren Prior]

Hi,

Have you transferred smb.conf from another machine, or did you use the default one?

regards,

Darren.

[Attila Horváth_1]

max connections = 0

[Attila Horváth_1]

I am using the default conf but I use swat for edit the config file.

[Darren Prior]

zero is the default value for max connections and means unlimited connections.

I'd suggest that you set debug level=3, restart Samba and try to connect again. Take a look through the log files to see what happens when the connection is refused.

regards,

Darren.

[Peter Godron]

Attila,
could you post your /etc/rc.config.d/nfsconf

[Attila Horváth_1]

# cat /etc/rc.config.d/nfsconf
#********************** NFSCONF ******************************

# NFS configuration. See nfsd(1m), mount(1m), pcnfsd(1m)
#
# @(#)B.11.22_ic46
#
# NFS_CLIENT: 1 if this node is an NFS client, 0 if not
# NFS_SERVER: 1 if this node is an NFS server, 0 if not
# Note: it is possible for one host to be a client, a server,
# both or neither! This system is an NFS client if you will
# be NFS mounting remote file systems; this system is a server
# if you will be exporting file systems to remote hosts.
# See Also: nfsd(1M), mount(1M).
# NUM_NFSD: Number of NFS deamons (nfsd) to start on an NFS server. Four
# has been chosen as optimal.
# NUM_NFSIOD: Number of NFS BIO daemons (biod) to start on an NFS client.
# Four has been chosen as optimal.
# PCNFS_SERVER: 1 if this node is a server for PC-NFS requests. This
# variable controls the startup of the pcnfsd(1M) server.
# See Also: pcnfsd(1M).
#
NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=16
NUM_NFSIOD=16
PCNFS_SERVER=0
# export feature does not work in this file since files are being
# sourced into another file rc.config and this file is being sourced
# into the startup scripts.

#
# DAEMON OPTIONS
#
# LOCKD_OPTIONS: options to be passed to rpc.lockd when it is started.
# STATD_OPTIONS: options to be passed to rpc.statd when it is started.
# MOUNTD_OPTIONS: options to be passed to rpc.mountd when it is started.
#
LOCKD_OPTIONS=""
STATD_OPTIONS=""
MOUNTD_OPTIONS=""
#
# automount configuration
#
# AUTOMOUNT = 0 Do not start automount
# AUTOMOUNT = 1 Start Automount.
# AUTO_MASTER = filename of the master file passed to automount
# AUTO_OPTIONS = options passed to automount
#
AUTOMOUNT=1
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"
#
# rpc.mountd configuration. See mountd(1m)
#
# START_MOUNTD: 1 if rpc.mountd should be started by a system startup script.
# 0 if /etc/inetd.conf has an entry for mountd.
# Note: rpc.mountd should be started from a system startup script,
# however, it can be started from either nfs.server or inetd, and
# MUST only be configured in one place.
#
START_MOUNTD=1
#
#autofs configuration. See autofs(1m)
#
#For the 11.0 Release line both AUTOFS and the old Automount
#are delivered. In order to invoke the AUTOFS instead of
#you must set the AUTOFS flag to 1.
#
#/usr/sbin/automount is now a script that sources in this file
#Depending on the variable AUTOFS, either AUTOFS or the old
#automount process will execute. The nfs.client start script
#will also use this variable to start the appropriate process
#during the boot sequence.
#AUTOFS= 0 - use the old automount process.
# 1 - use the new AutoFS.
#AUTOMOUNT_OPTIONS= - options to the AutoFS automount command
#AUTOMOUNTD_OPTIONS= - options to the AutoFS automountd daemon
#
#The AUTOMOUNT flag still needs to be set for either the old
#automount or new AutoFS to be started by the nfs.client script.
#
AUTOFS=0
AUTOMOUNT_OPTIONS=""
AUTOMOUNTD_OPTIONS=""
#

[Robert-Jan Goossens]

do you use windows terminal servers (windows 2000 or NT) ?

http://support.microsoft.com/default.aspx?kbid=818528

[Attila Horváth_1]

I have setted the debug level to 3 and restarted the samba. After then I have maked 2 connection and deleted the log.smbd
After I have tried to make a new connection which was not accepted. Here is the log.smbd
[2005/02/18 11:54:30, 3] param/loadparm.c:(1233)
Initialising global parameters
[2005/02/18 11:54:30, 3] param/params.c:(577)
params.c:pm_process() - Processing configuration file "/etc/opt/samba/smb.conf
"
[2005/02/18 11:54:30, 3] param/loadparm.c:(2970)
Processing section "[global]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[homes]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[tmp]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[ora_arch]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[ora_bkup]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[girogep]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[mick]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[debug]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[bankcardIN]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[bankcardOUT]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[ora_bkup_IT]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[ora_arch_IT]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[ora_bkup_db1]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[ora_arch_db1]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[mick_db1]"
[2005/02/18 11:54:30, 2] param/loadparm.c:(2988)
Processing section "[mick_it]"
[2005/02/18 11:54:30, 3] param/loadparm.c:(1968)
adding IPC service IPC$
[2005/02/18 11:54:30, 3] param/loadparm.c:(1968)
adding IPC service ADMIN$
[2005/02/18 11:54:30, 2] lib/interface.c:(81)
added interface ip=192.168.1.222 bcast=192.168.1.255 nmask=255.255.255.0
[2005/02/18 11:54:30, 0] locking/brlock.c:(233)
Failed to open byte range locking database
[2005/02/18 11:54:30, 0] locking/locking.c:(354)
ERROR: Failed to initialise locking database
[2005/02/18 11:54:30, 0] locking/locking.c:(354)
ERROR: Failed to initialise locking database
#

[Attila Horváth_1]

I do not use terminal szerver.

[Darren Prior · Accepted solution]

I would suggest that you need to increase nflocks. I believe Samba needs something like 12 + (clients * 10), so you're hitting the limit with just 2 clients.

I believe there's info on recommended kernel parameters in the CIFS manual.

regards,

Darren.

[Attila Horváth_1]

You are right!

After I have stopped an oracle instance, the 3rd user can connect to samba.
Thanks the solution!

(The problem is that I can't modify the any kernel parameters because I can't build a new kernel.)

[Peter Godron]

Attile,
so the problem was the nflocks kernel as suggested in second mail?

[Attila Horváth_1]

Yes, the problem was the nflocks.