similar to: tdb_expand overflow detected

On Wed, Nov 13, 2024, at 4:30 PM, Dan Langille via samba wrote: > Hello, > > I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with > quotas on those filesystems, etc) > > I'm seeing these entries in my logs. Is this something which needs > action? If not, I'll start ignoring them. > > Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11

On 19/11/24 02:27, Dan Langille via samba wrote: > On Wed, Nov 13, 2024, at 4:30 PM, Dan Langille via samba wrote: >> Hello, >> >> I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with >> quotas on those filesystems, etc) >> >> I'm seeing these entries in my logs. Is this something which needs >> action? If not, I'll start

On Tue, Nov 19, 2024, at 3:35 PM, Douglas Bagnall wrote: > On 19/11/24 02:27, Dan Langille via samba wrote: >> On Wed, Nov 13, 2024, at 4:30 PM, Dan Langille via samba wrote: >>> Hello, >>> >>> I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with >>> quotas on those filesystems, etc) >>> >>> I'm seeing these

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)

So I re run the test with domain users gid 14513 Still not working (sssd stopped, nsswitch.cnf with? "files winbind" for passwd group, # net cache flush + restart winbindd smb) On the samba server : # wbinfo -i MYDOMAIN\usertest MYDOMAIN\usertest:*:10430:*14513*:user TEST:/home/usertest:/bin/bash In log, I have : myw7worstation.log /[2019/06/19 12:04:29.496822,? 1]

On 20/11/24 11:55, Dan Langille wrote: > Hope that helps. Not much unfortunately. Running this: net cache list will tell you what the cache thinks it contains. If it is filled with real things, it could indicate where they're coming from. If it fails or shows a cache full of nonsense, well that is also interesting. > > The original messages are long scrolled off the

Hello samba list, We're trialling Samba 3.6 and on some of our systems I see the following type of messages in the smbd and winbind logs: [2012/03/16 17:28:59.038177, 0] ../lib/util/tdb_wrap.c:65(tdb_wrap_log) tdb(/var/lib/samba/messages.tdb): tdb_oob len 663932 beyond eof at 12288 [2012/03/16 17:28:59.038331, 0] ../lib/util/tdb_wrap.c:65(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 2 commands works : # getent passwd MYDOMAIN\\usertest MYDOMAIN\\usertest:*:10430:14513:user TEST:/home/usertest:/bin/bash # getent group MYDOMAIN\\"Utilisateurs du domaine" MYDOMAIN\utilisateurs du domaine:x:14513: I have to put "Utilisateurs du domaine" instead of Domain\ Users because the Windows AD is a french AD. Le 19/06/2019 ? 12:32, Rowland penny via samba a

Hello, I performed a test in order to get access to my samba share with winbindd (and not sssd). For that, 1. I change the gid of domain users from 513 to 15513 (to match with the domain range 10000 - 14999) And verify my test user is part of 15513 2. Stop sssd and change nsswitch.conf like this : /passwd:???? files winbind// //shadow:???? files// //group:????? files //winbind// / 3.

On a fresh installed Illumos/Solaris in a VirtualBox Guest I get the following error after starting up samba 4.10: [2019/04/01 09:51:41.112485, 0] ../../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) tdb(/var/samba/lock/gencache.tdb): tdb_open_ex: tdb_mutex_init failed for /var/samba/lock/gencache.tdb: Device busy [2019/04/01 09:51:41.141396, 0] ../../lib/util/become_daemon.c:136(daemon_ready)

Is it possible to make start DOMAIN range from 500 instead of 10000 ? I realized that all my gid are in range 500 to 600 and not in range 10000 - 14999 I thought? DOMAIN range 10000 - 14999 was reserved for DOMAIN users -------- Message transf?r? -------- Sujet?: Re: [Samba] Fwd: Re: Fwd: Re: Kerberos and NTLMv2 authentication Date?: Tue, 18 Jun 2019 16:25:39 -0300 De?: Edouard Guign? via

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 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, samba team and other, client software calls samba and samba reads /etc/samba/smb.conf where some parameter contains variable %i (client ip address), but when samba calls samba-dcerpcd, it again reads /etc/samba/smb.conf where some parameter contains variable %i and at that moment %i is not client ip address, it is equal 0.0.0.0 for example I need client ip1 and client ip2 to get

This question has already been asked in the past, but there was no answer. The above message is logged quite often in /var/log/samba/log.samba-dcerpcd. This is a stand-alone anonymous read-only server. Is it something to worry about? It smells like samba isn't working properly. If yes, how can I fix it? If no, how can I stop samba from logging un-interesting messages? What dcerpcd is

Release Announcements ===================== This is the second release candidate of Samba 4.16.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.16 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.16.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.16 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Hello. I'm gradually replacing my 4.17 installations with 4.19 (on FreeBSD). As soon as I do this, I'm starting to see gobs of messages in the log like the followings: rpcd_lsad[54129]: rpcd_lsad version 4.19.5 started. samba-dcerpcd[14381]: samba-dcerpcd version 4.19.5 started. I actually experience no troubles (so far) and there are no error messages actually, but is this