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
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 linuxAdditional info, maybe relevant: on the DC I saw yesterday: Dez 11 20:00:16 backup winbindd[1390]: [2017/12/11 20:00:16.560037, 0] ../source3/winbindd/winbindd_group.c:45(fill_grent) Dez 11 20:00:16 backup winbindd[1390]: Failed to find domain 'NT AUTHORITY'. Check connection to trusted domains! This line repeated within seconds after reboot (reconnect with DM?), after that no more. DC, samba 4.6.11, debian 9.3 (LPH packages): # smb.conf (again): [global] workgroup = ARBEITSGRUPPE realm = arbeitsgruppe.hidden.tld netbios name = BACKUP server role = active directory domain controller idmap_ldb:use rfc2307 = yes dns forwarder = 10.0.0.254 [netlogon] path = /var/lib/samba/sysvol/hidden.tld/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No
DM crashed again. I will downgrade to 4.5.15 later this day, as this release works without problems at another customer.
DM crashed again. I will downgrade to 4.5.15 later this day, as this release works without problems at another customer.
Am 2017-12-12 um 16:42 schrieb Stefan G. Weichinger via samba:> Additional info, maybe relevant: > > on the DC I saw yesterday: > > Dez 11 20:00:16 backup winbindd[1390]: [2017/12/11 20:00:16.560037, 0] > ../source3/winbindd/winbindd_group.c:45(fill_grent) > Dez 11 20:00:16 backup winbindd[1390]: Failed to find domain 'NT > AUTHORITY'. Check connection to trusted domains!As I found on google this is related to the fact that we run (small shares ... ) file services on the DC as well. I assume I can ignore these lines on the DC?