search for: tdb_wrap

...sing 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 19:00:45.852391, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Nov 11 19:00:45 tm samba-dcerpcd[7373]: tdb(/var/db/samba4/gencache.tdb): tdb_expand overflow detected current map_size[4294967295] size[128]! Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11 19:00:45.853054, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Nov 11...

...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 19:00:45.852391, > 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) > Nov 11 19:00:45 tm samba-dcerpcd[7373]: > tdb(/var/db/samba4/gencache.tdb): tdb_expand overflow detected current > map_size[4294967295] size[128]! > Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11 19:00:45.853054, > 0] ../../lib/tdb_wrap/tdb_wr...

...th >> 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 19:00:45.852391, >> 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) >> Nov 11 19:00:45 tm samba-dcerpcd[7373]: >> [...] > > The following is just one of the 343,930 log entries over a one hour period (about 95 messages per second). > > Nov 18 12:00:00 tm smbd[70983]: [2024/11/18 12:00:00.027823, 0] ../../lib/td...

....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) tdb(/var/vol/3/.ctera/samba/lock/g_lock.tdb): tdb_oob len 1684959121 beyond eof at 16384 [2018/06/14 14:53:43.896430, 0, pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) tdb(/var/vol/3/.ctera/samba/lock/g_lock.tdb): tdb_oob len 1684959121 beyond eof at 16384 [2...

...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) > tdb(/var/vol/3/.ctera/samba/lock/g_lock.tdb): tdb_oob len 1684959121 > beyond eof at 16384 [2018/06/14 14:53:43.896430, 0, > pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) > tdb(/var/vol/3/.ctera/samba/lock/g_lock.tdb): tdb_oob len 1684959121 > b...

...ose 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 19:00:45.852391, >>> 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) >>> Nov 11 19:00:45 tm samba-dcerpcd[7373]: >>> [...] >> >> The following is just one of the 343,930 log entries over a one hour period (about 95 messages per second). >> >> Nov 18 12:00:00 tm smbd[70983]: [2024/11/18 12:00:00....

...on_snum)// //? create_connection_session_info failed: NT_STATUS_ACCESS_DENIED// //[2019/06/19 12:05:27.124307,? 1] ../source3/smbd/service.c:521(make_connection_snum)// //? create_connection_session_info failed: NT_STATUS_ACCESS_DENIED/ log.winbindd-idmap /[2019/06/19 12:04:29.464431,? 1] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)// //? tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_transaction_commit: transaction error pending// //[2019/06/19 12:04:29.464460,? 1] ../source3/winbindd/idmap_tdb_common.c:138(idmap_tdb_common_allocate_id)// //? Error allocating a new GID// //[2019/06/19 12:04:29.46460...

....540456, 10, pid=15439, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd_cm.c:1014(cm_prepare_connection)   cm_prepare_connection: connecting to DC WG101SC0002.BITIntra.de for domain BITINTRA [2019/03/12 09:21:04.540067,  5, pid=15439, effective(0, 0), real(0, 0)] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)   tdb(/opt/samba/var/lock/mutex.tdb): tdb_brlock failed (fd=22) at offset 592 rw_type=2 flags=1 len=1 [2019/03/12 09:21:04.540189,  1, pid=15439, effective(0, 0), real(0, 0)] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)   tdb(/opt/samba/var/lock/mutex.tdb): tdb_lock f...

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) tdb(/var/lib/samba/messages.tdb): tdb_oob len 663932 beyond eof at 12288 [2012/03/16 17:28:59.038408, 0] ../lib/util/tdb_wrap.c:6...

...S_ACCESS_DENIED// >> //[2019/06/19 12:05:27.124307,? 1] >> ../source3/smbd/service.c:521(make_connection_snum)// >> //? create_connection_session_info failed: NT_STATUS_ACCESS_DENIED/ >> >> log.winbindd-idmap >> /[2019/06/19 12:04:29.464431,? 1] >> ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)// >> //? tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_transaction_commit: >> transaction error pending// >> //[2019/06/19 12:04:29.464460,? 1] >> ../source3/winbindd/idmap_tdb_common.c:138(idmap_tdb_common_allocate_id)// >> //? Error alloca...

...on_snum)// //? create_connection_session_info failed: NT_STATUS_ACCESS_DENIED// //[2019/06/19 11:17:04.348099,? 1] ../source3/smbd/service.c:521(make_connection_snum)// //? create_connection_session_info failed: NT_STATUS_ACCESS_DENIED/ log.winbindd-idmap /[2019/06/18 14:43:16.926952,? 1] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)// //? tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_transaction_commit: transaction error pending// //[2019/06/18 14:43:16.926982,? 1] ../source3/winbindd/idmap_tdb_common.c:138(idmap_tdb_common_allocate_id)// //? Error allocating a new GID// //[2019/06/18 14:43:16.92712...

