Hi there,
>Date: Fri, 15 Jun 2007 10:32:50 -0700
>From: Jeremy Allison <[EMAIL PROTECTED]>
>To: Mac <[EMAIL PROTECTED]>
>Cc: [EMAIL PROTECTED]
>Subject: Re: [Samba] secrets.tdb locking fun!
>>
>> [2007/06/15 13:02:20, 0, pid=5430] tdb/tdbutil.c:tdb_log(783)
>> tdb(/usr/local/samba/private/secrets.tdb): tdb_lock failed on list 2
>> ltype=2 (Interrupted system call)
>> [2007/06/15 13:02:20, 0, pid=5430]
>> tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82)
>> tdb_chainlock_with_timeout_internal: alarm (10) timed out for key replay
>> cache mutex in tdb /usr/local/samba/private/secrets.tdb
>>
>If you get an smbd in that state, can you attach to it with gdb and
>get a stack backtrace so we can see where it was ?
We'll certainly have a go for you. I assume you mean the 'smbd' that
has got wedged (non "TERM"-able). Or do you mean the still running ones
(i.e the ones that are getting the 'tdb' errors.)
<fx: Mac beavering off to install gdb for Solaris 9....>
(and yes, the very astute of you will have noticed that the code
fragment I mentioned came from 3.0.25, but the log file entries are
3.0.24....... We'll move to 3.0.25 when 'b' comes out).
Mac
Assistant Systems Administrator @nibsc.ac.uk
[EMAIL PROTECTED]
Work: +44 1707 641565 Everything else: +44 7956 237670 (anytime)
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
