prebuilt_systems:ucs:failed_to_re-index_objectsid_sambadb
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen der Seite angezeigt.
| Nächste Überarbeitung | Vorherige Überarbeitung | ||
| prebuilt_systems:ucs:failed_to_re-index_objectsid_sambadb [2023/12/26 12:47] – angelegt loma | prebuilt_systems:ucs:failed_to_re-index_objectsid_sambadb [2025/05/18 09:22] (aktuell) – loma | ||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| ====== Failed to re-index objectSid (SambaDB) ====== | ====== Failed to re-index objectSid (SambaDB) ====== | ||
| + | You would like to show your appreciation for our help 8-o. Gladly. 🙏 We thank you for your donation! | ||
| + | [[https:// | ||
| + | \\ | ||
| + | Freely available [[: | ||
| + | \\ | ||
| + | GITLAB: [[https:// | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
| + | |||
| Failed to re-index objectSid in a non ucs@school environment, | Failed to re-index objectSid in a non ucs@school environment, | ||
| Zeile 27: | Zeile 37: | ||
| ===== Investigation: | ===== Investigation: | ||
| - | The message indicates, that the SID, samba would like to give, is already occupied by an other userobject. | + | The message indicates, that the SID, samba would like to give, is already occupied by an other userobject. To find out, you can check the ‘Rid Set’ of the server. |
| - | To find out, you can check the ‘Rid Set’ of the server. | + | |
| <code bash> | <code bash> | ||
| Zeile 36: | Zeile 45: | ||
| rIDAllocationPool rIDNextRID | rIDAllocationPool rIDNextRID | ||
| </ | </ | ||
| - | dn: CN=RID Set, | + | dn: CN=RID Set, |
| - | rIDNextRID: **1161** | + | rIDNextRID: **1161** |
| - | The attribute rIDNextRID shows the last successfully given RID. | + | The attribute rIDNextRID shows the last successfully given RID. Now you can check if this RID (should ) and the next following RID (should not ) (be)/is used. \\ |
| - | Now you can check if this RID (should ) and the next following RID (should not ) (be)/is used. | + | Take the SID from an other user or extract the Domain SID part: |
| - | Take the SID from an other user or extract the Domain SID part: | + | |
| univention-ldapsearch -xLLL sambaDomainName=* sambaSID | sed -ne ' | univention-ldapsearch -xLLL sambaDomainName=* sambaSID | sed -ne ' | ||
| Zeile 47: | Zeile 55: | ||
| univention-ldapsearch -LLL sambaSID=S-1-5-21-2438365080-1175145288-4246282840-1161 dn | univention-ldapsearch -LLL sambaSID=S-1-5-21-2438365080-1175145288-4246282840-1161 dn | ||
| - | dn: uid=b.baumann, | + | dn: uid=b.baumann, |
| + | |||
| + | univention-ldapsearch -LLL sambaSID=S-1-5-21-2438365080-1175145288-4246282840-1162 dn | ||
| + | |||
| + | dn: uid=l.croft, | ||
| + | The user l.croft already occupies the rid, which should be next in samba’s opinion. So this is the cause of the ‘“constraint violation”’ from. \\ | ||
| + | |||
| + | ===== Solution: ===== | ||
| + | Edit the ‘Rid Set’ in samba to the last successfully used RID. | ||
| + | ldbedit -H / | ||
| + | |||
| + | <code bash> | ||
| + | # editing 1 records | ||
| + | # record 1 | ||
| + | dn: CN=RID Set, | ||
| + | objectClass: | ||
| + | objectClass: | ||
| + | cn: RID Set | ||
| + | instanceType: | ||
| + | whenCreated: | ||
| + | whenChanged: | ||
| + | uSNCreated: 3667 | ||
| + | uSNChanged: 3667 | ||
| + | showInAdvancedViewOnly: | ||
| + | name: RID Set | ||
| + | objectGUID: 993ec2b2-c611-4cb4-8924-781111a47832 | ||
| + | rIDAllocationPool: | ||
| + | rIDPreviousAllocationPool: | ||
| + | rIDUsedPool: | ||
| + | objectCategory: | ||
| + | rIDNextRID: 1162 | ||
| + | distinguishedName: | ||
| + | </ | ||
| + | |||
| + | |||
| + | Source: https:// | ||
prebuilt_systems/ucs/failed_to_re-index_objectsid_sambadb.1703594835.txt.gz · Zuletzt geändert: von loma