...ession_info failed: NT_STATUS_ACCESS_DENIED// > //[2019/06/19 12:05:27.124307,? 1] > ../source3/smbd/service.c:521(make_connection_snum)// > //? create_connection_session_info failed: NT_STATUS_ACCESS_DENIED/ > > log.winbindd-idmap > /[2019/06/19 12:04:29.464431,? 1] > ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)// > //? tdb(/var/lib/samba/winbindd_idmap.tdb): tdb_transaction_commit: > transaction error pending// > //[2019/06/19 12:04:29.464460,? 1] > ../source3/winbindd/idmap_tdb_common.c:138(idmap_tdb_common_allocate_id)// > //? Error allocating a new GID// &gt...

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) daemon_ready: daemon 'smbd' finished starting up and ready to serv...

I have provisioned a AD DC using samba-4.11 and have completed the initial startup. Reviewing the contents of /var/log/samba4/ I see this in /var/log/samba4/smbd.log.smbd . . . [2020/06/05 15:55:18.663269, 2] ../../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) tdb(/var/db/samba4/registry.tdb): tdb_open_ex: could not open file /var/db/samba4/registry.tdb: No such file or directory [2020/06/05 15:55:19.262908, 2] ../../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) tdb(/var/db/samba4/account_policy.tdb): tdb_open_ex: could not op...

...effective(0, 0), real(0, > 0), > class=winbind] ../source3/winbindd/winbindd_cm.c:1014(cm_prepare_connection) > cm_prepare_connection: connecting to DC WG101SC0002.BITIntra.de for > domain BITINTRA [2019/03/12 09:21:04.540067,  5, pid=15439, > effective(0, 0), real(0, > 0)] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) > tdb(/opt/samba/var/lock/mutex.tdb): tdb_brlock failed (fd=22) at > offset 592 rw_type=2 flags=1 len=1 [2019/03/12 09:21:04.540189,  1, > pid=15439, effective(0, 0), real(0, > 0)] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) > tdb(/opt/samba/var/lock/mutex...

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

...>> 0), >> class=winbind] ../source3/winbindd/winbindd_cm.c:1014(cm_prepare_connection) >> cm_prepare_connection: connecting to DC WG101SC0002.BITIntra.de for >> domain BITINTRA [2019/03/12 09:21:04.540067,  5, pid=15439, >> effective(0, 0), real(0, >> 0)] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) >> tdb(/opt/samba/var/lock/mutex.tdb): tdb_brlock failed (fd=22) at >> offset 592 rw_type=2 flags=1 len=1 [2019/03/12 09:21:04.540189,  1, >> pid=15439, effective(0, 0), real(0, >> 0)] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) >> tdb(/opt/...

...on: getpeername failed with: Transport endpoint is not connected [2013/11/15 22:08:24.478174, 0, pid=4904] winbindd/winbindd_cm.c:835(cm_prepare_connection) cm_prepare_connection: getpeername failed with: Transport endpoint is not connected [2013/11/15 22:09:04.482330, 1, pid=4900] ../lib/util/tdb_wrap.c:65(tdb_wrap_log) [2013/11/15 22:09:04.482336, 1, pid=4901] ../lib/util/tdb_wrap.c:65(tdb_wrap_log) [2013/11/15 22:09:04.482336, 1, pid=4899] ../lib/util/tdb_wrap.c:65(tdb_wrap_log) tdb(/opt/MY/contrib/samba/var/locks/mutex.tdb): tdb_lock failed on list 45 ltype=1 (Interrupted system call) t...

...cache) initialize_winbindd_cache: clearing cache and re-creating with version number 2 [2016/12/08 15:42:02.258867, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'winbindd' finished starting up and ready to serve connections [2016/12/08 15:44:17.333519, 1] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) tdb(/usr/local/samba/var/lock/mutex.tdb): tdb_lock failed on list 63 ltype=1 (Interrupted system call) [2016/12/08 15:44:17.333569, 0] ../source3/lib/util_tdb.c:497(tdb_chainlock_with_timeout_internal) tdb_chainlock_with_timeout_internal: alarm (40) timed out fo...

...hen using smbclient (or indeed any client) connecting to the Samba server we see logs similar the following with log level of 3: [2012/07/18 20:00:33.762539, 3] libsmb/namequery.c:2461(get_dc_list) get_dc_list: preferred server list: ", *" [2012/07/18 20:00:43.756966, 1] ../lib/util/tdb_wrap.c:65(tdb_wrap_log) tdb(/var/opt/csw/samba/locks/mutex.tdb): tdb_lock failed on list 126 ltype=2 (Interrupted system call) [2012/07/18 20:00:43.757104, 0] lib/util_tdb.c:72(tdb_chainlock_with_timeout_internal) tdb_chainlock_with_timeout_internal: alarm (10) timed out for key UOS-ADS00002-SI.SOT...