Pappas, Bill
2007-Oct-17 14:24 UTC
[Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal (rev_2)
I've seen more and more occurrences of the following error (other people have different password servers) on the web. I submitted this question before, but it was never resolved. I've even tried changing the underlying file system (from clustered vxfs to ext3) and I still see the error. Error: [2007/10/17 08:29:33, 0] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82) tdb_chainlock_with_timeout_internal: alarm (10) timed out for key SJMEMDC15 in tdb /usr/local/samba-3.0.23a/private/secrets.tdb I've been seeing this error on and off for well over 1 year. What happens is that many smb clients (as shown on the client log files) start throwing this error. They cannot reach the smb server. I restart the server and everything is fine for days or weeks until it starts over again. I'm running: # /usr/local/samba/sbin/smbd -V Version 3.0.23a 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
Francis Galiegue
2007-Oct-17 14:38 UTC
[Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal (rev_2)
Le mercredi 17 octobre 2007, Pappas, Bill a ?crit?:> I've seen more and more occurrences of the following error (other people > have different password servers) on the web. > > I submitted this question before, but it was never resolved. I've even > tried changing the underlying file system (from clustered vxfs to ext3) > and I still see the error. > > Error: > > [2007/10/17 08:29:33, 0] > tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82) > > tdb_chainlock_with_timeout_internal: alarm (10) timed out for key > SJMEMDC15 in tdb /usr/local/samba-3.0.23a/private/secrets.tdb > > > I've been seeing this error on and off for well over 1 year. > > What happens is that many smb clients (as shown on the client log files) > start throwing this error. They cannot reach the smb server. I restart > the server and everything is fine for days or weeks until it starts over > again. > > I'm running: > > # /usr/local/samba/sbin/smbd -V > > Version 3.0.23a >What is your smb.conf like? Also, what do you mean by "other people have different password servers"? Do you mean people of the same network? If yes, are these other password servers also running Samba? Some more information would be useful for sure :p -- Francis Galiegue, One2team - fg@one2team.com [ATTENTION : CHANGEMENT DE COORDONN?ES !] +33178945552, +33683877875, http://www.one2team.com 40 avenue Raymond Poincar? - 75116 PARIS
Gerald (Jerry) Carter
2007-Oct-18 12:46 UTC
[Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal (rev_2)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pappas, Bill wrote:> tdb_chainlock_with_timeout_internal: alarm (10) timed out for > key SJMEMDC15 in tdb /usr/local/samba-3.0.23a/private/secrets.tdbWhat is SJMEMDC15? The name of your domain? or DC? Sounds like you are not running Winbind. If not, then running winbindd should reduce contention on access to the secrets.tdb file. jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHF1VmIR7qMdg1EfYRAimuAJwPVIVLXg2WPVoYSCcHXlbkuTeFHgCfRB0a AEJViF6i4nxTSPZapqhKpf8=SQhl -----END PGP SIGNATURE-----
Possibly Parallel Threads
- tdb/tdbutil.c:tdb_chainlock_with_timeout_internal
- Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
- tdb_lock failed.... (Interrupted system call)
- Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)
- Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)