[Samba] tdb_lock failed.... (Interrupted system call)

[Pappas, Bill]

Here is the core of my config:

# Global parameters
[global]
	workgroup = CBT
	printing = none
	#bind interfaces only = Yes
	security = DOMAIN
	Interfaces = 199.76.2.91/24 127.0.0.1/24
	encrypt passwords = Yes
	obey pam restrictions = Yes
	password server = 10.1.1.241,10.4.17.19
	cups server = none
	#smb passwd file = /usr/local/samba/private/smbpasswd
	syslog = 2
	log level = 2
	log file = /usr/local/samba/var/log.%m
	max log size = 50
	preferred master = No
	wins server = 10.1.1.202,10.1.1.203,10.1.1.240
	#local master = No
domain master = no 
	dns proxy = No
	create mask = 0700
	force create mode = 0700
	security mask = 0700
	directory mask = 0700
	directory security mask = 0700	
	oplock break wait time = 2
	strict locking = No
wins support = no 



Thanks,
Bill Pappas - System Integration Engineer - SAN 
St. Jude Children's Research Hospital
332 North Lauderdale
Memphis, TN 38105
Danny Thomas Tower - Room D1010
Mail Stop 312
901-495-4549

-----Original Message-----
From: Volker Lendecke [mailto:Volker.Lendecke at SerNet.DE] 
Sent: Wednesday, June 13, 2007 4:44 PM
To: Jeremy Allison
Cc: Pappas, Bill; samba at lists.samba.org
Subject: Re: [Samba] tdb_lock failed.... (Interrupted system call)

On Wed, Jun 13, 2007 at 02:31:47PM -0700, Jeremy Allison wrote:
> >   tdb_chainlock_with_timeout_internal: alarm (10) timed out for key
> > SJMEMDC06 in tdb /usr/local/samba-3.0.23a/private/secrets.tdb
> 
> What platform are you running on ? I don't know of any specific issue
> around this, but we've definately done some work on tdb since 3.0.23.

10 seconds very likely sounds like the grab_server_mutex,
too many smbd trying to connect the DC at the same time.

Volker