search for: idmap_tdb_common_allocate_id_act

Displaying 6 results from an estimated 6 matches for "idmap_tdb_common_allocate_id_act".

GID range full!!
2017 Dec 12
4
GID range full!!
...ek 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 allocating a new GID [2017/12/12 15:55:55.186723, 1] ../source3/winbindd/idmap_tdb_common.c:68(idmap_tdb_common_allocate_id_action) Fa...
GID range full!!
2017 Dec 06
2
GID range full!!
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
GID range full!!
2017 Dec 04
2
GID range full!!
...ember 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 arbeitsgruppe:range = 10000-9999999 idmap config arbeitsgruppe:backend = ad idmap config * : range = 2000-9999 idmap config * : backend = tdb and...
wbinfo -u does not listed trusted users, wbinfo -n works, idmap not working
2016 Dec 19
1
wbinfo -u does not listed trusted users, wbinfo -n works, idmap not working
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
GID range full!!
2017 Dec 04
0
GID range full!!
...; 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 arbeitsgruppe:range = 10000-9999999 > idmap config arbeitsgruppe:backend = ad > idmap config * : range = 2000-9...
GID range full!!
2017 Dec 12
0
GID range full!!
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 the D...