search for: idmap_tdb_common_allocate_id

..._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.464606,? 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.464622,? 1] ../source3/winbindd/idmap_tdb_common.c:138(idmap...

...that there is a "--fix" option. > Any backups I should run before? Do it without clients connected? fixed those last week already : done today again these lines on the DM server: # tail log.winbindd-idmap [2017/12/12 15:40:40.200201, 1] ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) Error allocating a new GID [2017/12/12 15:55:55.186605, 1] ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) Fatal Error: GID range full!! (max: 2999) [2017/12/12 15:55:55.186630, 1] ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) Error...

Twice this week I had a Domain Member Server "crash" A week ago I saw errors like this in log.winbindd-idmap: [2017/11/27 11:25:02.768090, 1] ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) Error allocating a new GID [2017/11/27 11:25:02.768213, 1] ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) Fatal Error: GID range full!! (max: 2999) I increased this from 2999 to 9999: idmap config arbeitsgruppe:schema_mode = rfc2307 idmap config arbeitsgrup...

Am 2017-12-06 um 13:20 schrieb Stefan G. Weichinger via samba: > Could it somehow be the case that the kerberos-ticket between DM and DC > runs out after X hours or so? > > Just guessing ... found this thread https://lists.samba.org/archive/samba/2017-October/211476.html sounds quite similar - klist showed no Kerberos ticket, did a kinit ... dunno? I also see this: # tail

...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.464606,? 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.464622,...

..._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.927123,? 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.927140,? 1] ../source3/winbindd/idmap_tdb_common.c:138(idmap...

...ichinger via samba" <samba at lists.samba.org> wrote: > > Twice this week I had a Domain Member Server "crash" > > A week ago I saw errors like this in log.winbindd-idmap: > > [2017/11/27 11:25:02.768090, 1] > ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) > Error allocating a new GID > [2017/11/27 11:25:02.768213, 1] > ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) > Fatal Error: GID range full!! (max: 2999) > > I increased this from 2999 to 9999: > > idmap config arbeitsgruppe:schema_...

...nbindd-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.464606,? 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.464622,? 1] > ../source3/wi...

On both Samba 4.5.1 member server and Samba 3.6.25 member server I tried the following command wbinfo –set-uid-mapping=35049,S-1-5-21-xx-xx-xxx-xxx this should have created a mapping entry consistent with the one on the domain controller for a trusted user But I got the following error failed to call wbcSetUidMapping: WBC_ERR_NOT_IMPLEMENTED As far as I can tell from network

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

Am 2017-12-12 um 15:59 schrieb Stefan G. Weichinger via samba: > [2017/12/12 15:55:55.186723, 1] > ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) > Fatal Error: GID range full!! (max: 2999) > [2017/12/12 15:55:55.186736, 1] > ../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id) > Error allocating a new GID > > for reference: Samba 4.6.11, gentoo linux Additional info, maybe relevant: on t...