similar to: Accumulating smbd processes and sockets in CLOSE_WAIT state

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.

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 list DFS Links in a separate share seems to work, but in the [homes] section does not. Is this a known problem? Samba is 3.0.26a. /etc/smb.conf excerpts: ---------------------------- 8< ---------------------------- [global] ... host msdfs = yes ... [homes] ... msdfs root = yes ... [dfstest] path = /data/dfsroot msdfs root = yes ---------------------------- 8<

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

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

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, 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 all, I've recently run into a situation whereby I need samba to tackle a task. It is complicated by multi-vendor infrastructure. I am hoping that someone here has the knowledge and experience to say: "been there, done that...here is how..." To give some background to the architecture (slightly exotic)... 1. We run a large Sun SAM-FS/QFS installation (a high end

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)

Hi list I am having difficulties with 3.2.0rc1 on a Solaris10 server. After unsuccessfully trying once again to get winbindd to run in our environment (AD, SFU), we resorted back to the old solution of syncing the nss infos from AD down to the Unix passwd and group files by a perlscript and doing only authentication against the Active Directory. Now, I have other problems, however. Going

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

Hello, I''m experiencing a strange, but very bad behavior with Mongrel 0.3.13.4 and Pound 1.8. Every 6 hours or so one of our nine (not consistent on which one) application servers ( each one running several mongrel processes ) will start leaving lots of socket connections with pound open. This leads to "Too many open files" errors. I''ve set pound to close connections

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

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

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,

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)