samba - Dec 2017 - 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  log.wb-ARBEITSGRUPPE
[2017/12/06 13:49:22.905348,  1]
../source3/libads/ldap_utils.c:93(ads_do_search_retry_internal)
  Reducing LDAP page size from 1000 to 500 due to IO_TIMEOUT

hmm

Did dbcheck on DC. 257 errors for 372 objects.
Jeez. Why? Where does that come from?
>From some updating? I am quite sure that I ran those checks back when I
converted the domain and wouldn't have skipped these errors IMO.

example:

CN=mitarbeiter,CN=Users,DC=arbeitsgruppe,DC=hiddentld,DC=at: 0x00000000
ERROR: unsorted attributeID values in replPropertyMetaData on
CN=mitarbeiter,CN=Users,DC=arbeitsgruppe,DC=hiddentld,DC=at

Not fixing replPropertyMetaData on
CN=mitarbeiter,CN=Users,DC=arbeitsgruppe,DC=hiddentld,DC=at

I see that there is a "--fix" option.
Any backups I should run before? Do it without clients connected?

pls advise

Am 2017-12-06 um 15:03 schrieb Stefan G. Weichinger via
samba:
> 
> Did dbcheck on DC. 257 errors for 372 objects.
> Jeez. Why? Where does that come from?
> 
> From some updating? I am quite sure that I ran those checks back when I
> converted the domain and wouldn't have skipped these errors IMO.
> 
> example:
> 
> CN=mitarbeiter,CN=Users,DC=arbeitsgruppe,DC=hiddentld,DC=at: 0x00000000
> ERROR: unsorted attributeID values in replPropertyMetaData on
> CN=mitarbeiter,CN=Users,DC=arbeitsgruppe,DC=hiddentld,DC=at
> 
> Not fixing replPropertyMetaData on
> CN=mitarbeiter,CN=Users,DC=arbeitsgruppe,DC=hiddentld,DC=at
> 
> I see 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 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)
  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