[Samba] secrets.tdb locking fun!
jra at samba.org
Fri Jun 15 17:55:11 GMT 2007
On Fri, Jun 15, 2007 at 06:44:41PM +0100, Mac wrote:
> Hi there,
> >Date: Fri, 15 Jun 2007 10:32:50 -0700
> >From: Jeremy Allison <jra at samba.org>
> >To: Mac <mac at nibsc.ac.uk>
> >Cc: samba at samba.org
> >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).
I mean the one in the non-TERM'able state. That's the one that's
blocking the others.
More information about the samba