similar to: Mutex lock contention against Active directory domain controllers causing authentication failures

Hello! i have some trouble with my samba setup (v3.4.5 or 3.3.10). the server is not responding (or very slow) for some minutes in log.winbindd-idmap i get: ---------------------------- [2010/02/03 04:14:27, 1] lib/util_tdb.c:521(tdb_wrap_log) tdb(/home/samba-server/samba/3.4.5/var/locks/mutex.tdb): tdb_lock failed on list 43 ltype=1 (Interrupted system call) [2010/02/03 04:14:27,

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

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

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

On Sun, 17 Jun 2018 12:06:17 +0000 Oren Kishon via samba <samba at lists.samba.org> wrote: > 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

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

On Tue, 12 Mar 2019 11:32:46 +0100 Andrea Cucciarre' via samba <samba at lists.samba.org> wrote: > 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,

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)

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,

The OS is OmniOS, the DC is Windows Server (not sure about the release), and below the smb.conf. I have also noted that they have more trusted domains, but since they configured ad idmap only for one domain, then all the other domains use tdb idmap [global] client ldap sasl wrapping = plain dedicated keytab file = /etc/krb5.keytab disable spoolss = yes host msdfs = no idmap config * : backend

Hi, our window file server running 3.0.25b-33 (X64) (Sernet rpm) on SLES 9 SP3 has been stoped working. The log file shows nothing new. No error ... Only the clients can not connect to the server. After a restart of smbd it seems to work for a while. Any idea ? Any help is welcome !! ---------The last logline before was 10:39; at10:42 no connection was possible----- Jan 7 10:42:30 modena

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

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 in same time, th problem resolved after 40 minutes.... Syslog server 1/2/3: May 21 08:14:12  winbindd[6718]: [2018/05/21 08:14:12.288624,  0]

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, 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

Hi, I'm running Samba 2.2 on a legacy Solaris 7 box that I need to upgrade to Samba 3 to allow Windows Vista client to access their shares. I built Samba-3.0.25a from source and so long as I ran configure with the "--without-winbind" it compiled and installed okay. It is using DOMAIN authentication so I assume that not including winbind is acceptable. I am running the new version

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

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

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