-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.tdb
What is SJMEMDC15? The name of your domain? or DC? Sounds like
you are not running Winbind.
:45 AM
To: Pappas, Bill
Cc: samba@lists.samba.org
Subject: Re: [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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pappas, Bill wrote:
What 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.
SJMEMDC is a DC. I am not using
@lists.samba.org
Subject: Re: [Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal
(rev_2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pappas, Bill wrote:
What is SJMEMDC15? The name of your domain? or DC? Sounds like
you are not running Winbind. If not, then running winbindd should
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.
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
Hospital
332 North Lauderdale
Memphis, TN 38105
Danny Thomas Tower - Room D1010
Mail Stop 312
-Original Message-
From: Pappas, Bill
Sent: Saturday, July 22, 2006 4:01 PM
To: Jeremy Allison
Cc: samba@lists.samba.org
Subject: RE: [Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal
, Bill
Sent: Saturday, July 22, 2006 4:01 PM
To: Jeremy Allison
Cc: samba@lists.samba.org
Subject: RE: [Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal
Jeremy Allison wrote:
Then it might be an intermittent bug in Veritas. What system call is
smbd hanging on ? smbd should never hang
-Original Message-
From: Pappas, Bill
Sent: Saturday, July 22, 2006 4:01 PM
To: Jeremy Allison
Cc: samba@lists.samba.org
Subject: RE: [Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal
Jeremy Allison wrote:
Then it might be an intermittent bug in Veritas. What system call is
smbd
On Mon, Jul 24, 2006 at 02:07:47PM -0500, Pappas, Bill wrote:
Jeremy,
I was in a position (last night) to upgrade to 3.0.23a.
Again, I was using 3.0.21c.
If smbd goes into the D state, we can at least eliminate the possibility
that it is an unexpected 3.0.21c bug.
Thanks - yes I
On Fri, Jul 21, 2006 at 04:59:51PM -0500, Pappas, Bill wrote:
Hello. I run samba 3.0.21c on RHEL AS 4 EMT_64 U3 and I've experienced a
strange problem where smbd will go (and stay) in the D state. While
waiting for IO (possibly), these smbd processes do not respond to client
requests, thus
On Fri, Jul 21, 2006 at 06:17:09PM -0500, Pappas, Bill wrote:
I will say this works for weeks on end w/o a problem. When you say this will
not work, why? I've had no real problems with the veritas clustered fs. It
adheres to file locking and fcntl operations like any normal local filesystem
332 North Lauderdale
Memphis, TN 38105
Danny Thomas Tower - Room D1010
Mail Stop 312
-Original Message-
From: Jeremy Allison [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 22, 2006 10:56 AM
To: Pappas, Bill
Cc: [EMAIL PROTECTED]; samba@lists.samba.org
Subject: Re: [Samba] tdb
Hello. I run samba 3.0.21c on RHEL AS 4 EMT_64 U3 and I've experienced a
strange problem where smbd will go (and stay) in the D state. While
waiting for IO (possibly), these smbd processes do not respond to client
requests, thus samba appears to be down. I could not kill these
processes via kill
On Fri, Jul 21, 2006 at 04:59:51PM -0500, Pappas, Bill wrote:
Hello. I run samba 3.0.21c on RHEL AS 4 EMT_64 U3 and I've experienced a
strange problem where smbd will go (and stay) in the D state. While
waiting for IO (possibly), these smbd processes do not respond to client
requests, thus
:29 2006
Subject: Re: [Samba] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal
On Fri, Jul 21, 2006 at 04:59:51PM -0500, Pappas, Bill wrote:
Hello. I run samba 3.0.21c on RHEL AS 4 EMT_64 U3 and I've experienced a
strange problem where smbd will go (and stay) in the D state. While
waiting
16 matches
Mail list logo
