similar to: Winbindd (tdb_chainlock_with_timeout_internal: alarm (40) timed out for key)

Hi! Thanks  for answer! In future my plan is update, but this momento is no possible.. :-| But, same error, in same time, in 3 server, is very strange.... Regards; On 24-05-2018 15:38, Rowland Penny via samba wrote: > On Thu, 24 May 2018 09:32:56 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >> Hi! >> >> I have 3 server: >> >> S.O.

On Thu, 24 May 2018 09:32:56 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > I have 3 server: > > S.O. -  Debina 8 > > Winbind Version : 2:4.2.10+dfsg-0+deb8u3 > > Member Domain > > Samba Server : Ubuntu 14.04 with Samba 4.7.7 , are 18 Dcs > > --------------------- > > > In day 21/05 , the 3 server have same problema

Hey, But What's the reason of this error? On 05/25/2018 04:58 AM, Carlos via samba wrote: > Hi! > > Thanks  for answer! > > In future my plan is update, but this momento is no possible.. :-| > > But, same error, in same time, in 3 server, is very strange.... > > Regards; > > > On 24-05-2018 15:38, Rowland Penny via samba wrote: >> On Thu, 24 May

On Thu, 8 Dec 2016 13:54:17 -0500 lingpanda101 via samba <samba at lists.samba.org> wrote: > On 12/8/2016 1:14 PM, Rowland Penny via samba wrote: > > On Thu, 8 Dec 2016 13:03:49 -0500 > > lingpanda101 via samba <samba at lists.samba.org> wrote: > > > >> On 12/8/2016 12:52 PM, Rowland Penny via samba wrote: > >>> On Thu, 8 Dec 2016 12:27:20

On Wed, 19 Dec 2018 12:32:45 +0530 Amit Kumar via samba <samba at lists.samba.org> wrote: > Hey, > > But What's the reason of this error? > I do not know, but what I do know is that, if it is a bug, you will never get it fixed in Samba 4.2.x, this version is EOL. It might also have been fixed in a later version. Sorry if this isn't what you want to hear. Rowland

Hello, I have Samba 4.6 as AD domain member and sometime the users fails to login, the issue disappear after some minutes. I have enabled log leve 10 and I can see the following errors: 2019/03/12 09:20:32.280799,  5, pid=15466, effective(0, 0), real(0, 0)] ../source3/lib/username.c:181(Get_Pwnam_alloc)   Finding user BITINTRA\U002489 [2019/03/12 09:20:32.281111,  5, pid=15466, effective(0,

Hi, I am running samba/winbind 4.2.14 on Debian 8 which is joined to an Active Directory and would like to know if you have any idea with my issue. In my case, ntlm authentification is enabled in squid (proxy). Here is the problem that I am facing : "wbinfo -t" takes sometimes more than 30 secondes to display the result. For some reason, the server loses it's connection to the

We are using Samba 4.6.15. We have users not being able to login. winbindd log shows this: [2018/06/14 14:48:44.300203, 0, pid=3228] ../source3/rpc_client/cli_pipe.c:3292(cli_rpc_pipe_open_schannel_with_creds) netlogon_creds_cli_get returned NT_STATUS_UNSUCCESSFUL [2018/06/14 14:53:43.896350, 0, pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)

Am 2017-07-11 um 09:34 schrieb Stefan G. Weichinger via samba: > [2017/07/11 09:31:17.790046, 2] > ../source4/dns_server/dns_query.c:1019(dns_server_process_query_send) > Not authoritative for 'SERVER', forwarding > [2017/07/11 09:31:17.826966, 2] > ../source4/dns_server/dns_query.c:1019(dns_server_process_query_send) > Not authoritative for 'SERVER',

Hello list, My samba server stopped allowing access to shares this morning. It gave some funky errors. Has anyone seen these before? The OS is Fedora 9 and the version is... Version 3.2.0pre3-9.fc9 Am using ADS security for serving shares. Server is EXAMPLEDC.EXAMPLE.CORP Looks like it is saying no login servers in client log but, there are two listed in smb.conf and they both replied to a ping

Hello list Our central fileserver is a Samba 3.0.25b on Solaris 9 and has 10'000 users (several hundreds at the same time). This week it died on us and when I inspected the machine, it was out of 8GB Memory and 16GB Swap because thousands of smbd processes were running. netstat -na showed that many hundreds of connections to port 445 were in CLOSE_WAIT state. We first thought it could be

Hey Rowland, I wanted to ask a. What is mutex.tdb, what is its purpose? b. why "mutex grab failed" started appearing in messages, what can be the probable reasons? Is pre-authentication failed related to locking failure of mutex.tdb? Dec 15 12:49:52 abc winbindd[30467]: [2018/12/15 12:49:52.764924, 0] ../source3/libsmb/cliconnect.c:1921(cli_session_setup_spnego_send) Dec 15

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)

Hi all, After much grief today, we'd like to support the 'TODO' note in source/lib/util_tdb.c :- /* TODO: If we time out waiting for a lock, it might * be nice to use F_GETLK to get the pid of the * process currently holding the lock and print that * as part of the debugging message. -- mbp */ It could have saved us a whole-sale restart of Samba if we could have more easily

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 -9 , so I rebooted which worked. The only error I could see out of the ordinary would be

On 12/8/2016 2:10 PM, Rowland Penny via samba wrote: > On Thu, 8 Dec 2016 13:54:17 -0500 > lingpanda101 via samba <samba at lists.samba.org> wrote: > >> On 12/8/2016 1:14 PM, Rowland Penny via samba wrote: >>> On Thu, 8 Dec 2016 13:03:49 -0500 >>> lingpanda101 via samba <samba at lists.samba.org> wrote: >>> >>>> On 12/8/2016 12:52

After upgrading to 3.0.26a and moving to linux my member server gets hundreds of IPC$ connections when I run smbstatus. I also see in my logs the following... [2007/10/01 10:01:15, 0] lib/util_tdb.c:tdb_chainlock_with_timeout_internal(84) tdb_chainlock_with_timeout_internal: alarm (10) timed out for key VALDEZ in tdb /usr/local/samba/private/secrets.tdb I did a dump of secrets on my old

On Tue, 6 Dec 2016 14:52:20 -0500 lingpanda101 via samba <samba at lists.samba.org> wrote: > On 12/6/2016 1:49 PM, Rowland Penny via samba wrote: > > On Tue, 6 Dec 2016 19:38:49 +0100 > > Marc Muehlfeld via samba <samba at lists.samba.org> wrote: > > > >> Hello, > >> > >> Am 06.12.2016 um 19:15 schrieb lingpanda101 via samba: >

Hi, We are experiencing a problem with Samba 3.6.4 on Solaris 10 update 10. This problem has only recently started since an upgrade to v3.6.3 and was still present after rebuilding to 3.6.4. We are using the version of samba packaged by OpenCSW. >From a client perspective, the issue is manifested as intermittent very poor performance or intermittent inability to save a file to the share at

Hi list, Thanks in advanced. I have written a winbindd client software to do NTLM authentication by using WINBINDD_PAM_AUTH_CRAP message. that is to say, my winbindd client is similar to ntlm_auth, but with high performance. when I test it under large traffic, most of the time they all work well. and the transaction per second can reach more than 900. but sometimes, winbindd will return