跳转到主内容

报告"SID Lookup failed (SID查找失败)"事件

i
Knowledge Base guidance

This article may include metadata, visibility, validation state, and related support guidance.

适用场景

ONTAP 9

问题描述

  • 已删除配额用户"Admin\GD-Admin"、并创建了一个同名 "Admin\GD-Admin"的配额用户组。
  • POST在 事件日志中报告SID查找失败错误:

Wed Jan 03 00:39:21 +0100 [Cluster: secd: secd.unexpectedFailure:error]: Unexpected SecD failure in Vserver "svm1". Details: Error: Lookup of CIFS account SID procedure failed   [ 0 ms] Using cached S-1-5-21-1586194396-3347935261-3522003902-4376 to 'Admin\GD-Admin' mapping   [2] Successfully connected to ip 172.XX.XXX.XX, port 88 using TCP   [2077] TCP connection to ip 172.XX.XXX.XX, port 88 failed: Operation timed out.   [2088] Successfully connected to ip 172.XX.XXX.XX, port 88 using TCP   [2098] Could not get credentials via S4U2Self based on full Windows user name 'GD-Admin@XXXX.YY'. Continuing to LDAP.   [2098] Using a cached connection to Cluster.XXXXX.YYY **[2099] FAILURE: Cannot get credentials for SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'. No associated primary group.   [2099] Could not get credentials via LDAP for Windows user 'GD-Admin' based on SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [2099] Could not get credentials for Windows user 'GD-Admin' or SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [2099] SID lookup failed 

Wed Jan 03 00:40:35 +0100 [Cluster: secd: secd.unexpectedFailure:error]: Unexpected SecD failure in Vserver "svm1". Details: Error: Lookup of CIFS account SID procedure failed   [0 ms] Using cached S-1-5-21-1586194396-3347935261-3522003902-4376 to 'Admin\GD-Admin' mapping   [2] Successfully connected to ip 172.24.XXX.XX, port 88 using TCP   [2052] TCP connection to ip 172.26.XXX.XX, port 88 failed: Operation timed out.   [4057] TCP connection to ip 172.26.XX.XXX, port 88 failed: Operation timed out.   [6060] TCP connection to ip 172.26.XXX.XXX, port 88 failed: Operation timed out.   [8062] TCP connection to ip 172.24.XXX.XXX, port 88 failed: Operation timed out.   [10064] TCP connection to ip 172.27.XXX.XXX, port 88 failed: Operation timed out.   [12068] TCP connection to ip 172.26.XXX.XXX, port 88 failed: Operation timed out.   [14070] TCP connection to ip 172.25.XX.XXX, port 88 failed: Operation timed out.   [ 14082] Successfully connected to ip 172.26.XX.XXX, port 88 using TCP   [14092] Could not get credentials via S4U2Self based on full Windows user name 'GD-Admin@XXXX.YY'. Continuing to LDAP.   [14092] Using a cached connection to Cluster.XXXX.YYY **[14093] FAILURE: Cannot get credentials for SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'. No associated primary group.   [14093] Could not get credentials via LDAP for Windows user 'GD-Admin' based on SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [14094] Could not get credentials for Windows user 'GD-Admin' or SID 'S-1-5-21-1586194396-3347935261-3522003902-4376'   [14094] SID lookup failed   [14094] Retry requested, but the retry window (7000 ms) has expired; giving up. 

Wed Jan 03 00:49:38 +0100 [Cluster: quota_map_proc: wafl.quota.user.map.retry:debug]: User identifier (UID) to Windows Security Identifier (SID) mapping or vice versa failed for certain user quota records on volume GlobalData@vserver:0d1e78c2-c702-11ed-8015-d039eaa26884. The quota user mapping for these records will be retried after the initial attempt in 1 minute intervals.