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

This is a discussion on [Samba] tdb_lock failed.... (Interrupted system call) - Samba ; Has anyone seen any fixes above 3.0.23a that addresses an issue similar to this one? [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_log(783) tdb(/usr/local/samba-3.0.23a/private/secrets.tdb): tdb_lock failed on list 65 ltype=1 (Interrupted system call) [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82) tdb_chainlock_with_timeout_internal: alarm (10) timed out for key ...

+ Reply to Thread
Results 1 to 9 of 9

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

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

    Has anyone seen any fixes above 3.0.23a that addresses an issue similar
    to this one?



    [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_log(783)

    tdb(/usr/local/samba-3.0.23a/private/secrets.tdb): tdb_lock failed on
    list 65 ltype=1 (Interrupted system call)

    [2007/06/13 14:01:40, 0]
    tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82)

    tdb_chainlock_with_timeout_internal: alarm (10) timed out for key
    SJMEMDC06 in tdb /usr/local/samba-3.0.23a/private/secrets.tdb







    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



    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  2. Re: [Samba] tdb_lock failed.... (Interrupted system call)

    On Wed, Jun 13, 2007 at 03:01:01PM -0500, Pappas, Bill wrote:
    > Has anyone seen any fixes above 3.0.23a that addresses an issue similar
    > to this one?
    >
    >
    >
    > [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_log(783)
    >
    > tdb(/usr/local/samba-3.0.23a/private/secrets.tdb): tdb_lock failed on
    > list 65 ltype=1 (Interrupted system call)
    >
    > [2007/06/13 14:01:40, 0]
    > tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82)
    >
    > 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.

    Jeremy.
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  3. Re: [Samba] tdb_lock failed.... (Interrupted system call)

    On Wed, Jun 13, 2007 at 03:01:01PM -0500, Pappas, Bill wrote:
    > Has anyone seen any fixes above 3.0.23a that addresses an issue similar
    > to this one?


    Very likely by starting winbind this will be resolved.

    Volker

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.5 (GNU/Linux)

    iD8DBQFGcGLxpZr5CauZH5wRAisJAKC2fZkQb7AK0BvuEm56R9 CHc0L/ZACfQa8C
    vdhHJdRBJbfgDKWk3Fmaxhs=
    =9G2R
    -----END PGP SIGNATURE-----


  4. RE: [Samba] tdb_lock failed.... (Interrupted system call)

    Linux RHEL 4 U4 emt_64. I compiled from source.

    My configure options were:
    $ ./configure --prefix /usr/local/samba-3.0.23a --with-smbmount
    --with-pam --with-pam_smbpass --with-acl-support --disable-iprint
    --disable-cups

    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: Jeremy Allison [mailto:jra@samba.org]
    Sent: Wednesday, June 13, 2007 4:32 PM
    To: Pappas, Bill
    Cc: samba@lists.samba.org
    Subject: Re: [Samba] tdb_lock failed.... (Interrupted system call)

    On Wed, Jun 13, 2007 at 03:01:01PM -0500, Pappas, Bill wrote:
    > Has anyone seen any fixes above 3.0.23a that addresses an issue

    similar
    > to this one?
    >
    >
    >
    > [2007/06/13 14:01:40, 0] tdb/tdbutil.c:tdb_log(783)
    >
    > tdb(/usr/local/samba-3.0.23a/private/secrets.tdb): tdb_lock failed

    on
    > list 65 ltype=1 (Interrupted system call)
    >
    > [2007/06/13 14:01:40, 0]
    > tdb/tdbutil.c:tdb_chainlock_with_timeout_internal(82)
    >
    > 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.

    Jeremy.


    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  5. 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

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.5 (GNU/Linux)

    iD8DBQFGcGU4pZr5CauZH5wRAqSRAJ9+A1ph5G26GKA9cvIiAf 0xtSVuDACgi1+q
    mpivwAfK1udp77e5PRBTdaM=
    =m7bX
    -----END PGP SIGNATURE-----


  6. RE: [Samba] tdb_lock failed.... (Interrupted system call)

    I'm not using (running) winbind in my setup

    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@SerNet.DE]
    Sent: Wednesday, June 13, 2007 4:35 PM
    To: Pappas, Bill
    Cc: samba@lists.samba.org
    Subject: Re: [Samba] tdb_lock failed.... (Interrupted system call)

    On Wed, Jun 13, 2007 at 03:01:01PM -0500, Pappas, Bill wrote:
    > Has anyone seen any fixes above 3.0.23a that addresses an issue

    similar
    > to this one?


    Very likely by starting winbind this will be resolved.

    Volker

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  7. RE: [Samba] tdb_lock failed.... (Interrupted system call)

    Is there a way to throttle this?

    Under such circumstances, I have to kill samba and restart it.

    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@SerNet.DE]
    Sent: Wednesday, June 13, 2007 4:44 PM
    To: Jeremy Allison
    Cc: Pappas, Bill; samba@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

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  8. RE: [Samba] tdb_lock failed.... (Interrupted system call)

    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@SerNet.DE]
    Sent: Wednesday, June 13, 2007 4:44 PM
    To: Jeremy Allison
    Cc: Pappas, Bill; samba@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

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  9. Re: [Samba] tdb_lock failed.... (Interrupted system call)

    On Wed, Jun 13, 2007 at 04:47:16PM -0500, Pappas, Bill wrote:
    > Is there a way to throttle this?


    No, this is in response to client requests.

    The real way is to start winbind, which proxies all auth
    requests through the same connection. With modern Samba you
    can simply start it and not change any configuration.

    > Under such circumstances, I have to kill samba and restart it.


    That's a different problem then, maybe on your DC. Samba
    should come back after a while.

    Volker

    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.5 (GNU/Linux)

    iD8DBQFGcNzapZr5CauZH5wRAp2JAKCUvZ3nDQGRI+SFDnfNcI/tn/+pEACfTZHi
    Iad2kZ0NfyuBSQyZ1s3qQ60=
    =P2OA
    -----END PGP SIGNATURE-----


+ Reply to Thread